HADARA 0.4.6-rc.1

HADARA 0.4.6-rc.1

HADARA 0.4.6-rc.1 is a release-candidate refresh after published 0.4.6-rc.0. It focuses on installed-package dogfood findings, safe concurrent Task Capsule creation, first-user documentation workflow cleanup, and faster HADARA-dev Docker dist refresh before a stable 0.4.6 decision.

Highlights

• Validates the published rc.0 package through installed-package dogfood across multiple scenarios, including delegated toy projects and a larger Quant Battle Arena planning/development scenario.
• Serializes task id allocation and managed Task Board writes so external agents may request task creation concurrently while HADARA applies the actual write safely.
• Keeps fresh init scaffolds smaller and adds hadara docs add <type> for optional project-owned docs:
  • architecture
  • decisions
  • roadmap
  • security-model
  • test-strategy
  • agent-guide
• Updates generated workflow and AGENTS guidance so agents keep generated/project-owned docs/ files current when work changes their subject.
• Splits HADARA-dev Docker helper behavior:
  • npm run dev:docker-sync-build is now a fast minimal build/dist-refresh path with stage timings.
  • npm run dev:docker-check remains the full validation path.

Validation

• Focused task-create serialization, docs-add/init, schema/help, and Docker helper tests passed during the rc.1 preparation line.
• TypeScript builds passed.
• Docker fast sync-build refreshed dist and built CLI smoke reported distLooksStale=false.
• Release package smoke and strict release gate are part of the T-0620 source/readiness capsule.

Boundaries

• This is a prerelease candidate intended for npm next.
• Stable npm latest remains hadara@0.4.5 until a later stable promotion.
• npm publish, GitHub Release publication, token loading, and installed-package recycle remain operator-controlled steps after this source/readiness capsule.
• Post-publish recycle should install hadara@next and verify expected version 0.4.6-rc.1.

HADARA 0.4.6

HADARA 0.4.6

HADARA 0.4.6 is a stable release focused on first-user trust polish, delegated-agent onboarding reliability, safer lifecycle closure, and cleaner project initialization after the 0.4.6 release-candidate line.

Highlights

• Hardened brownfield init adoption:
  • duplicate .gitignore HADARA local-state managed blocks fail closed;
  • package-smoke empty-stdout fallbacks are visible in evidence;
  • best-effort project identity inference covers Node, Python, Cargo, and Go project manifests.
• Improved delegated-agent validation and evidence UX:
  • test and tests are CLI-only aliases for canonical validation evidence;
  • unsupported evidence category errors include allowed tokens, aliases, and schema hints;
  • validation command capture uses file-backed capture and direct-result recovery for process-capture edge cases.
• Cleaned up first-project onboarding:
  • stale bootstrap next-work is retired after the first real capsule closes;
  • init docs tell agents to keep generated/project-owned docs current;
  • optional docs can be added with hadara docs add <type> instead of expanding init profiles.
• Serialized task id allocation and managed Task Board writes so concurrent external agents can request capsules while HADARA applies writes safely.
• Split HADARA-dev Docker validation helpers:
  • npm run dev:docker-sync-build is a fast build/dist-refresh path with stage timings;
  • npm run dev:docker-check remains the full validation path.
• Fixed the stable-blocking first-capsule close boundary found in delegated rc.1 dogfood:
  • task finalize --execute --auto now treats finish writes atomically before close checks;
  • validation placeholder semantics allow deliberate pre-close validation rows;
  • delegated Codex rerun closed both an adoption baseline and a Quant Battle Arena MVP feature capsule without hand-editing lifecycle-owned status fields.

Validation

• 0.4.6-rc.0 and 0.4.6-rc.1 were published and dogfooded before this stable preparation.
• T-0625 reproduced the delegated first-capsule close blocker from a current package candidate.
• T-0626 and T-0627 fixed the close-boundary and validation placeholder issues.
• T-0628 reran delegated Codex dogfood from a clean external governed project and produced valid close proof for both baseline and MVP feature capsules.
• T-0629 refreshed source metadata, release docs, built dist, package smoke, and strict release gate for stable 0.4.6.

Operator Notes

• npm stable target: hadara@0.4.6 on dist-tag latest.
• GitHub Release target: v0.4.6.
• After publication, run installed-package recycle from hadara@latest with expected version 0.4.6.

