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.
@@ -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, failed semantic checkpoint, or awaiting
23
- owner decision is a warning, not corruption.
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`: prevents trustworthy adoption;
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 non-blocking debt,
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
- non-blocking work. Every open `baseline_blocker` remains blocking. Do not convert the
65
- ledger into hundreds of application tasks.
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 returned blockers through evidence or an owner decision, record the replacement
92
- snapshot, and retry. Adoption is complete only when `ultra.context` reports a current
93
- accepted baseline, the gap ledger has no open blocker, and project doctor has no
94
- authority failure. Route all selected work through `ultra-change`, including work
95
- described by a legacy plan. Import its accepted intent into a current Change Contract
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 checkpoint compiles or reuses the content-addressed Context Envelope, derives
52
- coverage diagnostics, exports `plan.json` and `plan.md` inside the same recoverable
53
- publication, accepts one Plan revision, and publishes the team checkpoint. Do not
54
- export separately.
55
-
56
- If rejected, the same Plan draft stays mutable. Fix task contracts or evidence and
57
- retry. To replace an accepted Plan, submit a new checkpoint revision; never edit
58
- SQLite or open a parallel run to escape a diagnostic.
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. A semantic rejection is a mutable
45
- diagnostic: correct the same draft and retry.
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
- If the checkpoint returns `accepted: false`, keep the same draft mutable, repair the
60
- reported evidence, and retry. Do not manufacture evidence or open a replacement run.
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 checkpoint compiles or
38
- reuses review context and derives both axes from registered artifacts.
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 stale scope or evidence and retry;
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 checkpoint compiles or reuses checking
34
- context and derives the verdict from the registered report.
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, repair evidence, and retry. Never weaken an
37
- assertion, hide a skip, or turn a warning into proof.
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 semantic rejection remains a mutable diagnostic. Correct the record; do not invent 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
@@ -100,7 +100,7 @@ tools:
100
100
 
101
101
  - name: ultra.checkpoint
102
102
  family: ultra
103
- description: Attempt one semantic stage checkpoint. Failed semantic checks return blockers and leave the draft mutable; accepted checkpoints commit durable authority once.
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: Converge and archive one accepted Change through the recoverable filesystem and database transaction boundary.
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: