holycodex 0.16.9 → 0.16.10-dev.112.1

package/dist/assets/plugin/plugin.json

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

package/dist/assets/plugin/skills/babysit-ci/SKILL.md

@@ -1,10 +1,15 @@
 ---
 name: babysit-ci
-description: Use when following CI or release gates through terminal completion.
+description: Use when CI or release gates need follow-through; monitor their terminal results and report gate evidence.
 ---
 
 # Babysit CI
 
+Root owns orchestration and mutations; Worker.operations observes the assigned
+gates. Dispatch independent checks and review observation concurrently.
+Use only the gates in the user's requested scope. When asked to monitor CI
+only or ignore review bots, omit review observation and review findings.
+
 Discover the repository's development and release topology for pushes and pull
 requests: refs, required checks, reviews, publication mechanism, and gate
 dependencies. Do not assume a provider, branch name, or separate pipeline.
@@ -13,13 +18,17 @@ For a push, bind every observation to the exact pushed ref and SHA. For a pull
 request, bind it to the current head SHA, target branch, pull-request identity,
 and review commit when the provider exposes one. Inspect required checks and
 relevant bot reviews, inline threads, issue comments, and commit comments. A
-new push invalidates all stale CI and review evidence; rediscover the current
-head and repeat validation and review observation for that SHA.
+new push requires CI and review evidence for the new head; reuse unchanged
+topology and local proof that remains applicable.
 
-Use bounded observer waits. Distinguish a bot that is absent or not configured
-from a known bot with no terminal signal, and both from a clean terminal
-disposition. Absence or no signal is an evidence gap. Green checks do not
-resolve outstanding review findings or threads.
+Use bounded observer waits at the longest supported event interval. If the provider
+offers only snapshots, avoid repeated reads before state can change; stop as
+soon as the exact target reaches a terminal result. Distinguish a bot that is absent
+or not configured from a known bot with no terminal signal, and both from a clean
+terminal disposition. Absence or no signal is an evidence gap.
+Green checks do not resolve outstanding review findings or threads.
+Include target-branch or pull-request mergeability evidence when exposed;
+green checks alone do not prove mergeability.
 
 After a development action, observe its exact ref and SHA to terminal state.
 Repair failed checks and actionable review findings, then repeat validation and

package/dist/assets/plugin/skills/babysit-ci/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "Babysit CI"
   short_description: "Follow repository CI and release gates to completion."
-  default_prompt: "Use babysit-ci for this CI or release lifecycle."
+  default_prompt: "Use $babysit-ci for this task."
 policy:
   allow_implicit_invocation: true

package/dist/assets/plugin/skills/codebase-onboarding/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: codebase-onboarding
-description: Use when explaining a repository or orienting a new contributor to how it works.
+description: Use when someone needs a repository explanation or contributor orientation; summarize its purpose, structure, and workflows from evidence.
 ---
 
 Provide a bounded, read-only orientation to the current repository or answer a

package/dist/assets/plugin/skills/codebase-onboarding/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "Codebase onboarding"
   short_description: "Explain a repository from a bounded read-only map."
-  default_prompt: "Explain how this repository works."
+  default_prompt: "Use $codebase-onboarding for this task."
 policy:
   allow_implicit_invocation: true

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

@@ -1,6 +1,6 @@
 ---
 name: commit
-description: Use when Root creates a local commit after scope and proof are settled.
+description: Use when Root is ready to commit settled and verified work; create the smallest coherent commits that follow repository conventions.
 ---
 
 After scope and proof are settled, follow the repository's commit conventions

package/dist/assets/plugin/skills/commit/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "Commit"
   short_description: "Create coherent local commits with exact scope proof."
-  default_prompt: "Open the commit workflow for this invocation."
+  default_prompt: "Use $commit for this task."
 policy:
   allow_implicit_invocation: false

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

@@ -1,6 +1,6 @@
 ---
 name: compress