HADARA 0.4.6-rc.0

HADARA 0.4.6-rc.0

HADARA 0.4.6-rc.0 is a release candidate focused on brownfield trust polish, delegated-agent onboarding friction, validation capture reliability, and current-state contract clarity after stable 0.4.5.

Highlights

• Fails closed on duplicate .gitignore HADARA local-state managed blocks during brownfield adoption.
• Adds package-smoke fallback observability when installed commands exit successfully but stdout capture is empty.
• Improves manifest inference for Python, Cargo, and Go projects, including Go semantic import version suffix handling such as /v2.
• Accepts CLI-only evidence category aliases test and tests, while still persisting canonical validation.
• Improves unsupported evidence category diagnostics with allowed tokens, aliases, and schema lookup hints.
• Hardens validation execution capture for delegated tool environments with file-backed capture and direct-result recovery.
• Retires stale bootstrap next-work recommendations after the first real capsule closes.
• Clarifies current-state semantics:
  • latestCompletedTask means highest Done task id, not close timestamp chronology.
  • validationBaseline means current trusted validation baseline, not necessarily the latest completed task evidence.
• Future-proofs current-state latest-task ordering by comparing task id numeric suffixes.

Validation

• Focused current-state, validation-run, evidence, manifest inference, and package-smoke tests passed across the 0.4.6 line.
• Docker dev sync build/full suite passed through T-0613 with 153 test files and 1108 tests.
• Built CLI dist freshness was verified with distLooksStale=false.

Boundaries

• This is a prerelease candidate intended for npm next.
• Stable npm latest remains hadara@0.4.5 until a later stable promotion.
• npm publish, GitHub Release publication, token loading, and installed-package recycle remain operator-controlled steps after this source/readiness capsule.
• Post-publish recycle should install hadara@next and verify expected version 0.4.6-rc.0.

HADARA 0.4.5

HADARA 0.4.5

HADARA 0.4.5 focuses on safe brownfield adoption, docs-registry cleanup, and release-readiness hardening for existing projects.

Highlights

• Adds docs-registry v3 with clearer lifecycle, role, origin, and profile applicability semantics.
• Adds safe brownfield hadara init adoption: existing projects get a zero-write plan first, then require explicit --adopt --execute --plan-hash <hash> before HADARA writes managed files.
• Fails closed for partial HADARA state, unsafe symlinks, malformed managed markers, path type mismatches, and non-HADARA tasks/T-* collisions.
• Detects meaningful single-file roots as brownfield projects, so small existing repos are not mistaken for greenfield.
• Preserves project-authored docs and existing managed-section ownership during adoption.
• Removes generated tasks/.gitkeep and keeps init scaffolds aligned with the current public command surface.
• Hardens docs-registry mutation commands so failed mutations exit non-zero.
• Validates fresh basic/standard/governed init, governed lifecycle close, installed-candidate brownfield adoption across TypeScript, Python/data, and web/monorepo shapes, plus fail-closed adoption safety paths.
• Fixes the final clean-clone test regressions found before publish: empty scaffold parent directories stay greenfield-safe, and adopted package.json descriptions populate Project State purpose metadata.
• Fixes package-smoke generated-init validation so packaging artifacts do not make the installed hadara init docs check fall into brownfield zero-write mode.

Boundaries

This release prepares npm latest publication for hadara@0.4.5. npm publish and GitHub Release publication remain operator-approved actions. Post-publish installed-package recycle should be handled in a follow-up capsule after publication.

HADARA 0.4.4

HADARA 0.4.4

Stable release for the 0.4.4 external/delegated dogfood and generated-document currentness line.

Highlights

• Promotes the 0.4.4-rc.0 line after npm/GitHub prerelease publication, installed-package recycle, stable-promotion verification, and final major CLI dogfood.
• Keeps the fresh-project UX fixes validated across delegated/basic, external/standard, and Claude-governed dogfood runs.
• Improves generated project behavior around version aliases, stale installed-package diagnostics, bootstrap next-work retirement, consumer context-pack guidance, finish-only status hints, and governed handoff scaffolds.
• Uses existing package.json metadata during hadara init while preserving docs doctor warnings for projects that leave product metadata unset after completed task history exists.
• Fixes a final state-projection false positive from T-0582: legacy docs/DEVELOPMENT_SLICES.md is not treated as latest-task authority unless canonical .hadara/state/slices.json exists.

