ultra-builder-pro-cli 0.24.0 → 0.24.2

package/.ultra-template/tasks/tasks.json

@@ -1,13 +1,15 @@
 {
   "kind": "ultra-team-task-ledger",
-  "schema_version": "1.0",
+  "schema_version": "2.0",
   "generation": 0,
   "parent_digest": null,
   "ancestors": [],
-  "state_digest": "5bf27fb3627b711c97abf72f0aad150ba693d35bcebdd57c2d80e325f495de6d",
+  "state_digest": "88098433d797125bb0f87068a01205cf378494169ca93ee2a9dcf15c1c83dd63",
   "published_at": null,
   "reason": "scaffold",
   "baseline": null,
   "changes": [],
+  "decisions": [],
+  "checkpoints": [],
   "tasks": []
 }

package/CHANGELOG.md

@@ -7,6 +7,54 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.24.2] — 2026-07-31
+
+### Changed
+
+- Made the production Change facade single-mode and Kernel-only. The pre-v0.24
+  Change implementation is explicitly isolated for compatibility, while retired
+  workflow and dialogue rows remain read-only history with no public artifact owner
+  or invalidation writer.
+- Made review and debug agents evidence-only: delegated workers can write only their
+  assigned report, while the primary host owns source remediation and final judgment.
+
+### Fixed
+
+- Preserved rejected semantic calls as bounded `ultra_kernel_attempt` audit history
+  visible through `ultra.context`, without creating the rejected semantic authority.
+- Renamed misleading `_ultra.state_commit` response metadata to
+  `_ultra.projection_commit`; projection processing no longer resembles a semantic
+  acceptance receipt.
+- Removed current Change-packet decisions and artifact invalidation from retired
+  workflow/dialogue tables while retaining safe migration and historical reads.
+
+## [0.24.1] — 2026-07-31
+
+### Changed
+
+- Kept semantic completeness, route selection, baseline sufficiency, and delivery
+  acceptance in Skills and the host model. The MCP kernel now records those conclusions
+  as advisory diagnostics while retaining hard failures only for structural authority,
+  current bytes, digests, scope ownership, concurrency, permissions, and recovery.
+- Made local delivery follow the evidence required by the actual Change route. Explicit
+  omissions and their rationale are preserved without imposing a fixed
+  Plan/Dev/Test/Review sequence on every archive.
+- Made completed Tasks explicitly reopenable without erasing their prior completion
+  commit or accepted history.
+
+### Fixed
+
+- Fixed nonexistent or mismatched Task/Change checkpoint scopes creating ghost
+  checkpoint authority; invalid scopes now fail before any Context or checkpoint write.
+- Fixed shallow or contradictory evidence declarations being accepted without checking
+  current managed artifact authority and stable file bytes.
+- Fixed baseline semantic gaps, missing optional research, and `not_run` verification
+  being misrepresented as mechanical authority failures.
+- Fixed installed Change revision paths depending on source-only semantic supervisor
+  modules excluded from the npm package.
+- Fixed Hooks, Skills, templates, and packaged documentation disagreeing about advisory
+  diagnostics, adaptive delivery, and the persistence/safety-kernel boundary.
+
 ## [0.24.0] — 2026-07-30
 
 ### Added

package/README.md

@@ -48,8 +48,10 @@ Ultra Builder Pro addresses those gaps with four ideas:
    recovery state across host sessions. Tracked semantic artifacts plus the
    MCP-published `.ultra/tasks/tasks.json` checkpoint carry reviewed project intent
    across Git checkouts without committing SQLite, leases, or telemetry.
-4. **Convergent delivery.** Research, plans, implementation, tests, review, and
-   specification updates must agree before a change is archived.
+4. **Adaptive delivery.** The host model evaluates the evidence produced by the
+   actual Change route, explicitly records any omitted capability and its rationale,
+   and asks the owner to accept the local handoff. MCP validates current managed
+   authority and archive integrity rather than requiring a fixed stage sequence.
 
 For example, if the user asks an agent to add organization SSO to an existing
 application, Ultra helps the agent inspect the real authentication path, capture
@@ -103,14 +105,14 @@ The responsibility split is deliberate:
 |---|---|
 | **User** | Product intent, semantic route selection, material scope and trade-offs, risk acceptance, destructive actions, publishing and deployment authorization |
 | **Host model** | Fact-finding, synthesis, research-coverage and route recommendations, reversible implementation decisions |