-description: Use when assigned text must be shortened without changing its contract or voice.
+description: Use when assigned text must be shortened without changing its contract or voice; preserve meaning and constraints in a more concise version.
 ---
 
 Shorten only the assigned text. Preserve meaning, constraints, technical terms,

package/dist/assets/plugin/skills/compress/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "Compress"
   short_description: "Shorten assigned text without changing its contract or voice."
-  default_prompt: "Open the compression workflow for this invocation."
+  default_prompt: "Use $compress for this task."
 policy:
   allow_implicit_invocation: true

package/dist/assets/plugin/skills/context7-cli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: context7-cli
-description: Use when querying current technical documentation with Context7 CLI.
+description: Use when current technical documentation is needed through Context7 CLI; find the requested version-specific facts.
 ---
 
 Resolve the requested library identity with the installed ctx7 CLI, then query

package/dist/assets/plugin/skills/context7-cli/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "Context7 CLI"
   short_description: "Find assigned current library and API documentation first."
-  default_prompt: "Open the current documentation lookup workflow for this invocation."
+  default_prompt: "Use $context7-cli for this task."
 policy:
   allow_implicit_invocation: false

package/dist/assets/plugin/skills/continue-work/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: continue-work
-description: Use when the user asks Root to continue, resume, or keep going with existing HolyCodex work.
+description: Use when the user asks Root to continue existing HolyCodex work; restore its current state and carry unresolved work forward.
 ---
 
 Restore the current Intent, Plan if present, Assignments, accepted evidence,

package/dist/assets/plugin/skills/continue-work/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "Continue work"
   short_description: "Resume the current HolyCodex work from durable state."
-  default_prompt: "Continue the current HolyCodex work."
+  default_prompt: "Use $continue-work for this task."
 policy:
   allow_implicit_invocation: true

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

@@ -1,6 +1,6 @@
 ---
 name: debugging
-description: Use to diagnose and repair an observable defect or unexplained behavior.
+description: Use when an observable defect or unexplained behavior needs diagnosis; establish its cause and repair it within the assigned boundary.
 ---
 
 Reproduce the issue with the smallest useful case when practical; otherwise,

package/dist/assets/plugin/skills/debugging/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "Debugging"
   short_description: "Diagnose an observable defect through reproduction or strong evidence."
-  default_prompt: "Open the debugging workflow for this invocation."
+  default_prompt: "Use $debugging for this task."
 policy:
   allow_implicit_invocation: false

package/dist/assets/plugin/skills/dev-server/SKILL.md

@@ -0,0 +1,13 @@
+---
+name: dev-server
+description: Use when a shared background development server is needed; let Root start, reuse, and manage one server for the session.
+---
+
+Root only. Reuse a healthy server for the current project; otherwise start the
+repository's development command in the background using the active runtime's
+process controls. Confirm readiness, return its URL, and share the URL with
+specialists so they reuse it. Root retains the process handle. Keep it alive
+across Assignments; restart only when configuration or server state requires
+it. Stop only the process owned by this session when
+no longer needed. Specialists request server changes through their terminal
+report rather than starting competing servers.

package/dist/assets/plugin/skills/dev-server/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "Dev server"
+  short_description: "Root manages one shared background development server."
+  default_prompt: "Use $dev-server for this task."
+policy:
+  allow_implicit_invocation: false

package/dist/assets/plugin/skills/grill-me/SKILL.md

@@ -1,21 +1,21 @@
 ---
 name: grill-me
-description: Use when an unspecified choice has multiple reasonable outcomes that could materially change the work.
+description: Use when a material user decision blocks authorized work; ask Root's concise question through request_user_input.
 ---
 
 # Grill me
 
-Use this skill only for a material unresolved choice involving architecture,
-behavior, UX, compatibility, dependencies, cost, security, external effects,
-or another meaningful user-visible result. Infer obvious safe defaults and
-continue without questioning routine omissions.
+Use this skill only when an unresolved material user decision blocks the next
+step. It is not for routine omissions, safe implementation choices, or
+planning.
 