Validation

• 0.4.4-rc.0 was published and recycled from hadara@next.
• T-0581 rechecked npm/GitHub RC metadata and installed-package recycle before stable promotion.
• T-0582 exercised major CLI paths before stable: repo read models, commands, help, schema, docs doctor, status, task status, release diagnostics, fresh basic/standard/governed init, and a governed toy lifecycle through validation evidence and task finalize --execute --auto.
• T-0582 fix validation passed focused state-projection tests, TypeScript build, Docker full suite, docs doctor, and status --state-only.

Boundaries

• This stable release does not add provider execution, a cloud service, scheduler/background runner, vector retrieval, dashboard productization, installer execution, Docker image publishing, PyPI publishing, or MCP release/package mutation.
• Post-publish installed-package recycle for hadara@latest expected 0.4.4 remains the next follow-up after npm/GitHub publication.

HADARA 0.4.4-rc.0

HADARA 0.4.4-rc.0

Release candidate for the external/delegated dogfood hardening line after stable 0.4.3.

Highlights

• Validates HADARA in external project shapes before release: delegated basic-profile dogfood, standard-profile external validation, and an independent Claude Code governed-profile run that completed 8 Task Capsules.
• Fixes fresh-project continuation drift found by dogfood: bootstrap "first task" guidance now retires after real task history, generated governed handoff no longer starts with empty completed-task tables, and Product metadata can be initialized from package metadata.
• Improves installed/consumer CLI UX: conventional -v behavior, non-HADARA-root version freshness diagnostics, generated read ranges, context-pack guidance, and finish-only status hints.
• Clarifies closed task status output by separating valid close proof from skipped fast-path done-level checks.
• Keeps the primary workflow unchanged: task status, task create, validation run / evidence add-command, and guarded task finalize.

Validation Line

• T-0572 defined the v0.4.4 external-repository validation plan.
• T-0573 through T-0577 ran delegated/external dogfood across basic, standard, and governed profiles.
• T-0575 and T-0578 fixed the dogfood findings selected for pre-release cleanup.
• T-0579 prepares this prerelease source/readiness state and leaves npm/GitHub mutation to the operator publish flow.

Boundaries

• npm publish should use the next tag for 0.4.4-rc.0.
• Stable latest remains hadara@0.4.3 until a later stable promotion decision.
• Docker image publish, PyPI publish, installer execution, MCP release/package execution, and post-publish installed-package recycle are out of scope for this release-preparation capsule.
• After publication, run a separate installed-package recycle capsule against hadara@next expected 0.4.4-rc.0.

HADARA 0.4.3

HADARA 0.4.3

Stable release for the 0.4.3 current-state, session-resume, and fresh-init dogfood hardening line.

Highlights

• Adds structured .hadara/state/current.json as the compact source for current release, latest/active task, next work, current problems, and validation baseline, with managed Project State and Agent Handoff projections.
• Makes new sessions resume from current state and session start without reconstructing project history from long-form historical docs.
• Replaces loose next-intent prose with a structured next-work contract so status/session guidance can distinguish candidate work from operator guidance.
• Adds explicit currentness diagnostics through docs doctor --json and drift checks for structured canon, Markdown projections, Task Board, onboarding versions, and removed-command references.
• Measures the primary workflow across basic, standard, and governed profiles while keeping the core workflow surface frozen at four command ids and six post-init calls.
• Fixes fresh-init dogfood regressions before stable publish: stale first-task recommendations, HADARA-dev validation command leakage, too-short generated TASK.md read ranges, and finish-only status guidance.
• Keeps HADARA scoped as a local-first evidence control plane; full controller/provider/cloud-worker expansion remains deferred.

Verification Line

• T-0565 completed non-deployment 0.4.3 source readiness: local tarball install, artifact/package/clean-checkout smokes, strict gate, release dry-run, and installed local-tarball workflow evidence.
• T-0566 through T-0569 completed current-state/session contract cleanup, structured next-work cleanup, fresh-init dogfood, and post-dogfood UX regression fixes.
• T-0570 prepares this stable publish path and leaves npm/GitHub mutation to the approval-gated operator release scripts.

