ultra-builder-pro-cli 0.25.1 → 0.26.1

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

@@ -0,0 +1,94 @@
+# 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. -->
+
+**Change Acceptance IDs**: [`AC-1`, `AC-3`, or `none` for task-local-only work]
+
+- [ ] `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`
+
+**Hard Constraints**: [`HC-1`, `HC-3`, or `none` — the north-star constraints this
+task could plausibly violate. Read them before the first edit and again before
+marking complete. Crossing one stops the work and goes to the owner, however good
+the argument.]
+
+**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,101 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.26.1] — 2026-08-03
+
+### Added
+
+- Added reframing to `ultra-grilling`, five bounded framing questions, and checkable
+  resolved, stalled, and unavailable exits so a literal request can be translated
+  into the role and outcome the owner actually means.
+- Added `HC-<n>` hard-constraint identifiers, task-level constraint mapping,
+  executable Change verification, and a supported `changes/abandoned/` exit.
+- Added owner-authorized cross-model-family review for major or security-relevant
+  Changes, plus optional native fan-out inside independent research and test regions.
+
+### Changed
+
+- Made `ultra-dev` converge on each task's mapped Change acceptance IDs, track the
+  best-ever passing set, and stop after two no-progress rounds or three repair rounds.
+- Expanded delivery reconciliation to every repository document and kept its wiring
+  gate local to an explicitly invoked `ultra-deliver`; ordinary npm lifecycle commands
+  never depend on project `.ultra/` evidence.
+- Made `ultra-change` read relevant archive history before opening intent, preferring
+  `delivery.md` while supporting legacy archive summaries and verification records.
+- Made all six review lenses the default and required every skipped lens to preserve
+  its reason in the aggregate result.
+
+### Fixed
+
+- Prevented delegated workers from modifying `.ultra/`, including when `.` grants the
+  rest of an isolated checkout.
+- Made dangerous-command authorization reachable by hashing the protected effect
+  independently of its retry spelling.
+- Kept additive protected-branch publication on the host's native authority path instead
+  of hard-blocking an already owner-authorized release, retained exact-digest guards for
+  history rewrites and branch deletion, and stopped treating inert searches as effects.
+- Kept expandable interpreter heredocs inside dangerous-effect inspection while
+  continuing to treat quoted commit-message heredocs as data.
+- Required explicit owner authority before `ultra-review` can launch a cross-host
+  model-family recheck.
+- Bound `ultra-dev` convergence to the active Change acceptance IDs, with explicit
+  stalled and unreachable exits instead of an open-ended repair loop.
+- Made `ultra-change` recover archived intent from legacy archive evidence when the
+  preferred delivery record is absent.
+- Kept the `ultra-deliver` wiring gate local to an owner-invoked delivery workflow;
+  ordinary package commands remain independent of project `.ultra/` state.
+- Added the missing `changes/abandoned/` template directory and migrated completed WIP
+  evidence links to their canonical runtime document.
+
+### Verified
+
+- Completed an authenticated Claude-to-Codex continuation on one isolated
+  file-first task: Claude banked the failing test and Resume Note without changing
+  implementation, and Codex resumed from Git plus `.ultra/`, reached green, and
+  closed the ledger and canonical evidence without conversation transfer.
+- Verified the release candidate with 111 Node tests, 10 Hook tests, 14 Skill Creator
+  validations, five healthy host Doctor reports, and zero audit vulnerabilities.
+
+## [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
@@ -1127,7 +1222,18 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   skill manifest, CLI protocol + mapping table; 5 spec validators.
 - **Phase 0 — skeleton**: multi-runtime installer scaffolding.
 
-[Unreleased]: https://github.com/rocky2431/ultra-builder-pro-cli/compare/v0.20.0...HEAD
+[Unreleased]: https://github.com/rocky2431/ultra-builder-pro-cli/compare/v0.26.1...HEAD
+[0.26.1]: https://github.com/rocky2431/ultra-builder-pro-cli/compare/v0.26.0...v0.26.1
+[0.26.0]: https://github.com/rocky2431/ultra-builder-pro-cli/compare/v0.25.1...v0.26.0
+[0.25.1]: https://github.com/rocky2431/ultra-builder-pro-cli/compare/v0.25.0...v0.25.1
+[0.25.0]: https://github.com/rocky2431/ultra-builder-pro-cli/compare/v0.24.2...v0.25.0
+[0.24.2]: https://github.com/rocky2431/ultra-builder-pro-cli/compare/v0.24.1...v0.24.2
+[0.24.1]: https://github.com/rocky2431/ultra-builder-pro-cli/compare/v0.24.0...v0.24.1
+[0.24.0]: https://github.com/rocky2431/ultra-builder-pro-cli/compare/v0.23.0...v0.24.0
+[0.23.0]: https://github.com/rocky2431/ultra-builder-pro-cli/compare/v0.22.0...v0.23.0
+[0.22.0]: https://github.com/rocky2431/ultra-builder-pro-cli/compare/v0.21.1...v0.22.0
+[0.21.1]: https://github.com/rocky2431/ultra-builder-pro-cli/compare/v0.21.0...v0.21.1
+[0.21.0]: https://github.com/rocky2431/ultra-builder-pro-cli/compare/v0.20.0...v0.21.0
 [0.20.0]: https://github.com/rocky2431/ultra-builder-pro-cli/compare/v0.19.1...v0.20.0
 [0.19.1]: https://github.com/rocky2431/ultra-builder-pro-cli/compare/v0.19.0...v0.19.1
 [0.19.0]: https://github.com/rocky2431/ultra-builder-pro-cli/compare/v0.18.0...v0.19.0