-Before asking, finish authorized discovery and reversible preparation that can
-narrow the choice without deciding it. Ask only for the earliest unresolved
-choice required by the next executable phase. After the answer, continue the
-discovery and ask the next dependent question only if it remains material.
-Avoid questionnaires about later phases whose relevance may change.
+Root only. For every clarification, call `request_user_input` with the smallest
+set of questions needed to resolve the decision, in the user's language and
+grounded in known evidence. Never ask what the session already establishes.
+If no material question remains, continue without invoking this skill.
 
-Persist the answer through the current Intent or Plan state model. Return to
-Root with the selected decision, its scope, and the evidence or dependency it
-unblocked; use `needs_root_input` when the choice remains unresolved.
+Continue independent authorized work while awaiting the answer. Do not ask
+about hypothetical later phases. Specialists must not ask the user; they
+return a `needs_root_input` outcome to Root with the specific decision and
+why it blocks their Assignment. Root uses that outcome only when the answer
+prevents further progress.

package/dist/assets/plugin/skills/grill-me/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "Grill me"
-  short_description: "Ask only material, dependency-ordered clarification questions."
-  default_prompt: "Open the material-choice clarification workflow for this invocation."
+  short_description: "Ask Root-only material questions through request_user_input."
+  default_prompt: "Use $grill-me for this task."
 policy:
-  allow_implicit_invocation: true
+  allow_implicit_invocation: false

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

@@ -1,9 +1,8 @@
 ---
 name: handoff
-description: Use when a caller needs a redacted projection of current Intent state for resume or export.
+description: Use when current Intent state must be resumed or exported; write a portable Markdown handoff with evidence and next action.
 ---
 
-Produce one compact projection of current Intent, Plan, and Assignment status,
-evidence, blockers, remaining risk, and the exact next action. Omit secrets,
-raw prompts, transcripts, and unchanged narration. Handoff is an export view;
-the semantic state remains authoritative.
+Write one compact Markdown handoff file in the host temporary directory resolved through environment variables such as TMPDIR, TMP, or TEMP. Avoid hardcoded absolute machine or user paths. Include current Intent, Plan, and Assignment status, evidence, blockers, remaining risk, and the exact next action. Omit secrets, raw prompts, transcripts, and unchanged narration. The semantic state remains authoritative.
+
+Verify the file contains sufficient context to resume the work. Return its portable location relative to the resolved temporary directory in a Markdown code block, identifying the temporary environment variable used. Let the user decide how to use it; do not create another thread.

package/dist/assets/plugin/skills/handoff/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "Handoff"
   short_description: "Export a redacted projection of current Intent state."
-  default_prompt: "Open the handoff workflow for this invocation."
+  default_prompt: "Use $handoff for this task."
 policy:
   allow_implicit_invocation: false

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

@@ -1,6 +1,6 @@
 ---
 name: refactor
-description: Use when one decided seam needs restructuring while preserving behavior and interfaces.
+description: Use when one decided seam needs restructuring without behavior or interface changes; refactor that seam and verify its boundaries.
 ---
 
 Restructure only the decided seam. Trace callers before changing a shared root

package/dist/assets/plugin/skills/refactor/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "Refactor"
   short_description: "Restructure one decided seam while preserving its contract."
-  default_prompt: "Open the bounded refactor workflow for this invocation."
+  default_prompt: "Use $refactor for this task."
 policy:
   allow_implicit_invocation: true

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

@@ -1,6 +1,6 @@
 ---
 name: rules
-description: Use when a repository rule needs discovery, validation, or diagnosis of an application failure.
+description: Use when a repository rule needs discovery, validation, or failure diagnosis; trace its owner and report the rule with evidence.
 ---
 
 Trace the owning rule loader and its limits, caching, trust boundary, and

