Certify Hammer/Hammer++ open-save compatibility

[dayflaree]

Objective

Complete future real Hammer or Hammer++ open/save certification when a runnable editor environment is available.

Background

Issue #131 now tracks the no-claim boundary that is actionable without Hammer. This issue preserves the original empirical certification goal for a future environment that has a real Hammer or Hammer++ executable.

Required work

• Use a real runnable Hammer or Hammer++ executable.
• Record editor kind, path, version/build, runtime mode, game config, game dir, and FGD paths.
• Generate a Source Weaver VMF fixture specifically for editor open/save validation.
• Open the VMF in the real editor.
• Record warnings, dialogs, console output, and load problems.
• Save as a separate VMF.
• Diff original versus saved VMF.
• Validate the saved VMF with Source Weaver.
• Update the compatibility/smoke matrix with a completed row.
• Post evidence with hashes and redistribution boundaries.

Acceptance criteria

• Evidence proves a real Hammer/Hammer++ editor opened and saved the VMF.
• Evidence includes exact tool path/version, input VMF, saved output, diff summary, warnings/errors, and Source Weaver validation result.
• The row states exactly what editor/game config was validated.
• No proprietary game content, editor binaries, SDK tools, or private assets are committed.

Non-goals

• Do not use fake editor wrappers.
• Do not reuse Source Weaver parser output as editor evidence.
• Do not treat Proton/Windows compatibility-data directories as an editor run unless Hammer/Hammer++ actually launches.

[dayflaree]

Blocker status checked after completing all currently actionable tickets.

Result

This remains open. I did not certify Hammer/Hammer++ open-save compatibility because no runnable Hammer or Hammer++ executable/session was available in the current environment, and no saved-VMF evidence exists from a real editor.

Commands run

cd /home/elijah/projects/sourceweaver
git status --short --branch
gh issue view 141 --repo dayflaree/sourceweaver --json number,title,state,body,labels,comments
uname -a
command -v hammer || true
command -v hammer.exe || true
command -v hammer++ || true
command -v hammerplusplus || true
command -v wine || true
rg -n "Hammer/Hammer\+\+ open/save|not certified|not validated|future issue #141|Hammer/Hammer\+\+" README.md CHANGELOG.md docs/compatibility-matrix.md docs/release.md docs/hammer-validation.md 2>/dev/null || true

Evidence

• Repository status before check: clean on main tracking origin/main.
• Current host is Linux; no native Windows/Hammer editor session was used.
• command -v hammer, hammer.exe, hammer++, and hammerplusplus produced no runnable editor path in the local shell.
• Existing docs keep Hammer/Hammer++ open/save as not validated / not certified and point to this future issue.

Blocker log:

acf801f520b1f410290055fc295233d513f6bd69447f61f088958cad72bf2bd5  /tmp/sourceweaver-issue141-blocker-check.log

Required evidence to close later

• Real Hammer or Hammer++ executable path/version.
• Source Weaver-generated VMF opened in the real editor.
• Editor save action completed.
• Saved VMF path, sanitized diff/inspection results, and SHA-256 hashes.
• Confirmation that no proprietary editor binaries, game content, private assets, or private paths were committed.

Redistribution and legal boundary

No Hammer/Hammer++ binary, Source SDK tool, game content, saved VMF from a real editor, private path, or proprietary asset was committed or redistributed. This comment records the blocker and leaves the future-certification ticket open.