HADARA 0.4.1
HADARA 0.4.1
Stable release for the 0.4.1 dogfood hardening line after 0.4.1-rc.0 prerelease publication, installed-package recycle, helper refactor, and post-recycle adaptive dogfood.
Highlights
- Promotes
task finalize --execute --autoas the ordinary guarded close path while preserving dry-run review, close-source hashing, blocker refusal, and stale-plan mismatch protection. - Keeps removed low-level lifecycle surfaces behind structured redirect stubs with
replacementCommandfields, whiletask statusandtask finalizeown the primary lifecycle. - Adds schema/vocabulary lookup, stronger controlled-token diagnostics, and docs-registry correction paths.
- Improves restricted-environment validation through
validation run --direct-result. - Adds package-smoke command-surface drift checks and package recycle behavior that adapts to the installed command surface.
- Promotes the bounded
DEVELOPMENT_SLICES.mdstate/projection prototype as 0.4.x scope, without adopting the full 0.5 state-first RFC.
Verification Line
0.4.1-rc.0was published on npm withnextand released as a public GitHub prerelease.- RC installed-package recycle passed from consumer paths.
- Post-refactor adaptive recycle dogfood verified that package recycle uses
task statusand does not fall back to removedtask lifecyclewhen the installed command surface supports the current path. - Stable source preparation in T-0516 retargeted metadata/docs to
0.4.1and leaves npm/GitHub publication as explicit operator actions.
Boundaries
- npm publish uses the
latesttag for0.4.1. - Docker image publish, PyPI publish, installer execution, MCP release/package execution, and full 0.5 state-first adoption remain out of scope.
- After publish, run a separate installed-package recycle capsule against
hadara@latestexpected0.4.1.