package/dist/assets/plugin/skills/rules/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "Rules"
   short_description: "Trace one repository rule discovery or application failure."
-  default_prompt: "Open the repository rules workflow for this invocation."
+  default_prompt: "Use $rules for this task."
 policy:
   allow_implicit_invocation: false

package/dist/assets/plugin/skills/visual-loop/SKILL.md

@@ -0,0 +1,10 @@
+---
+name: visual-loop
+description: Use when visual work needs rendered acceptance; coordinate Worker.visual, Reviewer.visual, and Root judgment.
+---
+
+Root only, when the rendered or interacted-with result is materially part of success. Follow the canonical loop: Worker.visual → Reviewer.visual → Root visual pass. Worker.visual produces mergeable implementation and inspects its actual result; Reviewer.visual independently reviews implementation and rendered interactions without repairs. Root independently inspects the current result, actively looks for issues both specialists missed, and remains final visual authority.
+
+Judge relevant viewports and states against acceptance criteria, user references, and the repository design system. Follow the installed visual capability priority and active-surface tool rules; use the shared development server when needed. Return a specific evidence blocker when required judgment is unavailable.
+
+For a material discrepancy, dispatch only the bounded visual repair required, repeat only affected review and judgment, and reuse unaffected evidence. Acceptance requires sufficient current rendered and interaction evidence. Do not run this loop for logic-only work with no material rendered consequence.

package/dist/assets/plugin/skills/visual-loop/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "Visual loop"
+  short_description: "Root judges rendered changes after specialists inspect their work and assigns repairs."
+  default_prompt: "Use $visual-loop for this task."
+policy:
+  allow_implicit_invocation: false

package/dist/assets/plugin/skills/web-visualize/SKILL.md

@@ -1,17 +1,8 @@
 ---
 name: web-visualize
-description: Use when the user requests an interactive visualization or approves a proposed one.
+description: Use when the user requests or approves an interactive visualization; create a standalone HTML experience from the supplied material.
 ---
 
-Use ChatGPT Sites to create an interactive, user-facing visualization that
-turns the supplied plan, analysis, design, structured information, or other
-useful material into a clear, usable result. When the user explicitly requests
-a visualization, create it without asking again. If you believe one would
-materially improve a task but the user did not request it, ask Root to obtain
-approval before creating it.
+Create a standalone .html file in the host temporary directory, resolved through environment variables such as TMPDIR, TMP, or TEMP. Do not hardcode machine or user paths. The result must turn the supplied material into a clear, usable interactive visualization that answers the request.
 
-Return the visualization and enough context to verify that it answers the
-request. If the requested result cannot be completed with an authorized,
-available capability, return the specific blocker to Root. Publication,
-sharing, and other consequential external effects require their usual
-authorization.
+Root assigns visual implementation and judges acceptance through visual-loop. Use the installed capability projection's web-visualize inspection and delivery workflow. Return the HTML artifact and sufficient evidence that its content and interactions meet the acceptance criteria. Publication, sharing, and consequential external effects retain their authorization boundary.

package/dist/assets/plugin/skills/web-visualize/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "Web visualize"
   short_description: "Turn useful information into an interactive user-facing visualization."
-  default_prompt: "Create the requested interactive visualization."
+  default_prompt: "Use $web-visualize for this task."
 policy:
   allow_implicit_invocation: true

package/dist/assets/plugin/skills/writing-instructions/SKILL.md

@@ -1,46 +1,30 @@
 ---
 name: writing-instructions
-description: Use when authoring or reviewing model-facing instructions.
+description: Use when model-facing instructions need authorship or review; make them coherent, scoped, and complete for their receiver.
 ---
 
 # Writing instructions
 
