ultra-builder-pro-cli 0.25.0 → 0.26.0

package/.ultra-template/contexts/TEMPLATE.md

@@ -0,0 +1,87 @@
+# Task {id}: {title}
+
+> **Status**: pending | **Priority**: {priority} | **Complexity**: {complexity}
+
+<!-- Status here and in tasks.json must always match. Both are written together, then both
+     are read back to confirm. A single-sided write breaks cross-host resume. -->
+
+## Context
+
+**What**: [what to build or change]
+
+**Why**: [business value, linked to a Persona and Scenario in specs/product.md]
+
+**Constraints**:
+- [constraint 1]
+- [constraint 2]
+
+## Implementation
+
+**Target Files**:
+- `path/to/file.ts` (create)
+- `path/to/existing.ts` (modify: description)
+
+**Layers touched**: [entry point / use case / domain / persistence — must be ≥2]
+
+**Pattern**: [existing code to follow]
+
+**Tech Notes**: [framework or library specifics]
+
+## Acceptance Criteria
+
+<!-- The verifiable definition of done. Read by mid_workflow_recall and session_context, and
+     injected into agent context — keep every line testable and keep noise out. -->
+
+- [ ] `exact test command`
+- [ ] Pass: [scenario 1]
+- [ ] Pass: [scenario 2]
+- [ ] Integration: [the one test proving this connects to its upstream/downstream boundary]
+
+<!-- Manual verification, deliberately outside the injected section:
+     curl -X POST localhost:3000/api/example -->
+
+## Definition of Drift
+
+<!-- What would count as drifting from this task's intent? Catches scope creep early. -->
+
+- [e.g. "splitting this into two services" — out of scope unless the owner agrees]
+- [e.g. "adding a caching layer" — out of scope]
+
+## Trace
+
+**Source**: `.ultra/specs/product.md#section-id`
+
+**Decisions**: [relevant `.ultra/decisions/<id>.md` entries, or `none`]
+
+## Change Log
+
+| Date | Classification | Change | Specs updated | Reason |
+|------|----------------|--------|---------------|--------|
+| {created_date} | — | Initial creation | — | Generated by ultra-plan |
+
+<!-- Classification is EXPANSION, CORRECTION, or REDUCTION. REDUCTION requires owner approval
+     before the spec is touched. See PHILOSOPHY C5. -->
+
+## Open Questions
+
+<!-- Question, its consequence, who owns it, and what evidence would resolve it. -->
+
+- _(none)_
+
+## Resume Note
+
+<!-- The single most important line for cross-session and cross-host continuation.
+     Overwrite it whenever work pauses. Say where to pick up, not what was done. -->
+
+_(not started)_
+
+## Completion
+
+> _Fill when the task is complete._
+
+- **Completed**: {date}
+- **Commit**: {hash}
+- **Summary**: {what was delivered}
+
+---
+*Generated by ultra-plan*

package/.ultra-template/decisions/.gitkeep

@@ -0,0 +1 @@
+

package/.ultra-template/evidence/.gitkeep

@@ -0,0 +1 @@
+

package/.ultra-template/north-star.md

@@ -0,0 +1,46 @@
+# Project North Star
+
+> **Authority**: the owner's literal intent for this project, kept short enough to re-inject every
+> session. Every task must trace back here.
+>
+> **Scope**: only what cannot be derived from `specs/product.md`. Success metrics,
+> excluded features, actors and scenarios stay in that file — do not copy them here.
+
+---
+
+## One-line
+
+<!-- ONE sentence, in the owner's own words, describing what they want.
+     Captured by ultra-init, or from the owner's first request.
+     Do not paraphrase into product-speak: specs/product.md holds the processed version.
+     The value of this line is that it is the unprocessed baseline you check the
+     processed version against. -->
+
+_(not yet defined — run `ultra-init`, or the first owner request will populate this)_
+
+---
+
+## Hard Constraints
+
+<!-- What must never happen, even when convenient. These are prohibitions, not technical
+     constraints — architecture.md holds those. Examples:
+     - Never store plaintext passwords
+     - Cannot break backwards compatibility with API v1
+     - Bundle stays under 500 KB
+     - External API cost stays under $X/month -->
+
+_(not yet defined)_
+
+---
+
+## Notes for agents
+
+1. Re-anchor on the One-line — that is the literal owner request. When the spec and this line
+   disagree, the spec drifted.
+2. Check Hard Constraints before any "improvement". An improvement that violates a constraint is
+   a regression.
+3. If your current work does not trace back here, **stop and ask**. You may be building the
+   wrong thing.
+
+The One-line is injected by `session_context` at SessionStart. `mid_workflow_recall`
+re-injects the active task acceptance before relevant tool use. See PHILOSOPHY C1.

