holycodex 0.16.6-dev.84.1 → 0.16.7-dev.86.1

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.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "holycodex",
3
- "version": "0.16.6",
3
+ "version": "0.16.7",
4
4
  "description": "Root-directed capabilities and deterministic installed assets for HolyCodex.",
5
5
  "author": {
6
6
  "name": "David Basile Filho",
@@ -8,6 +8,10 @@ contract. Check callers, contracts, tests, and generated artifacts. Repair
8
8
  defects inside the review surface and return the findings, repairs, checks, and
9
9
  remaining risk.
10
10
 
11
+ Lead with actionable findings and check evidence. Keep the terminal report
12
+ concise and structured, reuse stable facts, and inspect large artifacts only
13
+ when a material decision, conflict, failure, or finding requires it.
14
+
11
15
  Root dispatches this procedure to the mandatory native `Reviewer.code` route
12
16
  after implementation or a major code change and before completion or VCS. The
13
17
  canonical receiver contract owns the quality and mergeability criteria; this
@@ -6,4 +6,6 @@ description: Use when a caller needs a redacted projection of current Intent sta
6
6
  Produce one compact projection of current Intent, Plan, and Assignment status,
7
7
  evidence, blockers, remaining risk, and the exact next action. Omit secrets,
8
8
  raw prompts, transcripts, and unchanged narration. Handoff is an export view;
9
- the semantic state remains authoritative.
9
+ the semantic state remains authoritative. Lead with observable evidence and
10
+ material decisions, reuse stable facts, and inspect or include large material
11
+ only when a material decision, conflict, failure, or finding requires it.
@@ -7,7 +7,9 @@ Resolve the current material choices into an implementation-ready Plan with
7
7
  scope, owners, seams, data and control flow, policy, recovery, compatibility,
8
8
  acceptance evidence, and a bounded proof route. Keep planning proportional:
9
9
  trivial work can proceed without a Plan. Persist the canonical revision through
10
- the semantic Plan operation.
10
+ the semantic Plan operation. Stable bounded component scopes are the canonical
11
+ ownership boundary; the lifecycle worker owns deterministic Intent, Plan, and
12
+ Assignment API decisions.
11
13
 
12
14
  Root owns material choices and dispatches this procedure through the native
13
15
  `Reviewer.plan` route when adversarial plan review is needed; the skill never