Boundaries

• npm publish uses the latest tag for 0.4.3.
• Docker image publish, PyPI publish, installer execution, MCP release/package execution, and external multi-repository validation remain out of scope.
• After publish, run a separate installed-package recycle capsule against hadara@latest expected 0.4.3.

HADARA 0.4.2

HADARA 0.4.2

Stable release for the 0.4.2 command-surface reduction, status performance, init structure, and stable-preflight dogfood line.

Highlights

• Promotes the 0.4.2-rc.0 command portfolio cleanup: retired public command surfaces and stale redirect stubs stay removed, while current workflow guidance stays centered on task status, task finalize, validation run, and evidence list/add-command.
• Improves status/read-model performance with faster default status output, explicit full/detail modes, and invocation-local selected-task read memoization.
• Keeps task finalize --execute --auto as the ordinary guarded close path, with close-plan blockers detected before partial finish writes.
• Adds response-only evidence append-lock diagnostics and preserves direct-result validation recovery for restricted agent environments.
• Fixes stable-preflight dogfood issues from the published RC line: consumer context pack source/release-warning leakage, empty-project first-task guidance, similar handoff-to-open-task matching, EOF slice truncation semantics, and validation recovery guidance.
• Adds final profile-aware cleanup: basic and standard projects do not warn about optional missing docs/AGENT_HANDOFF.md, and task-selection required-reading recommendations only include docs present in the project profile.

Verification Line

• 0.4.2-rc.0 was published on npm with next and released as a public GitHub prerelease.
• RC installed-package recycle passed from consumer paths.
• Installed toy-project dogfood covered basic, standard, and governed profiles.
• Stable-preflight source dogfood rerun in T-0544 confirmed the prior findings stayed fixed and closed a governed toy task through the current workflow.
• Stable source preparation in T-0545 retargets metadata/docs to 0.4.2 and leaves npm/GitHub publication as explicit operator actions.

Boundaries

• npm publish uses the latest tag for 0.4.2.
• 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@latest expected 0.4.2.

HADARA 0.4.2-rc.0

HADARA 0.4.2-rc.0

Release candidate for the post-0.4.1 cleanup line: command-surface reduction, status/read-model performance, init structure, finalize/evidence UX hardening, dead-code cleanup, and fresh-project dogfood.

Highlights

• Removes retired public command surfaces and command-era dead code after the 0.4.1 cleanup line.
• Keeps task status and task finalize as the primary lifecycle while stale lifecycle hints now point to current commands.
• Improves selected-task status performance with invocation-local read memoization and keeps top-level status fast by default.
• Splits init implementation internals without changing generated project behavior.
• Hardens task finalize --execute --auto against partial finish writes when close blockers remain.
• Adds response-only evidence append-lock diagnostics.
• Fixes session-start docs read-map preview count parity.
• Dogfoods a fresh governed project through init, generated docs review, validation/direct-result recovery, auto finalize, removed-route checks, docs doctor, doctor, schema, and context surfaces.

Verification Line

• T-0538 refreshed development dist with Docker sync-build and passed full Vitest 148 files / 1002 tests.
• T-0538 fresh /tmp dogfood closed toy task T-0001 as closed-valid.
• T-0539 source preparation retargets package metadata and release-facing docs to 0.4.2-rc.0.

Boundaries

• npm publish should use the next tag for 0.4.2-rc.0.
• Stable latest remains hadara@0.4.1.
• Docker image publish, PyPI publish, installer execution, MCP release/package execution, and installed-package recycle are out of this source-preparation capsule.
• After publish, run a separate installed-package recycle capsule against hadara@next expected 0.4.2-rc.0.

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 --auto as 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 replacementCommand fields, while task status and task finalize own 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.md state/projection prototype as 0.4.x scope, without adopting the full 0.5 state-first RFC.

Verification Line

• 0.4.1-rc.0 was published on npm with next and 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 status and does not fall back to removed task lifecycle when the installed command surface supports the current path.
• Stable source preparation in T-0516 retargeted metadata/docs to 0.4.1 and leaves npm/GitHub publication as explicit operator actions.

Boundaries

• npm publish uses the latest tag for 0.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@latest expected 0.4.1.