-| **Ultra MCP** | Structure validation, durable checkpoints, evidence references, digests, team sync, leases, archive transactions, and mechanical recovery; never semantic route selection |
+| **Ultra MCP** | Structure/current-byte validation, caller-declared checkpoints, evidence references, digests, team sync, leases, archive transactions, and mechanical recovery; never semantic completeness or route selection |
 | **Host adapter** | Native Skill discovery, user questions, tool invocation, installation, and runtime wiring |
 | **Hooks** | Fast lifecycle observation, current breadcrumb injection, and protection of MCP-owned checkpoint and generated projection paths |
 
-The MCP does not replace the model's judgment or pre-authorize a semantic route. It
-reports draft diagnostics and commits accepted checkpoints. A hook does not decide
-product strategy. A prompt does not become durable authority merely because it
-appeared in a conversation.
+The MCP does not replace the model's judgment, judge completion, or pre-authorize a
+semantic route. It reports diagnostics and safely commits the model's explicit
+checkpoint/archive handoff. A hook does not decide product strategy. A prompt does not
+become durable authority merely because it appeared in a conversation.
 
 ### The seven-tool MCP kernel
 
@@ -120,16 +122,21 @@ The public model-facing surface is intentionally small:
 |---|---|
 | `ultra.context` | Read the complete current spine without side effects |
 | `ultra.record` | Batch typed draft facts and events with idempotency |
-| `ultra.checkpoint` | Attempt one semantic stage checkpoint; rejection leaves the draft editable |
+| `ultra.checkpoint` | Commit one caller-declared stage checkpoint after structural, byte, digest, and publication validation |
 | `ultra.sync` | Inspect, import, or publish the Git team checkpoint |
 | `ultra.session` | Own the transactional execution lease |
-| `ultra.archive` | Converge and archive through the recoverable filesystem/DB boundary |
+| `ultra.archive` | Persist one explicit local delivery handoff through the recoverable filesystem/DB boundary |
 | `ultra.doctor` | Inspect or repair mechanical health, backup first |
 
 Retired fine-grained operation names are neither discoverable nor callable. Workflow
 prose stays in Skills, model judgment stays with the host, and SQLite records what
 happened rather than deciding what the model is allowed to think next.
 
+Rejected semantic attempts remain visible as bounded `ultra_kernel_attempt` audit
+diagnostics in the next `ultra.context`; they do not create rejected authority.
+`_ultra.projection_commit` describes only generated-view processing, never semantic
+acceptance. The production Change API has no legacy/current mode switch.
+
 The enforcement gradient is:
 
 ```text
@@ -283,7 +290,7 @@ resolves observable facts itself and asks for material product decisions as
 needed. Once the evidence and specifications are accurate, the user approves
 the baseline.
 
-The common path after baseline approval is:
+One common full-depth path after baseline approval is:
 
 ```text
 ultra-change