package/.ultra-template/research/.gitkeep

@@ -0,0 +1 @@
+

package/.ultra-template/specs/discovery.md

@@ -6,7 +6,7 @@ copying provider payloads or research transcripts.
 ## Scope
 
 - Repository or product boundary:
-- Baseline id and revision:
+- Inspected Git revision and dirty boundary:
 - Decision this evidence must unlock:
 - Freshness boundary:
 
@@ -67,7 +67,7 @@ decision. Include source date, segment, geography, and assumptions when applicab
 
 ## Baseline Gaps
 
-Reference authoritative gap ids from `.ultra/.runtime/state.db`.
+Assign stable ids here and cite the repository evidence that exposed each gap.
 
 | Gap id | Category | Status | Evidence | Owner |
 |---|---|---|---|---|

package/.ultra-template/tasks.json

@@ -0,0 +1,3 @@
+{
+  "tasks": []
+}

package/.ultra-template/test-report.json

@@ -0,0 +1,27 @@
+{
+  "$schema": "ultra-test-report-v1",
+  "change_id": null,
+  "task_ids": [],
+  "git_commit": null,
+  "worktree": {
+    "dirty": null,
+    "diff_digest": null
+  },
+  "commands": [],
+  "areas": {
+    "anti_patterns": {"status": "not_run", "evidence_refs": [], "omissions": ["Not yet run"]},
+    "coverage_gaps": {"status": "not_run", "evidence_refs": [], "omissions": ["Not yet run"]},
+    "wiring": {"status": "not_run", "evidence_refs": [], "omissions": ["Not yet run"]},
+    "e2e": {"status": "not_run", "evidence_refs": [], "omissions": ["Not yet run"]},
+    "performance": {"status": "not_run", "evidence_refs": [], "omissions": ["Not yet run"]},
+    "security": {"status": "not_run", "evidence_refs": [], "omissions": ["Not yet run"]}
+  },
+  "verified_seams": [],
+  "findings": [],
+  "omissions": ["Not yet run"],
+  "residual_risks": [],
+  "owner_disposition": [],
+  "passed": false,
+  "run_count": 0,
+  "timestamp": null
+}

package/CHANGELOG.md

@@ -7,6 +7,55 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.26.0] — 2026-08-01
+
+### Added
+
+- Added `ultra-delegate`, five source-backed CLI profiles, and a background worker with
+  bounded instruction, permission, worktree, logs, and three terminal result states.
+- Added five file-first hooks for session context, acceptance recall, compact recovery,
+  mechanical evidence observation, and exact-command dangerous-effect protection.
+
+### Changed
+
+- Rebuilt the product around fourteen portable Skills: eight owner workflows, five
+  model-invoked disciplines, and one router. Repository files and Git are now the
+  complete cross-session and cross-host authority.
+- Replaced all five host adapters with managed, provenance-checked file-first plugin
+  artifacts and isolated install/doctor/update/uninstall behavior.
+- Moved rule-side research, review, TDD, and autonomy material into focused Skill
+  references and reduced the project skeleton to one canonical `.ultra-template/`.
+
+### Removed
+
+- Removed the MCP server, SQLite runtime dependency, workflow state machine,
+  orchestrator, operational CLI, command projections, custom-agent projections, and
+  their obsolete schemas and tests.
+
+### Fixed
+
+- Made `--config-dir` the isolation home for Codex plugin and personal-marketplace
+  sidecars, and registered the plugin through Codex with the same isolated `HOME` and
+  `CODEX_HOME`, preventing sandbox installs from mutating the real home directory.
+- Namespaced multi-host `--config-dir` installs by runtime so one host cannot replace
+  another host's `skills/` or `plugins/` tree.
+- Made failed Codex registration restore the previous managed plugin and marketplace,
+  or remove a fresh partial install.
+- Rejected project-escaping task context and spec paths before hooks read them.
+- Rejected delegated writable roots outside the named worktree and readable roots
+  outside the current project before launching another CLI.
+- Restored independent plan, development-evidence, and final-wiring checks so a locally
+  green layer cannot stand in for an end-to-end product path.
+
+## [0.25.1] — 2026-07-31
+
+### Fixed
+
+- Published state-migration lock ownership atomically from a fully written and
+  synchronized candidate inode, so concurrent Node 22 processes cannot mistake a
+  valid publication or release window for a malformed lock. Stable malformed locks
+  remain fail-closed.
+
 ## [0.25.0] — 2026-07-31
 
 ### Added