-Use this skill for model-facing instructions, including Root/session policy,
-specialist and Role.task contracts, skills, and conditional workflows. Keep
-shared behavior under one owner across model routes; account for model-specific
-differences only when supported by evidence.
-
-Before writing, identify the receiver's effective context: higher-priority and
-user instructions, repository instructions, Role/task policy, relevant skills,
-tools and capabilities, configuration, and current task context. Add only the
-missing semantic delta. Resolve conflicts against the governing authority;
-do not duplicate a meaning already supplied to the same receiver.
-
-Give each meaning one authoritative owner at the narrowest scope that applies:
-Root/session invariants in Root policy, repository conventions in AGENTS.md,
-shared specialist boundaries in the specialist baseline, route-specific behavior
-in Role.task, and genuinely conditional workflow or tool knowledge in a skill.
-Generated projections derive from or validate against that owner. Invocation
-metadata selects a branch; it does not become a second policy source.
-
-Define the required outcome and completion evidence, bounded authority, relevant
-constraints, material decisions or blockers that escalate, and stopping
-conditions. Keep required lifecycle and safety invariants explicit. Give the
-receiver room to choose routine safe, reversible, in-scope steps. A contract must
-carry authorized work through its requested terminal state, including required
-repair and proof; a first pass or pending gate is not completion.
-
-Remove older-model competence scaffolding, fixed recipes without a required
-ordering constraint, broad reading rituals, stale environment facts, duplicate
-policy, and unnecessary questionnaires. Preserve meaningful repository checks
-and review gates through their canonical owners instead of reproducing them in
-every skill. Use configuration for verbosity rather than generic style padding.
-
-When changing a skill's invocation boundary or conditional branches, follow
-[Skill mechanics](SKILL-MECHANICS.md).
-
-An instruction change is complete when the receiver can act within its authority,
-recognize completion and escalation boundaries, and return sufficient evidence;
-the effective context has no contradictory or duplicate rule for that meaning.
-Validate changed behavior with meaningful proof and repository-required gates,
-using the canonical testing policy rather than inventing extra test rituals.
+Treat every model-facing instruction as an execution contract.
+
+The receiver must be able to determine the goal or required end-state, the observable conditions that constitute success, and the evidence required to prove that success.
+
+Use this mental model:
+
+goal -> success criteria -> optional required method -> proof of success
+
+Identify the receiver's effective context: instruction hierarchy, repository rules, Root or Role.task authority, relevant skills, tools, projected capabilities, configuration, and Assignment facts. Add only missing constraints and resolve contradictions against governing authority.
+
+Give each meaning one authoritative owner. Project policy from that owner instead of duplicating it across prompts, metadata, skills, generated instructions, or nearby policies.
+
+State a required means, procedure, tool, ordering, or implementation detail only when it materially constrains correct execution. Otherwise leave routine safe implementation choices to the receiver.
+
+Completion evidence must prove the success criteria. Use the smallest meaningful proof proportionate to behavior, scope, risk, uncertainty, and acceptance criteria. Reuse current evidence. Broaden or repeat validation only after relevant changes, failures, elevated risk, or unresolved material concerns. Preserve required repository gates and necessary high-risk regression coverage.
+
+Remove redundant policy, stale model scaffolding, broad reading rituals, rigid recipes without a real dependency, hypothetical gates, repeated testing, and prose that merely restates choices the receiver can safely make itself.
+
+Carry authorized work through repair and proof.
+
+Validate the effective contract rather than exact wording: the receiver can identify the goal, recognize success and blockers, act within authority, and return sufficient evidence without contradictory rules.
+
+Keep skill descriptions short and situation-first. Audit triggers alongside nearby skills; keep coherent shared guidance together and link uncommon mechanics from the condition that needs them. Display and invocation metadata selects the workflow; it does not duplicate model-facing behavior. Metadata default prompts invoke the named skill without embedding another instruction source. Preserve upstream attribution.

package/dist/assets/plugin/skills/writing-instructions/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "Writing instructions"
   short_description: "Author and review model-facing instructions."
-  default_prompt: "Use writing-instructions for this instruction change."
+  default_prompt: "Use $writing-instructions for this task."
 policy:
   allow_implicit_invocation: true