You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Daily maintenance could drift away from the original specification because role context, task freshness, verification seams, and implementation discoveries were not one durable contract. Hooks also injected broad workflow prose while projection-only hosts could accept stale manifests.
This release adds Context Manifest v2, schema 10.0, deterministic breadcrumbs, approval-gated specification learning, and 32 live MCP contracts. It gives every linked task a bounded role/gate packet, required references and digests, a public seam, an exact verification command, and fail-closed readiness. Convergence now requires current task contexts, documentation/spec evidence, exact test seams, and independent spec-fidelity and engineering-standards review.
The seven daily execution workflows are compressed from 1,922 to 758 lines and all twelve public workflows are host-invocable. Claude Code, Codex, OpenCode, and Kimi Code receive native Context Spine rendering; OpenCode rejects legacy or HEAD-stale projections. A shared read-only hook helper replaces duplicated broad context injection.
Compatibility remains additive: the 9.1 to 10.0 migration preserves durable rows and foreign keys; external providers continue to own memory and code graphs; Gemini and RTK remain absent from active runtime, prompt, installer, and documentation surfaces. Rollback is package reinstall to 0.9.0; databases retain additive columns/table and should be backed up before any manual downgrade.
Verification: npm run verify:release (144 Node tests, 21 hook tests, npm audit with 0 vulnerabilities); npm pack --dry-run --json (222 files, all new runtime assets present); git diff --cached --check; MCP system.doctor reports healthy with SQLite integrity ok, zero projection lag, zero open incidents, and external provider ownership.
'- Authority: `.ultra/state.db` is the only durable Ultra authority for changes, tasks, sessions, events, incidents, projection state, telemetry, and review evidence. Generated JSON and Markdown are projections or workflow artifacts.',
63
+
'- Context Spine boundary: `change.context` compiles role/gate readiness, bounded references, fresh-context budget, public seam, verification command, and one next action. Hooks inject only the DB-derived `change.breadcrumb`; stale or blocked context must be recompiled.',
'- Memory and graph boundary: Ultra Builder Pro does not capture prompts, transcripts, observations, summaries, cross-session memory, or code-graph content. Separately installed providers own that data; Ultra may store only their metadata references in a change context manifest.',
64
66
'- Hook boundary: Ultra hooks observe workflow/change lifecycle only. Health/context may run when `.ultra/state.db` exists; projection protection is always authoritative, while edit/compact/stop/subagent enforcement remains active-workflow scoped. Generic command blocking and post-edit policy stay in user or repository governance.',
65
67
'- Installation boundary: `ubp --doctor` is the read-only authority for installed asset provenance, content hashes, and host entry-point wiring; `system.doctor` remains scoped to project state and workflow recovery.',
0 commit comments