@@ -295,11 +302,14 @@ ultra-change
   -> ultra-deliver
 ```
 
-Each public workflow is explicitly invoked rather than auto-chained. Thinking and
-research coverage are adaptive, and verification depth is risk-selected, but every
-Change reaches a current plan, DB-backed task contract, and role-scoped context before
-development. “Direct Build” skips Research only; it does not bypass Plan, Task, or
-Context authority.
+Each public workflow is explicitly invoked rather than auto-chained. The example is a
+recommended route for a normal implementation Change, not an archive state machine.
+Thinking and research coverage are adaptive, verification depth is risk-selected, and
+the host may omit or repeat a capability when the actual Change makes that appropriate,
+provided the delivery handoff names the omission and its rationale. Any implementation
+task still requires a current plan, DB-backed task contract, and role-scoped context.
+“Direct Build” skips Research only; it does not bypass Plan, Task, or Context authority
+when development is performed.
 
 ### 2. Adopt an existing project
 
@@ -365,9 +375,12 @@ must be reconciled against the current Change authority.
 
 ### 4. Deliver and continue
 
-`ultra-deliver` verifies that implementation, acceptance evidence, testing,
-review findings, specification learning, and baseline reconciliation agree. It
-then archives the local Ultra change authority.
+`ultra-deliver` asks the host model to assess the current managed evidence for the
+route the Change actually took. The handoff explicitly records any omitted capability
+and its evidence-based rationale; the owner decides whether that semantic packet is
+sufficient. MCP then validates paths, digests, reconciliation structure, idempotency,
+and recoverability before archiving the local Ultra change authority. It does not
+require every Change to pass through a fixed Research/Plan/Dev/Test/Review sequence.
 
 Delivery does **not** grant permission to commit, push, publish, tag, deploy, or
 perform another external effect. Those actions remain separate and require the
@@ -396,6 +409,11 @@ recommends the next capability from current context and owner intent; SQLite doe
 encode the semantic route. Another public capability starts only after an explicit
 user command or skill invocation.
 
+Review and debug agents are evidence-only workers. They may inspect the assigned
+checkout and write their declared report, but they never edit source or commit
+authority. The primary host evaluates the evidence, applies any repair, and records
+the verified outcome.
+
 ### Command interaction graph
 
 Every solid handoff below means: the current capability returns context and checkpoint
@@ -430,11 +448,16 @@ flowchart TD
     PLAN --> DEV["ultra-dev<br/>one dependency-ready vertical task"]
     DEV --> TASKS{"More executable tasks?"}
     TASKS -->|"Yes"| DEV
-    TASKS -->|"No"| TEST["ultra-test<br/>risk-selected formal verification"]
+    TASKS -->|"No"| ASSESS{"What evidence does this Change still need?"}
+    ROUTE -->|"Accepted handoff already has sufficient evidence"| DELIVER["ultra-deliver"]
+    ASSESS -->|"Risk-selected verification"| TEST["ultra-test<br/>risk-selected formal verification"]
+    ASSESS -->|"Independent review"| REVIEW["ultra-review<br/>specification fidelity and engineering quality"]
+    ASSESS -->|"Caller accepts current evidence and explicit omissions"| DELIVER
     TEST -->|"Failed or incomplete"| DEV
-    TEST -->|"Passing"| REVIEW["ultra-review<br/>specification fidelity and engineering quality"]
+    TEST -->|"Review is warranted"| REVIEW
+    TEST -->|"Caller accepts current evidence and explicit omissions"| DELIVER
     REVIEW -->|"Changes required"| DEV
-    REVIEW -->|"Approved"| DELIVER["ultra-deliver"]
+    REVIEW -->|"Approved"| DELIVER
     DELIVER --> ARCHIVE["Reconcile specifications<br/>apply the Change overlay and archive evidence"]
     ARCHIVE --> NEXT{"Continue"}
     NEXT -->|"Next outcome"| CHANGE
@@ -586,10 +609,10 @@ host's existing model session.
   any real conflict. Never edit `.ultra/tasks/tasks.json` by hand.
 - **A generated view disagrees with MCP:** trust `.ultra/.runtime/state.db`; never edit
   `.ultra/.runtime/projections/` by hand.
-- **A draft checkpoint is rejected:** use `ultra-status` to read the exact warnings
-  and blockers, fix the same mutable draft, and retry. If the attempt is no longer
-  relevant, leave it as history and open a new draft revision; no hidden workflow
-  state must be cancelled first.
+- **A draft checkpoint reports warnings:** the model keeps them visible and decides
+  whether to investigate, revise, defer with rationale, or accept. If a checkpoint is
+  rejected for a structural, digest, path, publication, or concurrency conflict, fix
+  the same mutable draft and retry; no hidden workflow state must be cancelled first.
 - **Kimi reports a native-module ABI error:** ensure an external Node.js 22+
   executable is available on `PATH`; the generated Kimi MCP launcher uses
   `env node`.

package/agents/code-reviewer.md

@@ -1,7 +1,7 @@
 ---
 name: code-reviewer
 description: Review an explicit diff or file set for consequential correctness, security, integration, test, and maintainability defects. Use for a bounded read-only review before commit, merge, or release.
-tools: Read, Grep, Glob, Bash, Write, Edit
+tools: Read, Grep, Glob, Bash, Write
 model: opus
 maxTurns: 30
 skills:
@@ -34,10 +34,9 @@ evidence. Default to read-only analysis.
 
 ## Mutation boundary
 
-Do not edit during an ordinary review. If the parent explicitly assigns review and
-fix, modify only findings within the accepted scope, preserve unrelated changes, and
-rerun the checks invalidated by each edit. Judgment-heavy or scope-expanding fixes
-return to the primary agent for a decision.
+Do not edit source. Write only the assigned evidence artifact. If remediation is
+authorized, return the smallest verified repair instructions to the primary host,
+which owns implementation and final judgment.
 
 Use the current checkout and parent-supplied packet only. Do not call Ultra MCP write
 tools. Return a concise review, not raw tool output.

package/agents/debugger.md

@@ -1,7 +1,7 @@
 ---
 name: debugger
-description: Find the earliest incorrect state behind an error, test failure, or unexpected behavior and return a minimal verified fix when implementation is authorized.
-tools: Read, Write, Edit, Bash, Grep, Glob
+description: Find the earliest incorrect state behind an error, test failure, or unexpected behavior and return bounded evidence plus a minimal verified remediation.
+tools: Read, Write, Bash, Grep, Glob
 model: opus
 maxTurns: 40
 ---
@@ -24,14 +24,14 @@ that violates the intended contract.
    distinguishes it from alternatives.
 5. Test the hypothesis without broad refactoring. Record evidence that accepts or
    rejects it.
-6. If implementation is authorized, write a regression test that fails for the
-   observed defect, apply the minimum root-cause fix, and rerun focused and adjacent
-   checks.
-7. Report the symptom, evidence trail, root cause, changed files when any, exact
+6. Describe the smallest regression test and root-cause repair that the primary host
+   should apply. Do not edit source.
+7. Report the symptom, evidence trail, root cause, proposed files, exact diagnostic
    verification, and residual uncertainty.
 
-Do not change code when the assignment is diagnosis-only. Do not use a passing test
-from another checkout as evidence.
+Write only the assigned evidence artifact. Do not change source, even when remediation
+is authorized; the primary host owns implementation and final judgment. Do not use a
+passing test from another checkout as evidence.
 
 If three distinct fix attempts expose different underlying failures, stop patching and
 return the evidence as an architectural boundary problem. For an Ultra incident, also

package/docs/AGENT-CONTEXT.md

@@ -11,7 +11,7 @@ Ultra owns:
   `ultra-change`, `ultra-plan`, `ultra-dev`, `ultra-test`, `ultra-review`,
   `ultra-deliver`, `ultra-status`, and `ultra-doctor`;
 - four internal worker-rule Skills;
-- bounded review/debug workers;
+- bounded evidence-only review/debug workers;
 - deterministic workflow Hooks;
 - exactly seven public MCP tools;
 - `.ultra` project authority, team sync, recovery, and the portable installer.
@@ -52,6 +52,12 @@ diagnostics and leaves the draft editable. Hard errors are limited to corruption
 unsafe paths, digest/CAS/lease conflicts, missing runtime prerequisites, permissions,
 and irreversible external effects.
 
+A rejected semantic attempt is appended as `ultra_kernel_attempt` audit history and
+appears alongside the next `ultra.context` envelope without changing its semantic
+digest. It never creates the rejected semantic row or claims that authority was
+committed. `_ultra.projection_commit` reports only the post-call generated-view cycle;
+it is not a semantic acceptance receipt.
+
 ## Context Envelope
 
 Every Skill begins by reading `ultra.context` for the relevant stage and scope. The
@@ -95,15 +101,17 @@ If the host mode forbids interaction, leave the decision unresolved.
 
 ## Stage Checkpoints
 
-Skills describe adaptive evidence expectations; SQLite does not authorize a fixed
-step sequence. A stage has a mutable draft and immutable accepted revisions:
+Skills describe adaptive evidence expectations and decide semantic sufficiency;
+SQLite does not authorize a fixed step sequence or reinterpret the supplied verdict.
+A stage has a mutable draft and immutable accepted revisions:
 
 ```text
 draft N -> accepted N -> superseded by accepted N+1
 ```
 
-Warnings and semantic gaps do not lock a draft. An accepted revision can be replaced
-by a later accepted revision without rewriting history.
+Warnings and semantic gaps do not reject explicit acceptance. Structural, digest,
+path, publication, and concurrency conflicts leave the draft mutable. An accepted
+revision can be replaced by a later accepted revision without rewriting history.
 
 ## Worker handoff
 
@@ -119,9 +127,10 @@ The packet binds:
 - exact output path;
 - `packet_digest`.
 
-Workers may inspect and write only the declared output. They do not write SQLite,
-accept checkpoints, modify another worker's result, or decide final delivery. Output
-must echo `packet_digest`; the primary host verifies and records it.
+Workers may inspect the assigned checkout and write only the declared evidence output.
+They do not edit source, write SQLite, accept checkpoints, modify another worker's
+result, or decide final delivery. Output must echo `packet_digest`; the primary host
+verifies it, performs any source repair, and records the resulting evidence.
 
 ## Hook boundary
 
@@ -161,3 +170,8 @@ state.
 
 Every semantic file must have one writer, owner, consumer, digest, promotion gate, and
 archive rule as defined in `ARTIFACT-AUTHORITY.md`.
+
+The production Change API has one Kernel behavior and exposes no legacy/current mode
+switch. Pre-v0.24 workflow and dialogue rows remain read-only migration/audit history:
+the public kernel cannot create workflow-owned artifacts or mutate those rows during
+current invalidation.

package/docs/ARCHITECTURE.md

@@ -43,7 +43,8 @@ There is no second semantic authority:
 - MCP owns structure validation, idempotency, digests, CAS, leases, safe paths,
   filesystem journals, recovery, and accepted checkpoints.
 - Hooks own deterministic observation and bounded injection only.
-- Agents receive one immutable Worker Packet and write only the declared output.
+- Agents receive one immutable Worker Packet and write only the declared evidence
+  output; the primary host owns every source change and final judgment.
 
 SQLite never chooses the next capability and never requires a fixed sequence of
 reasoning steps. Semantic gaps appear in `diagnostics`, `warnings`, or
@@ -59,16 +60,18 @@ Every host discovers exactly seven tools:
 |---|---|
 | `ultra.context` | Side-effect-free, bounded Context Envelope read |
 | `ultra.record` | Typed, idempotent recording of facts, decisions, artifacts, tasks, outcomes, and observations |
-| `ultra.checkpoint` | Reversible draft validation and immutable accepted Stage Checkpoint |
+| `ultra.checkpoint` | Caller-declared Stage Checkpoint with structural, scope, byte, digest, and publication validation |
 | `ultra.sync` | Inspect, migrate, import, or publish the Git team checkpoint |
 | `ultra.session` | Lease/worktree acquisition plus immutable Worker Packet handoff |
-| `ultra.archive` | Crash-safe delivery convergence and immutable archive |
+| `ultra.archive` | Crash-safe caller-declared local handoff and immutable archive |
 | `ultra.doctor` | Mechanical diagnosis and backup-first repair |
 
 Retired fine-grained tool names are not registered and return `UNKNOWN_TOOL`. The
-source repository retains migration readers and regression fixtures for old authority,
-but those modules are excluded from the npm distribution and have no live public
-consumer.
+source repository retains migration readers, an explicitly named internal Change
+compatibility implementation, and regression fixtures for old authority. The
+production Change facade exposes one Kernel behavior with no mode flag; retired
+semantic supervisors are excluded from the npm distribution and no public call can
+write their workflow/dialogue authority.
 
 ## Canonical Context Envelope
 
@@ -119,8 +122,10 @@ draft N -> accepted N -> superseded by accepted N+1
 ```
 
 There is no fixed step authorization table. Skills decide which evidence is relevant
-to the actual work. Checkpoint validation verifies declared facts, files, digests, and
-scope; an incomplete draft remains mutable.
+and whether the actual work is semantically sufficient. Checkpoint validation verifies
+declared facts, files, digests, scope, idempotency, and safe publication. Semantic
+warnings remain recorded but do not prevent an explicit caller acceptance; a hard
+authority conflict leaves the draft mutable.
 
 ### Worker Packets
 
@@ -128,6 +133,20 @@ Every delegated worker receives a digest-bound packet containing the exact Conte
 Envelope, accepted decisions, Git boundary, Task contract, acceptance, evidence
 references, output path, and output schema. The worker must echo `packet_digest`.
 Workers do not write SQLite or accept their own result.
+Review and debug workers do not edit source; their only mutation is the assigned
+evidence artifact, and the primary host applies any accepted remediation.
+
+### Rejected attempts and projection metadata
+
+Semantic diagnostics do not disappear when a caller corrects and retries. A rejected
+public call appends an `ultra_kernel_attempt` event containing the typed operation,
+scope, idempotency key, blockers, and diagnostics without storing raw prompts or
+creating the rejected semantic row. `ultra.context` exposes a bounded recent view of
+that audit history alongside, but outside the digest-bound semantic envelope.
+
+Server metadata uses `_ultra.projection_commit` only for the deterministic
+post-mutation projection job. It must never be interpreted as proof that a semantic
+record, checkpoint, or archive was accepted.
 
 ## `.ultra` storage planes
 
@@ -208,7 +227,9 @@ Contexts, and v0.22/v0.23 database and ledger authority.
 Migration is inspectable, exact-byte backup-first, transactional, and fail-closed on
 conflict. Old workflow and dialogue rows are retained as non-authoritative history;
 current Context, Decisions, Checkpoints, and the team ledger are rebuilt from verified
-facts. No user should edit SQLite or move a legacy file manually to recover.
+facts. Current artifact invalidation may traverse legacy graph edges to reach a live
+Task, but it never rewrites the legacy workflow row. No user should edit SQLite or move
+a legacy file manually to recover.
 
 ## External boundaries
 

package/docs/ARTIFACT-AUTHORITY.md

@@ -44,7 +44,7 @@ these surfaces independently owns all three roles.
 |---|---|---|
 | Owner | Goals, acceptance, non-goals, material choices, risk acceptance, and authorization for irreversible or external effects | Supply facts the checkout or runtime can establish directly |
 | Host model | Inspect evidence, recommend a route, ask only for unresolved owner choices, normalize the answer, call the owning write, update semantic artifacts, read back the result, and present the next recommendation | Fabricate evidence, infer owner authorization, or bypass mechanical safety |
-| Ultra MCP | Persist normalized inputs, validate structure and current digests, record facts and provenance, commit Stage Checkpoints, project local views, publish/import the Git checkpoint, and expose recovery | Choose product direction, prove a UI click, pre-authorize reasoning steps, force a semantic route, or replace model judgment |
+| Ultra MCP | Persist normalized inputs, validate structure/current bytes/digests, record facts and provenance, commit caller-declared Stage Checkpoints, project local views, publish/import the Git checkpoint, and expose recovery | Judge semantic completeness, choose product direction, prove a UI click, pre-authorize reasoning steps, force a semantic route, or replace model judgment |
 | Host adapter | Render the shared interaction contract through the host-native question and tool surfaces | Become a second workflow authority |
 | Hook | Observe lifecycle, inject compact DB-derived recovery context, and protect MCP-owned checkpoint and generated projection paths | Select a semantic route or block ordinary development |
 
