Bind Boatstack delivery authority to repository readiness

[bigboateng]

What changed

• Runs Git/worktree readiness before schema-v3 approval and repeats it at activation, binding the plan, base/head commits, branch/upstream relation, and journey manifest to approval receipts and immutable locks.
• Adds required plan-level journey decisions, fingerprinted journey-oracle manifests, record-journey-results, and manifest/head/diff-bound journey enforcement at test and review gates.
• Replaces the global repair budget with independent implementation, verification, and review counters, requires a repair mechanism in the CLI, and rejects identical class/evidence/mechanism retries as friction.
• Attributes readiness, repair class, journey discovery, and authorization freshness in positive J-flow gaps with the specified 1/3 cost classes.
• Updates exported host instructions, templates, workflow/configuration docs, public projection coverage, and release note 2026-07-29-readiness-and-journey-control.md.

Why

Approval previously could precede the branch/worktree freshness proof, journey failures could be discovered after implementation authority was granted, and one shared retry counter mixed unrelated failure classes. This change makes readiness a prerequisite to authority and makes journey and retry evidence attributable and replay-safe.

Compatibility

• Plan schemas v1/v2, approval receipts v1/v2, and active lock schemas v1/v2 remain readable.
• New plans use schema v3 and require journey_evidence.
• Delivery state v1 migrates conservatively to v2 by applying its existing repair_attempt to every typed counter.
• Post-activation publication validates the immutable lock, so committing an already-authorized working-tree representation does not require reapproval.

Validation

• go build ./...
• go vet ./...
• go test -count=1 -timeout=300s ./...
• python3 -m unittest tests.test_product_loop
• python3 labs/12-product-engineering-loop/scripts/release_notes.py validate --root labs/12-product-engineering-loop/boatstack-distribution/release-notes
• python3 labs/12-product-engineering-loop/scripts/release_notes.py preflight --repo . --base-branch main

Boundary conformance covers positive, negative, relation, bypass, failure-state, replay/fingerprint, and compatibility paths for readiness, journey evidence, repair authority, and J-flow attribution.