holycodex 0.16.2-dev.64.1 → 0.16.3-dev.66.1

package/dist/assets/plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "holycodex",
-  "version": "0.16.2",
+  "version": "0.16.3",
   "description": "Root-directed capabilities and deterministic installed assets for HolyCodex.",
   "author": {
     "name": "David Basile Filho",

package/dist/assets/plugin/skills/code-review/SKILL.md

@@ -7,17 +7,10 @@ Use this skill once after implementation or manifest work. Inspect the actual
 integrated result to a fixed point before Root judges readiness. Apply
 [testing quality](../testing-quality.md) when judging new or modified tests.
 
-Owner: Reviewer. Boundary: inspect the assigned diff, callers, contracts,
-tests, compatibility, and artifact. Repair only reviewer-owned defects inside
-scope, verify each repair, and repeat until no assigned defect remains. Root
-retains architecture, product, scope, trust, interface, external-state, and
-final readiness decisions.
+Inspect the assigned diff, callers, contracts, tests, compatibility, and
+artifact. Repair defects inside the review surface, verify each repair, and
+repeat until the review reaches a fixed point.
 
-Use existing code and project conventions before adding code; prefer
-standard-library or native behavior; trace callers before judging a shared root
-cause; and flag speculative abstractions, pointless file splits, oversized or
-unmergeable diffs, unclear dependency direction, and unnecessary tests.
-Check that temporary/generated output is absent and Git/VCS remains Root-only.
-
-Completion: no reviewer-owned defect remains, verification evidence is
-recorded, and every residual risk or Root decision is explicit.
+Flag speculative abstractions, pointless file splits, oversized changes,
+unclear dependency direction, and tests that protect implementation detail.
+Confirm incidental generated output is absent before stopping.

package/dist/assets/plugin/skills/programming/SKILL.md

@@ -3,33 +3,9 @@ name: programming
 description: Use when Root has decided a seam and assigns bounded implementation, fixes, tests, or manifests with known acceptance behavior.
 ---
 
-Implement only the assigned seam. Inspect required callers and tests, preserve
-typed boundaries and portability, edit only approved files, and make one
-bounded clarity pass.
-
-Prefer existing project conventions and standard-library or native behavior.
-Trace every caller before repairing a shared root cause. Reuse an existing
-boundary when it has real callers or clear near-term value; do not add
-speculative abstractions or split a cohesive file without a concrete benefit.
-Keep the smallest correct, independently mergeable diff with deliberate error
-handling and sensible dependency direction. Git/VCS work remains Root-only.
-
-Before checking a change, discover the repository's own formatter, linter,
-typecheck, and validation commands from its package scripts, task config, and
-contributor guidance. Run the smallest relevant local command first, then
-broaden only when the changed boundary or release gate requires it; report
-which commands were unavailable instead of inventing replacements.
-
-When implementation changes tests, apply [testing quality](../testing-quality.md)
-before adding or retaining them: protect a meaningful stable behavior at the
-least brittle observable boundary, and avoid tests for implementation detail.
-Remove temporary or incidental generated output before handoff. Escalate
-material choices.
-
-Owner: Worker. Boundary: preserve repository-native ownership, dependency
-direction, trust checks, and acceptance behavior; do not broaden scope or
-delegate.
-
-Completion: the requested behavior and focused proof are present, changed
-files are inspected, diagnostics and proportional checks pass, and structured
-evidence names residual risk or a precise blocker.
+Implement the decided seam inside the assigned files. Inspect the callers and
+tests needed to preserve its behavior and typed boundaries, then add focused
+proof at the least brittle observable boundary. Discover the repository's own
+validation commands and run the smallest relevant check first; broaden when
+the changed boundary or release gate requires it. Inspect changed files and
+remove incidental generated output before stopping.

package/dist/assets/plugin/skills/refactor/SKILL.md

@@ -3,21 +3,9 @@ name: refactor
 description: Use when Root has decided one seam needs restructuring; preserve behavior, ownership, and interfaces.
 ---
 
-Prefer existing project conventions and standard-library or native behavior.
-Trace callers before changing a shared root cause. Reuse an existing boundary
-when it has real callers or clear near-term value; avoid speculative
-abstractions and splitting a cohesive file without a concrete benefit. Keep
-the smallest correct, independently mergeable diff with coherent dependency
-direction. Git/VCS work remains Root-only.
-
-Discover the repository-specific formatter, linter, typecheck, and validation
-commands from its package scripts, task config, and contributor guidance. Run
-the smallest relevant local proof first and broaden only when the changed
-boundary or release gate requires it; do not invent unavailable commands.
-
-Owner: Worker. Boundary: change only the assigned seam; preserve ownership,
-dependency direction, public behavior, and interfaces.
-
-Completion: changed files are inspected, focused behavior-locked checks are
-clean, temporary/generated output is removed, and any residual risk or blocker
-is explicit.
+Restructure only the decided seam. Trace its callers before changing a shared
+root cause, preserve public behavior and interfaces, and keep the smallest
+cohesive change. Discover the repository's own validation commands and run the
+smallest relevant behavior-locked check first; broaden when the changed
+boundary or release gate requires it. Inspect changed files and remove
+incidental generated output before stopping.

package/dist/assets/plugin/skills/writing-for-agents/SKILL.md

@@ -10,8 +10,12 @@ Treat each instruction as an interface with one contract:
 - **Owner:** the role permitted to act or decide.
 - **Boundary:** the exact scope, authority, constraints, and escalation point.
 - **Completion:** the observable outcome and proof that permit the agent to stop.
+- **Return:** the result Root needs to integrate: outcome or findings, changed
+  paths, verification, unresolved risk, and any requested decision.
 
-Write an objective, scope, retained constraints, evidence, exclusions, and the exact missing fact or material choice that returns to the owner. The receiver must be able to act, prove, and stop without reconstructing intent.
+Write an objective, scope, retained constraints, evidence, exclusions, and the
+exact missing fact or material choice that returns to the owner. The receiver
+must be able to act, prove, and stop without reconstructing intent.
 
 Before any Root subagent dispatch, ensure this skill is fully loaded and applied
 in the current context. Reuse the loaded instructions for later dispatches