@@ -112,11 +112,13 @@ document's before/after digest, delta and acceptance references, verification, a
 verified consumer or explicit no-consumer reason. Standard and major delivery require
 one current reconciliation even when its document set is empty.
 
-`change.archive` preflights the complete target set before writing, applies overlay
-bytes through a recoverable local transaction, refreshes baseline digests, moves the
-complete Change root to its archive location, and rebinds registry paths. A conflict,
-crash, or DB failure must roll back or resume the whole packet; no subset is reported
-as delivered.
+The Deliver Skill owns the evidence-based semantic handoff and records any deliberate
+stage omission. `change.archive` does not infer completeness or require a fixed
+Plan/Dev/Test/Review/Deliver sequence. It preflights the caller-declared target set
+before writing, validates reconciliation structure, applies overlay bytes through a
+recoverable local transaction, refreshes baseline digests, moves the complete Change
+root to its archive location, and rebinds registry paths. A conflict, crash, or DB
+failure must roll back or resume the whole packet; no subset is reported as delivered.
 
 ## Context and plan authority
 
@@ -141,7 +143,8 @@ A current plan is a Change-owned pair:
   task contracts.
 
 The Plan checkpoint selects both paths from the owning Change and accepts no arbitrary
-output path. It binds the JSON digest and the preceding `plan/planning` snapshot;
+output path. The model owns decomposition and semantic coverage. MCP binds the JSON
+digest and the preceding `plan/planning` snapshot;
 the artifact registry records both plan files with that context provenance. Publication
 preflights both path authorities and prior digests, rejects symlinked ancestors or
 targets, and journals the two file replacements so a registry or event failure restores

package/docs/LEGACY-CLI-CROSSWALK.md

@@ -29,7 +29,7 @@ contract and adds stronger authority, recovery, or portability.
 | Development uses isolated Git work, TDD, verification, review, commit, and integration | `ultra-dev`, `session.*`, and the session runner create real worktrees and retain task/review/commit evidence | Preserved and strengthened. Process exit cannot complete a task; uncommitted or unintegrated worktrees cannot be deleted. |
 | Test checks wiring, acceptance, regression, build, performance, security, and failures | `ultra-test` emits a change-bound immutable report covering each applicable dimension | Preserved and strengthened with HEAD, context, task-set, and report-digest validation. |
 | Review challenges specification fidelity and engineering quality | `ultra-review` is a first-class stage with independent specification and engineering axes | Strengthened. A coordinated summary cannot replace either complete axis. |
-| Delivery verifies clean readiness, documentation, build, and evidence | `ultra-deliver` requires current tasks, test, review, learning resolution, reconciliation, a local archive, and an immutable report | Preserved and strengthened. Publish, deploy, push, and other external effects remain separate explicitly authorized operations. |
+| Delivery verifies clean readiness, documentation, build, and evidence | `ultra-deliver` assesses the explicitly accepted evidence packet for the actual Change route, records deliberate omissions, reconciles current managed authority, and creates a recoverable local archive and immutable report | Preserved without a fixed stage gate and strengthened by path, digest, reconciliation, idempotency, and recovery validation. Publish, deploy, push, and other external effects remain separate explicitly authorized operations. |
 | Status restores the current workflow position | `ultra-status` reads DB authority, Git, sessions, artifacts, decisions, allowed transitions, and any hard recovery requirement | Strengthened. The host recommends the semantic route; projections and Prompt prose cannot override state. |
 | Thinking synchronizes owner and Agent intent | `ultra-think` plus `decision.*` persists one-question dialogue, non-ceremonial completion, and optional artifact checkpoints | Strengthened. Observable facts are resolved first; only load-bearing owner choices block. |
 

