Haft 9.0.0

Haft 9 builds on the v8 governance-substrate pivot and completes the move to a source-native FPF and typed project-memory substrate used through existing coding agents, the CLI, and MCP.

The v9 release line introduces:

• a smaller governance-only distribution: haft run, haft harness, the complete Open-Sleigh contour, and the Elixir/OTP/BEAM runtime dependency are removed; WorkCommission and RuntimeRunRecord governance, haft commission, haft_commission, and complete-external remain runner-neutral;
• source-native FPF concern retrieval, exact lookup, and inspect projections with explicit provenance and abstention;
• recoverable FPF refresh that can adopt a complete structurally supported upstream publication while preserving parser, semantic, Query, and token findings as explicit release-review diagnostics;
• a fused code and reasoning graph with bounded Explore, code-context, and impact surfaces;
• typed project-memory validation, non-binding admission, exact entity resolution, neighborhood, and recall under a selected project TypeEnv basis;
• automatic, idempotent activation of every bundled ProjectTypeEnv successor proven compatible with the exact current project, without an operator prompt or review carrier; activation audit events record the distinct compatible_successor_policy provenance, while incompatible or stale successors leave the head unchanged;
• project-profile and specification carriers that version FPF source, project-local application, binding authority, and evidence separately;
• a predecessor-pinned profile-relation repair path for specification applicability, with onboarding workflow state kept separate from current specification health;
• stable full integrations for Codex and Claude, including MCP config, transformed skills, and managed project instructions; other host adapters remain explicitly experimental or legacy;
• host instructions in which h-decide routes only a direct, unambiguous operator request, while h-commission remains an explicit manual execution- authority action;
• deterministic archive smoke checks and separate tag-validation and public release-publication gates;
• one full-race owner in CI: local development uses the P13 critical profile by default, and release requires the successful exact-SHA CI aggregate instead of rerunning the same repository-wide suite.

Upgrade from v8.1.0

The published predecessor is v8.1.0; v8.2.0 was never published.

Before the first v9 start, stop all Haft MCP processes and back up both the project .haft/ directory and its global project ledger under ~/.haft/projects/<project-id>/. Re-run haft init for the host targets you use, then fully restart those hosts so every MCP process loads the same v9 binary.

The successful v9 installer removes only the exact Haft-managed legacy runtime at ~/.haft/runtimes/open-sleigh/current. User-owned ~/.open-sleigh/ data and the independent haft-embed runtime are preserved. Calls to the removed haft run and haft harness commands must be migrated to host-agent work or a separately operated external runner; v9 ships no compatibility executor.

Database migration is forward-only for this release boundary. Running v8.1 against a v9-migrated database is unsupported; rollback requires restoring the complete pre-upgrade backup. See MIGRATION-v8.md (github.com) for the full procedure.

Deliberately outside the v9 contract

Dense or hybrid retrieval superiority over a pinned FPF file, ordinary source search, or host RAG remains deferred research. The optional embedding sidecar does not change FPF authority or turn retrieval rank into applicability, selection, recommendation, or evidence.

This committed note describes the release contract; it does not record a P13 or P14 result and is not release authority. Tag validation and public GitHub Release publication are separate operator-controlled actions.