ultra-builder-pro-cli 0.24.0 → 0.24.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.ultra-template/tasks/tasks.json +4 -2
- package/CHANGELOG.md +48 -0
- package/README.md +48 -25
- package/agents/code-reviewer.md +4 -5
- package/agents/debugger.md +8 -8
- package/docs/AGENT-CONTEXT.md +22 -8
- package/docs/ARCHITECTURE.md +30 -9
- package/docs/ARTIFACT-AUTHORITY.md +10 -7
- package/docs/LEGACY-CLI-CROSSWALK.md +1 -1
- package/docs/STATE-DB-ACCESS-POLICY.md +8 -1
- package/docs/WORKFLOW-LIFECYCLE.md +38 -23
- package/hooks/health_check.py +11 -6
- package/mcp-server/lib/artifact-registry.cjs +7 -56
- package/mcp-server/lib/baseline-workflow.cjs +74 -46
- package/mcp-server/lib/change-authority.cjs +26 -0
- package/mcp-server/lib/change-packet.cjs +4 -32
- package/mcp-server/lib/change-workflow.cjs +33 -2724
- package/mcp-server/lib/legacy-change-workflow.cjs +2809 -0
- package/mcp-server/lib/state-ops.cjs +21 -3
- package/mcp-server/lib/task-expander.cjs +6 -1
- package/mcp-server/lib/ultra-facade.cjs +280 -47
- package/mcp-server/server.cjs +1 -1
- package/package.json +1 -1
- package/skills/ultra-change/SKILL.md +2 -1
- package/skills/ultra-deliver/SKILL.md +15 -17
- package/skills/ultra-dev/SKILL.md +3 -1
- package/skills/ultra-doctor/SKILL.md +2 -2
- package/skills/ultra-init/references/brownfield-adoption.md +13 -10
- package/skills/ultra-plan/SKILL.md +10 -8
- package/skills/ultra-research/SKILL.md +8 -4
- package/skills/ultra-review/SKILL.md +6 -4
- package/skills/ultra-test/SKILL.md +6 -4
- package/skills/ultra-think/SKILL.md +3 -2
- package/spec/mcp-tools.yaml +6 -2
|
@@ -19,8 +19,8 @@ Call `ultra.doctor { repair: false }` and inspect:
|
|
|
19
19
|
- projection jobs, sessions, leases, worktrees, and recovery journals;
|
|
20
20
|
- installed plugin assets, MCP startup, and hook paths.
|
|
21
21
|
|
|
22
|
-
An expected workflow pause, editable draft,
|
|
23
|
-
|
|
22
|
+
An expected workflow pause, editable draft, semantic warning, or awaiting owner
|
|
23
|
+
decision is not corruption.
|
|
24
24
|
|
|
25
25
|
## Repair
|
|
26
26
|
|
|
@@ -52,17 +52,20 @@ baseline is ready.
|
|
|
52
52
|
Record every adoption gap with a stable id, evidence references, owner, blocking flag,
|
|
53
53
|
and one category:
|
|
54
54
|
|
|
55
|
-
- `baseline_blocker`:
|
|
55
|
+
- `baseline_blocker`: the model should recommend against adoption until resolved or
|
|
56
|
+
the owner explicitly accepts the recorded risk;
|
|
56
57
|
- `documentation_drift`: maintained prose conflicts with observed behavior;
|
|
57
58
|
- `known_defect`: reproducible incorrect behavior;
|
|
58
59
|
- `technical_debt`: accepted maintainability or quality cost;
|
|
59
60
|
- `unknown`: evidence is insufficient;
|
|
60
61
|
- `future_change`: desired behavior outside the current baseline.
|
|
61
62
|
|
|
62
|
-
Use `open` for unresolved gaps, `accepted` for owner-accepted
|
|
63
|
+
Use `open` for unresolved gaps, `accepted` for owner-accepted debt,
|
|
63
64
|
`resolved` when evidence closes the gap, and `deferred` for explicitly postponed
|
|
64
|
-
|
|
65
|
-
|
|
65
|
+
work. Keep every open `baseline_blocker` visible as a semantic warning. It does not
|
|
66
|
+
become a SQLite hard gate: the model explains the risk, recommends resolution, and may
|
|
67
|
+
record owner-authorized adoption without erasing the gap. Do not convert the ledger
|
|
68
|
+
into hundreds of application tasks.
|
|
66
69
|
|
|
67
70
|
## Record authority
|
|
68
71
|
|
|
@@ -88,9 +91,9 @@ worktree state, and material decisions to the owner. Use `ultra.record` with
|
|
|
88
91
|
`accept_known_red` and `accept_dirty_worktree` only for the exact items the owner
|
|
89
92
|
accepted.
|
|
90
93
|
|
|
91
|
-
Resolve
|
|
92
|
-
|
|
93
|
-
|
|
94
|
-
|
|
95
|
-
|
|
96
|
-
before planning.
|
|
94
|
+
Resolve hard authority blockers, then present semantic warnings for evidence or an
|
|
95
|
+
owner decision. Adoption is complete when `ultra.context` reports a current accepted
|
|
96
|
+
baseline, every material open gap is visible with its owner/risk and any acceptance is
|
|
97
|
+
explicit in the approval note, and project doctor has no mechanical authority failure.
|
|
98
|
+
Route all selected work through `ultra-change`, including work described by a legacy
|
|
99
|
+
plan. Import its accepted intent into a current Change Contract before planning.
|
|
@@ -48,14 +48,16 @@ payload: planning posture, optional approval already obtained, context budget/re
|
|
|
48
48
|
idempotency_key: stable semantic Plan checkpoint id
|
|
49
49
|
```
|
|
50
50
|
|
|
51
|
-
The
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
51
|
+
The model decides whether decomposition, acceptance coverage, and context are
|
|
52
|
+
sufficient and records any deliberate omission. The checkpoint compiles or reuses the
|
|
53
|
+
content-addressed Context Envelope, reports advisory coverage diagnostics, exports
|
|
54
|
+
`plan.json` and `plan.md` inside the same recoverable publication, accepts one Plan
|
|
55
|
+
revision, and publishes the team checkpoint. Do not export separately.
|
|
56
|
+
|
|
57
|
+
If rejected, the same Plan draft stays mutable. Fix only the reported structural,
|
|
58
|
+
digest, path, or concurrency conflict and retry. To replace an accepted Plan, submit a
|
|
59
|
+
new checkpoint revision; never edit SQLite or open a parallel run to escape a
|
|
60
|
+
diagnostic.
|
|
59
61
|
|
|
60
62
|
Return topology, executable slices, public seams, exact checks, checkpoint result, and
|
|
61
63
|
the model's recommended execution order. Do not invoke `ultra-dev` automatically.
|
|
@@ -41,8 +41,9 @@ Use one `ultra.record` batch for typed durable facts:
|
|
|
41
41
|
- `baseline / observe` or `baseline / accept` for baseline authority;
|
|
42
42
|
- `change_contract / revise` for Change-bound findings.
|
|
43
43
|
|
|
44
|
-
Every entry needs a stable idempotency key.
|
|
45
|
-
|
|
44
|
+
Every entry needs a stable idempotency key. Structural or authority conflicts require
|
|
45
|
+
repair; semantic warnings remain visible but do not decide whether the research is
|
|
46
|
+
sufficient.
|
|
46
47
|
|
|
47
48
|
## Commit one research checkpoint
|
|
48
49
|
|
|
@@ -56,8 +57,11 @@ entries, then publish the team checkpoint with `ultra.sync { action: publish }`.
|
|
|
56
57
|
For Change-bound research, keep all findings and delta artifacts below the Change
|
|
57
58
|
root and never edit accepted baseline specs directly.
|
|
58
59
|
|
|
59
|
-
|
|
60
|
-
|
|
60
|
+
The model decides whether the selected coverage and synthesis are sufficient, and
|
|
61
|
+
states omissions or deferred areas in the payload. MCP validates declared evidence
|
|
62
|
+
bytes and records that conclusion; its semantic diagnostics are advisory. If it
|
|
63
|
+
returns `accepted: false`, repair the reported structural, digest, path, or concurrency
|
|
64
|
+
conflict and retry the same draft.
|
|
61
65
|
|
|
62
66
|
Return coverage, decisive evidence, remaining gaps, durable artifact paths, and a
|
|
63
67
|
model recommendation for the next explicit capability, such as `ultra-change` after a
|
|
@@ -34,11 +34,13 @@ Register specialist and summary artifacts through one `ultra.record` batch using
|
|
|
34
34
|
## Checkpoint
|
|
35
35
|
|
|
36
36
|
Call `ultra.checkpoint` once with `stage: review`, exact scope, evidence, and outputs
|
|
37
|
-
tagged `spec_review`, `engineering_review`, or summary. The
|
|
38
|
-
|
|
37
|
+
tagged `spec_review`, `engineering_review`, or summary. The model and bounded review
|
|
38
|
+
agents own both evidence-derived axes. The checkpoint compiles or reuses review
|
|
39
|
+
context, verifies declared artifact bytes and digests, and records the supplied axes
|
|
40
|
+
without overriding findings.
|
|
39
41
|
|
|
40
|
-
A rejected checkpoint leaves the draft mutable. Fix
|
|
41
|
-
do not open a replacement run or suppress a finding.
|
|
42
|
+
A rejected checkpoint leaves the draft mutable. Fix the structural, digest, path, or
|
|
43
|
+
concurrency fault and retry; do not open a replacement run or suppress a finding.
|
|
42
44
|
|
|
43
45
|
Return both axes, findings, reviewed scope, worker rationale, digests, and the model's
|
|
44
46
|
recommended next explicit capability. Do not invoke it automatically.
|
|
@@ -30,11 +30,13 @@ profile, timestamp, blockers, and evidence-derived verdict. Register it with
|
|
|
30
30
|
## Checkpoint
|
|
31
31
|
|
|
32
32
|
Call `ultra.checkpoint` once with `stage: test`, exact scope, evidence, and an output
|
|
33
|
-
for the report (`kind: test-report`). The
|
|
34
|
-
|
|
33
|
+
for the report (`kind: test-report`). The model owns the evidence-derived verdict and
|
|
34
|
+
material exclusions. The checkpoint compiles or reuses checking context, verifies the
|
|
35
|
+
declared report authority and digest, and records that verdict without re-judging it.
|
|
35
36
|
|
|
36
|
-
If rejected, keep the same draft
|
|
37
|
-
assertion, hide a skip, or turn a warning into
|
|
37
|
+
If rejected, keep the same draft and repair the structural, digest, path, or
|
|
38
|
+
concurrency fault. Never weaken an assertion, hide a skip, or turn a warning into
|
|
39
|
+
proof.
|
|
38
40
|
|
|
39
41
|
Return the profile, exact results, verified seams, blockers, report digest, and the
|
|
40
42
|
model's recommended next explicit capability. Do not invoke it automatically.
|
|
@@ -30,8 +30,9 @@ Use one `ultra.record` batch with `decision / accept` and, when required,
|
|
|
30
30
|
`supersedes_id`; accepted records remain immutable history. Store normalized decisions
|
|
31
31
|
and artifact references, never transcripts or internal reasoning.
|
|
32
32
|
|
|
33
|
-
A
|
|
34
|
-
new decision merely to satisfy a state machine.
|
|
33
|
+
A structural or authority rejection remains a mutable diagnostic. Correct the record;
|
|
34
|
+
do not invent a new decision merely to satisfy a state machine. Semantic disagreement
|
|
35
|
+
belongs in the recommendation and visible decision record, not a kernel error.
|
|
35
36
|
|
|
36
37
|
Return the conclusion, decisive evidence, uncertainty, affected authority, and the
|
|
37
38
|
model's recommended next explicit capability. Thinking never performs unrelated
|
package/spec/mcp-tools.yaml
CHANGED
|
@@ -100,7 +100,7 @@ tools:
|
|
|
100
100
|
|
|
101
101
|
- name: ultra.checkpoint
|
|
102
102
|
family: ultra
|
|
103
|
-
description:
|
|
103
|
+
description: Commit one caller-declared stage checkpoint after validating scope, structure, idempotency, current file bytes, digests, and transactional publication. Semantic completeness remains a Skill/model judgment and is returned only as advisory diagnostics.
|
|
104
104
|
phase: '24'
|
|
105
105
|
writer_role: mcp
|
|
106
106
|
input_schema:
|
|
@@ -122,6 +122,10 @@ tools:
|
|
|
122
122
|
- { code: VALIDATION_ERROR, description: 'input failed structural validation' }
|
|
123
123
|
- { code: STATE_CORRUPT, description: 'local authority cannot be checkpointed safely' }
|
|
124
124
|
- { code: PATH_AUTHORITY_VIOLATION, description: 'checkpoint evidence escapes managed authority' }
|
|
125
|
+
- { code: CHECKPOINT_EVIDENCE_AUTHORITY_MISSING, description: 'declared checkpoint evidence is not current managed authority' }
|
|
126
|
+
- { code: CHECKPOINT_EVIDENCE_DIGEST_MISMATCH, description: 'declared checkpoint evidence bytes changed' }
|
|
127
|
+
- { code: CHECKPOINT_SCOPE_NOT_FOUND, description: 'the explicit Task or Change scope does not exist' }
|
|
128
|
+
- { code: CHECKPOINT_SCOPE_MISMATCH, description: 'the explicit Task does not belong to the supplied Change scope' }
|
|
125
129
|
cli_subcommand: 'ultra checkpoint'
|
|
126
130
|
emits_events: [ultra_checkpoint_accepted, ultra_checkpoint_rejected]
|
|
127
131
|
|
|
@@ -168,7 +172,7 @@ tools:
|
|
|
168
172
|
|
|
169
173
|
- name: ultra.archive
|
|
170
174
|
family: ultra
|
|
171
|
-
description:
|
|
175
|
+
description: Archive one caller-declared local Change handoff through a recoverable filesystem and database transaction. The kernel validates authority, paths, digests, reconciliation structure, and recovery safety without requiring a fixed semantic stage sequence.
|
|
172
176
|
phase: '24'
|
|
173
177
|
writer_role: mcp
|
|
174
178
|
input_schema:
|