package/docs/STATE-DB-ACCESS-POLICY.md

@@ -40,6 +40,8 @@ It does not grant lifecycle authority: external writers use the published observ
 allowlist, while lifecycle event
 names are emitted only inside the mutation that owns the corresponding state change.
 Consumers must verify mutable rows rather than infer success from an event name.
+Rejected semantic calls are recorded as `ultra_kernel_attempt` observations and shown
+by `ultra.context`; they do not create the rejected row or authorize a transition.
 
 ## 2. Connection discipline
 
@@ -80,7 +82,7 @@ resolve the mount/runtime constraint before retrying.
 | `decision_records` | MCP server through `ultra.record`; normalized accepted intent and applied references are stored, never UI receipts, prompts, or transcripts |
 | `stage_checkpoints` | MCP server through `ultra.checkpoint`; mutable drafts and immutable accepted/superseded revisions, never fixed reasoning steps |
 | `context_envelopes`, `worker_packets` | MCP server through `ultra.context`, `ultra.checkpoint`, and `ultra.session`; exact digest-bound handoff authority |
-| `decision_threads`, `decision_items`, `workflow_runs`, `workflow_steps` | legacy history retained for migration and audit; no current public writer or authorization role |
+| `decision_threads`, `decision_items`, `workflow_runs`, `workflow_steps` | read-only legacy history retained for migration and audit; no current public writer, invalidation mutation, or authorization role |
 | `artifacts`, `artifact_edges` | MCP server through `ultra.record` and checkpoint-owned registration |
 | `context_snapshots`, `spec_learning_candidates`, `trace_links` | MCP server through `ultra.record` and `ultra.checkpoint` |
 | `incidents`, `projection_jobs`, `event_consumers`, `circuit_breaker` | MCP server; backup-first doctor recovery may perform only documented mechanical transitions |
@@ -124,6 +126,11 @@ performs semantic import, publication, or conflict selection.
   than the orchestrator's boot-time WAL detector.
 - **No raw SQL in command md files.** Commands call MCP tools or
   `ultra-tools …` subcommands; the SQL lives in `mcp-server/lib`.
+- **No legacy authority mode switch.** Public Change callers use the single Kernel
+  facade. New workflow-owned artifacts and workflow/dialogue writes are rejected.
+- **No semantic meaning in projection metadata.** `_ultra.projection_commit` means
+  only that the generated-view job was durably enqueued and processed; acceptance is
+  read from the typed tool result and current authority.
 - **No `vacuum` / `wal_checkpoint(TRUNCATE)` from inside a transaction.**
   Maintenance subcommands open their own connection.
 

package/docs/WORKFLOW-LIFECYCLE.md

@@ -15,19 +15,24 @@ flowchart TD
     RESEARCH --> THINK["ultra-think when a material decision remains"]
     THINK --> RESEARCH
     RESEARCH --> CHANGE["ultra-change"]
-    CHANGE --> ROUTE{"Evidence sufficient?"}
-    ROUTE -->|"No"| CR["bounded ultra-research"]
-    CR --> PLAN["ultra-plan"]
-    ROUTE -->|"Yes"| PLAN
+    CHANGE --> ROUTE{"What does this Change actually need?"}
+    ROUTE -->|"Evidence gap"| CR["bounded ultra-research"]
+    CR --> ROUTE
+    ROUTE -->|"Implementation"| PLAN["ultra-plan"]
     PLAN --> DEV["ultra-dev for one owned Task"]
     DEV --> MORE{"More executable Tasks?"}
     MORE -->|"Yes"| DEV
-    MORE -->|"No"| TEST["ultra-test"]
+    MORE -->|"No"| ASSESS{"What evidence is still warranted?"}
+    ROUTE -->|"No implementation; current evidence is sufficient"| ASSESS
+    ASSESS -->|"Risk-selected verification"| TEST["ultra-test"]
+    ASSESS -->|"Independent review"| REVIEW["ultra-review"]
+    ASSESS -->|"Caller accepts current packet and explicit omissions"| DELIVER["ultra-deliver"]
     TEST -->|"implementation gap"| DEV
