Hammer Addons v0.1.0-alpha.5

Restore launcher compatibility with CS2 builds 25472966 and 25492732.
If the launcher reports that Asset Browser does not match a supported original
Valve build after these updates, install this package.

Fixes and improvements

• Added compatibility profiles for both builds after checking Valve signatures,
  x64 architecture, and the required Asset Browser exports and ordinals.
• All bundled example add-ons now support the reload lifecycle.
• Reload uses a verified package snapshot and its captured manifest. Failed or
  declined attempts that never reach native loading clean up their own copies.
• Failed native load attempts count toward the 32-attempt limit per add-on.
• Invalid reload preparation results disable the instance. A veto keeps the
  instance active but cannot undo changes already made by its callback.
• C++ callback exceptions revoke the failed add-on's SDK access and cancel its
  jobs while healthy add-ons continue receiving callbacks.

Update

1. Close Workshop Tools and the project picker.
2. Extract hammer-addons-v0.1.0-alpha.5-windows-x64.zip into a new folder
   outside your CS2 installation.
3. Copy your custom add-on folders from the previous package's addons/
   directory into the new package. Keep the updated bundled add-ons.
4. Start Launch Workshop Tools.cmd from the new folder. Update existing
   desktop or Steam shortcuts to point to this copy.

Use the complete package; editing compatibility.json beside an older launcher
does not update that launcher's compiled compatibility profiles. No Valve files
need to be replaced.

Validation and limits

The Windows build, native regression suites, and 35 loader integration scenarios
passed locally. The rebuilt launcher's --check accepts the installed CS2 build
25492732. A live editor session on that build has not been verified.

Native add-ons remain unsandboxed. Access violations and memory corruption can
still crash the host. Retired DLLs remain mapped until process exit, and unused
cache cleanup is best effort when other programs block deletion. The native
tool-log provider remains disabled; Hammer build-output capture is independent.

Hammer Addons v0.1.0-alpha.4

Load newly installed add-ons and reload compatible DLLs without restarting
Workshop Tools. This release also adds Steam account and friends support.

New features

• Load new add-ons: discover packages installed while the application is
  running from the manager's Add-ons tab.
• Reload selected: replace a running add-on that opts into hot reload.
  Pending jobs or an incomplete DLL build leave the current instance running.
• Reload SDK and example: hammer_reload.h defines the cleanup contract;
  the reload_counter example demonstrates preserving settings across reloads.
  The add-on generator includes a reload_counter template.
• Steam account and friends: the bundled steam_context add-on shows account
  identity, friends and presence, with profile and friends overlay shortcuts
  when available. SDK snapshots and subscriptions are available to add-on authors.

Update

Close Workshop Tools, extract the Windows x64 ZIP outside CS2, and copy your
custom add-on folders into its addons/ directory. Start Launch Workshop
Tools.cmd and choose a project normally. Updating the framework itself still
requires restarting the tools.

In the Workshop Add-ons manager, use Load new add-ons after installing
a package, or select a running add-on and choose Reload selected.
Hammer keeps the manager under Help > Workshop Add-ons.

Existing add-ons remain compatible. Hot reload requires reloadable=true in
the manifest and a valid HA_QueryReload export; other add-ons still need a
restart after updates. The SDK ZIP includes the new header, example source,
and docs/HOT_RELOAD.md.

Limits

• Reload affects the current process. The project picker and editor have
  separate add-on instances.
• Reloadable packages support one DLL plus data files. Retired DLL images stay
  mapped until process exit, with a limit of 32 generations per add-on.
• If cleanup throws or a replacement fails after the previous instance stops,
  correct the package and restart. Reload does not sandbox native code.
• Steam networking and invitations are not implemented. Overlay shortcuts
  depend on availability in the tools session.
• The native logging provider remains disabled. Automatic Hammer build-output
  capture continues to work independently.

Downloads include the portable Windows x64 package, SDK, release metadata and
SHA-256 checksums. Native add-ons run with your Windows permissions; install
only code you trust.

Hammer Addons v0.1.0-alpha.3

This update fixes a crash when closing the Workshop project picker.

• Fixed UI pointer cleanup that could cause heap corruption during window
  teardown, including after opening the add-on manager.
• Picker crashes now report a launch failure and exit code instead of appearing
  as successful cancellation.
• Added regression coverage for pointer lifetime, copied guards and abnormal
  picker exits.

Close Workshop Tools, extract the new Windows x64 ZIP outside CS2, and start
its CMD launcher. Keep your custom add-on folders when updating. Existing
add-ons and the public SDK remain compatible.

The native logging provider remains disabled pending separate verification.
Automatic Hammer build-output capture continues to work independently.

Hammer Addons v0.1.0-alpha.2

This alpha adds project-aware diagnostics and session build history.

• Problems table: repeated build diagnostics are grouped, with first-line
  references, occurrence counts, original messages, and suggested checks for
  recognized resource and sound-operator errors. Zero failure counts are excluded.
• Problem actions: copy an asset path or diagnostic, and reveal an existing
  project-local source file in Explorer.
• Build history: view the latest eight captured builds and compare new/resolved
  messages between complete captures for the same editor window and map title.
• Project context: view the selected Workshop project's folders and find loose
  source files. The SDK exposes this through hammer_project.h.
• SDK tables: create selectable, read-only panel tables with stable row IDs.
  Example sources and the scaffold script include the new capabilities.
• Public installation and contributor documentation has been updated.

Download the Windows x64 ZIP, extract it outside CS2, and launch Workshop Tools
from its CMD file. In Hammer, open Help > Workshop Add-ons > Build log report
and build normally with F9. Close Workshop Tools before updating; keep any custom
add-on folders when transferring them to the new package.

Known limitations: picker heap-corruption crashes remain under investigation;
the native logging provider is disabled. Capture can be partial, and history lasts
only for the current session. Source lookup checks loose files in the selected
project, not VPKs or the full asset dependency graph. Editor context does not expose
unsaved map objects. Radar generation is not included.

Regression coverage includes project-path validation, SDK compatibility, diagnostic
classification, build comparisons, table selection, and the existing loader/UI tests.

Hammer Addons v0.1.0-alpha.1

First public alpha of Hammer Addons for CS2 Workshop Tools.

Download hammer-addons-v0.1.0-alpha.1-windows-x64.zip, extract it outside CS2,
and double-click Launch Workshop Tools.cmd. Choose your project in Valve's
normal picker. The SDK archive contains C headers, example source, and documentation.

• Native add-on loader and shared manager for the project picker and editors.
• Panels, commands, settings, menu hooks, custom import handlers and editor metadata.
• Background jobs, cancellation and queued editor callbacks.
• Automatic Hammer build-output capture and the included Build log report.
  Open Help > Workshop Add-ons > Build log report and compile normally with F9.
• Tested native loader, launcher and Qt integration; real Hammer compilation and
  automatic report delivery verified on the supported CS2 build.

Alpha limitations: picker heap-corruption crashes have been observed and remain
under investigation. The separate native logging provider is disabled. Build-output
capture is independent of it, bounded, and may miss transient output. Diagnostics
are keyword candidates, not a build-success determination. No unsaved scene editing,
multiplayer editing, or radar generation is included in this release.

No Valve DLLs or Qt runtime DLLs are included or replaced. Add-ons execute native
code with your account's permissions; install only trusted add-ons. Licensing of
this project's own code remains undecided; third-party terms are documented separately.

SHA256SUMS.txt covers both downloads and release.json records the source commit.