-    TEST -->|"evidence accepted"| REVIEW["ultra-review"]
+    TEST -->|"review warranted"| REVIEW
+    TEST -->|"caller accepts evidence"| DELIVER
     REVIEW -->|"implementation issue"| DEV
     REVIEW -->|"contract issue"| PLAN
-    REVIEW -->|"accepted"| DELIVER["ultra-deliver"]
+    REVIEW -->|"accepted"| DELIVER
     DELIVER --> CHANGE
     STATUS["ultra-status"] -.-> INIT
     STATUS -.-> CHANGE
@@ -35,10 +40,12 @@ flowchart TD
     DOCTOR -.-> CHANGE
 ```
 
-The graph is guidance, not database authorization. A quick, well-understood Change may
-skip extra research, but it still needs an explicit Plan, Task contract, Context,
-verification, review, and delivery evidence. `ultra-status` is read-only.
-`ultra-doctor` repairs mechanical authority only.
+The graph is guidance, not database authorization. The host model selects the evidence
+needed by the actual Change route and records every deliberate omission in the delivery
+handoff. When implementation occurs, its Plan, Task contract, and Context remain
+mandatory execution authority; Research, Test, and Review are used according to the
+actual evidence and risk rather than as universal archive gates. `ultra-status` is
+read-only. `ultra-doctor` repairs mechanical authority only.
 
 ## Shared command contract
 
@@ -99,10 +106,12 @@ draft revision N
   -> accepted revision N+1 supersedes N
 ```
 
-A failed acceptance returns diagnostics and keeps the same draft mutable. Plan export
-is part of Plan checkpoint publication, so changing a Task contract before acceptance
-cannot invalidate an already-recorded “export step.” There is no locked intermediate
-run to cancel or manually repair.
+Semantic diagnostics remain recorded but do not reject the model's explicit
+checkpoint conclusion. A structural, digest, path, publication, or concurrency
+conflict keeps the same draft mutable. Plan export is part of Plan checkpoint
+publication, so changing a Task contract before acceptance cannot invalidate an
+already-recorded “export step.” There is no locked intermediate run to cancel or
+manually repair.
 
 Accepted checkpoints are immutable evidence. New facts create a replacement draft.
 Only archive history is terminal; subsequent product work opens a new Change.
@@ -118,9 +127,11 @@ active -> archived
 ```
 
 `blocked`, `ready`, and `needs_attention` are derived diagnostics, not absorbing Change
-states. An active Change may be revised. Archive requires complete current Task,
-Context, test, review, documentation, and delivery checkpoints, then performs a
-recoverable filesystem/DB transaction. Archived bytes remain immutable.
+states. An active Change may be revised. The Deliver Skill inspects the relevant Task,
+Context, test, review, documentation, and delivery evidence, decides semantic
+sufficiency, and records deliberate omissions. Archive validates the explicit handoff,
+current authority, reconciliation structure, and safe recoverable filesystem/DB
+transaction without enforcing a fixed stage sequence. Archived bytes remain immutable.
 
 Older `ready` or `blocked` rows are readable migration history. They do not authorize
 new work until migration/revalidation derives current checkpoint authority.
@@ -130,14 +141,18 @@ new work until migration/revalidation derives current checkpoint authority.
 Task durable outcomes remain portable:
 
 ```text
-pending -> completed
-   |
+pending -> in_progress -> completed
+   |          |              |
+   |          -> blocked     -> in_progress (explicit reopen)
    -> blocked
    -> cancelled
 ```
 
 `in_progress`, Worker ownership, leases, PIDs, heartbeats, worktrees, and completion
 commit backfill are checkout-local. They are not published to Git.
+Reopening a completed Task clears the local completion/session fields, preserves the
+prior completion commit in an append-only `task_reopened` event, and requires a new
+durable outcome before it can be completed again.
 
 `ultra.session acquire` atomically:
 
@@ -210,6 +225,6 @@ Only these classes fail the tool call:
 - permission failure;
 - archive/publish/deploy or another irreversible external-effect failure.
 
-Evidence gaps, incomplete exploration, stale optional context, missing reports, or a
-checkpoint that is not yet ready are structured diagnostics. The model remains free to
-investigate, revise, and retry.
+Evidence gaps, incomplete exploration, stale optional context, missing reports, or
+other semantic insufficiency are structured diagnostics. The model remains responsible
+for investigating, revising, accepting, or explicitly recording an omission.