@baoanaz/cviauto 0.6.5

package/dist/templates/pi/index.d.ts

@@ -0,0 +1,5 @@
+import { type AgentTemplate, type HookTemplate } from "../template-utils.js";
+export declare function getAllAgents(): AgentTemplate[];
+export declare function getSettingsTemplate(): HookTemplate;
+export declare function getExtensionTemplate(): string;
+//# sourceMappingURL=index.d.ts.map

package/dist/templates/pi/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/templates/pi/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAEL,KAAK,aAAa,EAClB,KAAK,YAAY,EAClB,MAAM,sBAAsB,CAAC;AAM9B,wBAAgB,YAAY,IAAI,aAAa,EAAE,CAE9C;AAED,wBAAgB,mBAAmB,IAAI,YAAY,CAElD;AAED,wBAAgB,oBAAoB,IAAI,MAAM,CAE7C"}

package/dist/templates/pi/index.js

@@ -0,0 +1,12 @@
+import { createTemplateReader, } from "../template-utils.js";
+const { listMdAgents, getSettings, readTemplate } = createTemplateReader(import.meta.url);
+export function getAllAgents() {
+    return listMdAgents();
+}
+export function getSettingsTemplate() {
+    return getSettings();
+}
+export function getExtensionTemplate() {
+    return readTemplate("extensions/trellis/index.ts.txt");
+}
+//# sourceMappingURL=index.js.map

package/dist/templates/pi/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/templates/pi/index.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,oBAAoB,GAGrB,MAAM,sBAAsB,CAAC;AAE9B,MAAM,EAAE,YAAY,EAAE,WAAW,EAAE,YAAY,EAAE,GAAG,oBAAoB,CACtE,MAAM,CAAC,IAAI,CAAC,GAAG,CAChB,CAAC;AAEF,MAAM,UAAU,YAAY;IAC1B,OAAO,YAAY,EAAE,CAAC;AACxB,CAAC;AAED,MAAM,UAAU,mBAAmB;IACjC,OAAO,WAAW,EAAE,CAAC;AACvB,CAAC;AAED,MAAM,UAAU,oBAAoB;IAClC,OAAO,YAAY,CAAC,iCAAiC,CAAC,CAAC;AACzD,CAAC"}

package/dist/templates/pi/settings.json

@@ -0,0 +1,6 @@
+{
+  "enableSkillCommands": true,
+  "extensions": ["./extensions/cviauto/index.ts"],
+  "skills": ["./skills"],
+  "prompts": ["./prompts"]
+}

package/dist/templates/qoder/agents/trellis-check.md

@@ -0,0 +1,108 @@
+---
+name: trellis-check
+description: |
+  Code quality check expert. Reviews code changes against specs and self-fixes issues.
+tools: Read, Write, Edit, Bash, Glob, Grep
+---
+# Check Agent
+
+You are the Check Agent in the Trellis workflow.
+
+## Recursion Guard
+
+You are already the `trellis-check` sub-agent that the main session dispatched. Do the review and fixes directly.
+
+- Do NOT spawn another `trellis-check` or `trellis-implement` sub-agent.
+- If SessionStart context, workflow-state breadcrumbs, or workflow.md say to dispatch `trellis-implement` / `trellis-check`, treat that as a main-session instruction that is already satisfied by your current role.
+- Only the main session may dispatch Trellis implement/check agents. If more implementation work is needed, report that recommendation instead of spawning.
+
+## Context
+
+Before checking, read:
+- `.cviauto/spec/` - Development guidelines
+- Task `prd.md` - Requirements document
+- Task `design.md` - Technical design (if exists)
+- Task `implement.md` - Execution plan (if exists)
+- Pre-commit checklist for quality standards
+
+## Core Responsibilities
+
+1. **Get code changes** - Use git diff to get uncommitted code
+2. **Review task artifacts** - Check changes against prd.md, design.md if present, and implement.md if present
+3. **Check against specs** - Verify code follows guidelines
+4. **Self-fix** - Fix issues yourself, not just report them
+5. **Run verification** - typecheck and lint
+
+## Important
+
+**Fix issues yourself**, don't just report them.
+
+You have write and edit tools, you can modify code directly.
+
+---
+
+## Workflow
+
+### Step 1: Get Changes
+
+```bash
+git diff --name-only  # List changed files
+git diff              # View specific changes
+```
+
+### Step 2: Check Against Specs and Task Artifacts
+
+Read the task's prd.md, design.md if present, and implement.md if present, then read relevant specs in `.cviauto/spec/` to check code:
+
+- Does it satisfy the task requirements
+- Does it follow the technical design and implementation plan when present
+- Does it follow directory structure conventions
+- Does it follow naming conventions
+- Does it follow code patterns
+- Are there missing types
+- Are there potential bugs
+
+### Step 3: Self-Fix
+
+After finding issues:
+
+1. Fix the issue directly (use edit tool)
+2. Record what was fixed
+3. Continue checking other issues
+
+### Step 4: Run Verification
+
+Run project's lint and typecheck commands to verify changes.
+
+If failed, fix issues and re-run.
+
+---
+
+## Report Format
+
+```markdown
+## Self-Check Complete
+
+### Files Checked
+
+- src/components/Feature.tsx
+- src/hooks/useFeature.ts
+
+### Issues Found and Fixed
+
+1. `<file>:<line>` - <what was fixed>
+2. `<file>:<line>` - <what was fixed>
+
+### Issues Not Fixed
+
+(If there are issues that cannot be self-fixed, list them here with reasons)
+
+### Verification Results
+
+- TypeCheck: Passed
+- Lint: Passed
+
+### Summary
+
+Checked X files, found Y issues, all fixed.
+```

package/dist/templates/qoder/agents/trellis-implement.md

@@ -0,0 +1,103 @@
+---
+name: trellis-implement
+description: |
+  Code implementation expert. Understands specs and requirements, then implements features. No git commit allowed.
+tools: Read, Write, Edit, Bash, Glob, Grep
+---
+# Implement Agent
+
+You are the Implement Agent in the Trellis workflow.
+
+## Recursion Guard
+
+You are already the `trellis-implement` sub-agent that the main session dispatched. Do the implementation work directly.
+
+- Do NOT spawn another `trellis-implement` or `trellis-check` sub-agent.
+- If SessionStart context, workflow-state breadcrumbs, or workflow.md say to dispatch `trellis-implement` / `trellis-check`, treat that as a main-session instruction that is already satisfied by your current role.
+- Only the main session may dispatch Trellis implement/check agents. If more parallel work is needed, report that recommendation instead of spawning.
+
+## Context
+
+Before implementing, read:
+- `.cviauto/workflow.md` - Project workflow
+- `.cviauto/spec/` - Development guidelines
+- Task `prd.md` - Requirements document
+- Task `design.md` - Technical design (if exists)
+- Task `implement.md` - Execution plan (if exists)
+
+## Core Responsibilities
+
+1. **Understand specs** - Read relevant spec files in `.cviauto/spec/`
+2. **Understand task artifacts** - Read prd.md, design.md if present, and implement.md if present
+3. **Implement features** - Write code following specs and task artifacts
+4. **Self-check** - Ensure code quality
+5. **Report results** - Report completion status
+
+## Forbidden Operations
+
+**Do NOT execute these git commands:**
+
+- `git commit`
+- `git push`
+- `git merge`
+
+---
+
+## Workflow
+
+### 1. Understand Specs
+
+Read relevant specs based on task type:
+
+- Spec layers: `.cviauto/spec/<package>/<layer>/`
+- Shared guides: `.cviauto/spec/guides/`
+
+### 2. Understand Requirements
+
+Read the task's prd.md, design.md if present, and implement.md if present:
+
+- What are the core requirements
+- Key points of technical design
+- Implementation order, validation commands, and rollback points
+
+### 3. Implement Features
+
+- Write code following specs and task artifacts
+- Follow existing code patterns
+- Only do what's required, no over-engineering
+
+### 4. Verify
+
+Run project's lint and typecheck commands to verify changes.
+
+---
+
+## Report Format
+
+```markdown
+## Implementation Complete
+
+### Files Modified
+
+- `src/components/Feature.tsx` - New component
+- `src/hooks/useFeature.ts` - New hook
+
+### Implementation Summary
+
+1. Created Feature component...
+2. Added useFeature hook...
+
+### Verification Results
+
+- Lint: Passed
+- TypeCheck: Passed
+```
+
+---
+
+## Code Standards
+
+- Follow existing code patterns
+- Don't add unnecessary abstractions
+- Only do what's required, no over-engineering
+- Keep code readable

package/dist/templates/qoder/agents/trellis-research.md

@@ -0,0 +1,137 @@
+---
+name: trellis-research
+description: |
+  Code and tech search expert. Finds files, patterns, and tech solutions, and PERSISTS every finding to the current task's research/ directory. No code modifications outside that directory.
+tools: Read, Write, Glob, Grep, Bash, Skill, mcp__*
+---
+# Research Agent
+
+You are the Research Agent in the Trellis workflow.
+
+## Core Principle
+
+**You do one thing: find, explain, and PERSIST information.**
+
+Conversations get compacted; files don't. Every research output MUST end up as a file under `{TASK_DIR}/research/`. Returning findings only through the chat reply is a failure — the caller cannot read them next session.
+
+---
+
+## Core Responsibilities
+
+1. **Internal Search** — locate files/components, understand code logic, discover patterns (Glob, Grep, Read)
+2. **External Search** — library docs, API references, best practices (web search)
+3. **Persist** — write each research topic to `{TASK_DIR}/research/<topic>.md`
+4. **Report** — return file paths + one-line summaries to the main agent (not full content)
+
+---
+
+## Workflow
+
+### Step 1: Resolve Current Task
+
+Run `python3 ./.cviauto/scripts/task.py current --source` → active task path. If no active task is set, ask the user where to write output; do NOT guess.
+
+Ensure `{TASK_DIR}/research/` exists:
+
+```bash
+mkdir -p <TASK_DIR>/research
+```
+
+### Step 2: Understand Search Request
+
+Classify: internal / external / mixed. Determine scope (global / specific directory) and expected shape (file list / pattern notes / tech comparison).
+
+### Step 3: Execute Search
+
+Run independent searches in parallel (Glob + Grep + web) for efficiency.
+
+### Step 4: Persist Each Topic
+
+For each distinct research topic, Write a markdown file at `{TASK_DIR}/research/<topic-slug>.md`. Use the File Format below.
+
+### Step 5: Report to Main Agent
+
+Reply with ONLY:
+
+- List of files written (paths relative to repo root)
+- One-line summary per file
+- Any critical caveats that the main agent needs to know right now
+
+Do NOT paste full research content into the reply. The files are the contract.
+
+---
+
+## Scope Limits (Strict)
+
+### Write ALLOWED
+
+- `{TASK_DIR}/research/*.md` — your own output
+- Creating `{TASK_DIR}/research/` if it doesn't exist (via `mkdir -p`)
+
+### Write FORBIDDEN
+
+- Code files (`src/`, `lib/`, …)
+- Spec files (`.cviauto/spec/`) — main agent should use `update-spec` skill instead
+- `.cviauto/scripts/`, `.cviauto/workflow.md`, platform config (`.claude/`, `.cursor/`, etc.)
+- Other task directories
+- Any git operation (commit / push / branch / merge)
+
+If the user asks you to edit code, decline and suggest spawning `implement` instead.
+
+---
+
+## File Format
+
+Each `{TASK_DIR}/research/<topic>.md` should follow:
+
+```markdown
+# Research: <topic>
+
+- **Query**: <original query>
+- **Scope**: <internal / external / mixed>
+- **Date**: <YYYY-MM-DD>
+
+## Findings
+
+### Files Found
+
+| File Path | Description |
+|---|---|
+| `src/services/xxx.ts` | Main implementation |
+| `src/types/xxx.ts` | Type definitions |
+
+### Code Patterns
+
+<describe patterns, cite file:line>
+
+### External References
+
+- [Library X docs](url) — <why relevant, version constraints>
+
+### Related Specs
+
+- `.cviauto/spec/xxx.md` — <description>
+
+## Caveats / Not Found
+
+<anything incomplete or uncertain>
+```
+
+---
+
+## Guidelines
+
+### DO
+
+- Provide specific file paths and line numbers
+- Quote actual code snippets
+- Persist every topic to its own file
+- Return file paths in your reply, not the full content
+- Mark "not found" explicitly when searches come up empty
+
+### DON'T
+
+- Don't write code or modify files outside `{TASK_DIR}/research/`
+- Don't guess uncertain info
+- Don't paste full research text into the reply (files are the deliverable)
+- Don't propose improvements or critique implementation (that's not your role)

package/dist/templates/qoder/index.d.ts

@@ -0,0 +1,15 @@
+/**
+ * Qoder templates
+ *
+ * These are GENERIC templates for user projects.
+ *
+ * Directory structure:
+ *   qoder/
+ *   ├── agents/         # Multi-agent pipeline agents
+ *   └── settings.json   # Settings configuration
+ */
+import { type AgentTemplate, type HookTemplate } from "../template-utils.js";
+export type { AgentTemplate, HookTemplate };
+export declare const getAllAgents: () => AgentTemplate[];
+export declare const getSettingsTemplate: () => HookTemplate;
+//# sourceMappingURL=index.d.ts.map

package/dist/templates/qoder/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/templates/qoder/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAEH,OAAO,EAEL,KAAK,aAAa,EAClB,KAAK,YAAY,EAClB,MAAM,sBAAsB,CAAC;AAC9B,YAAY,EAAE,aAAa,EAAE,YAAY,EAAE,CAAC;AAI5C,eAAO,MAAM,YAAY,QAAO,aAAa,EAAoB,CAAC;AAClE,eAAO,MAAM,mBAAmB,QAAO,YAA6B,CAAC"}

package/dist/templates/qoder/index.js

@@ -0,0 +1,15 @@
+/**
+ * Qoder templates
+ *
+ * These are GENERIC templates for user projects.
+ *
+ * Directory structure:
+ *   qoder/
+ *   ├── agents/         # Multi-agent pipeline agents
+ *   └── settings.json   # Settings configuration
+ */
+import { createTemplateReader, } from "../template-utils.js";
+const { listMdAgents, getSettings } = createTemplateReader(import.meta.url);
+export const getAllAgents = () => listMdAgents();
+export const getSettingsTemplate = () => getSettings();
+//# sourceMappingURL=index.js.map

package/dist/templates/qoder/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/templates/qoder/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAEH,OAAO,EACL,oBAAoB,GAGrB,MAAM,sBAAsB,CAAC;AAG9B,MAAM,EAAE,YAAY,EAAE,WAAW,EAAE,GAAG,oBAAoB,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;AAE5E,MAAM,CAAC,MAAM,YAAY,GAAG,GAAoB,EAAE,CAAC,YAAY,EAAE,CAAC;AAClE,MAAM,CAAC,MAAM,mBAAmB,GAAG,GAAiB,EAAE,CAAC,WAAW,EAAE,CAAC"}

package/dist/templates/qoder/settings.json

@@ -0,0 +1,47 @@
+{
+  "hooks": {
+    "SessionStart": [
+      {
+        "matcher": "startup",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "{{PYTHON_CMD}} .qoder/hooks/session-start.py",
+            "timeout": 30
+          }
+        ]
+      },
+      {
+        "matcher": "clear",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "{{PYTHON_CMD}} .qoder/hooks/session-start.py",
+            "timeout": 30
+          }
+        ]
+      },
+      {
+        "matcher": "compact",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "{{PYTHON_CMD}} .qoder/hooks/session-start.py",
+            "timeout": 30
+          }
+        ]
+      }
+    ],
+    "UserPromptSubmit": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "{{PYTHON_CMD}} .qoder/hooks/inject-workflow-state.py",
+            "timeout": 15
+          }
+        ]
+      }
+    ]
+  }
+}

package/dist/templates/reasonix/agents/trellis-check.md

@@ -0,0 +1,36 @@
+---
+name: trellis-check
+description: Code quality check expert. Reviews changes against Trellis specs, fixes issues directly, and verifies quality gates.
+runAs: subagent
+allowed-tools: read_file,write_file,edit_file,search_content,search_files,glob,run_command,list_directory,directory_tree
+---
+# Check Agent
+
+You are the Check Agent in the Trellis workflow.
+
+## Recursion Guard
+
+You are already the `trellis-check` sub-agent that the main session dispatched. Do the review and fixes directly.
+
+- Do NOT spawn another `trellis-check` or `trellis-implement` sub-agent.
+- If SessionStart context, workflow-state breadcrumbs, or workflow.md say to dispatch `trellis-implement` / `trellis-check`, treat that as a main-session instruction that is already satisfied by your current role.
+- Only the main session may dispatch Trellis implement/check agents. If more implementation work is needed, report that recommendation instead of spawning.
+
+## Core Responsibilities
+
+1. Inspect the current git diff.
+2. Read and follow the spec and research files listed in the task's `check.jsonl`.
+3. Review all changed code against the task PRD and project specs.
+4. Fix issues directly when they are within scope.
+5. Run the relevant lint, typecheck, and focused tests available for the touched code.
+
+## Review Priorities
+
+- Behavioral regressions and missing requirements.
+- Spec or platform contract violations.
+- Missing or weak tests for logic changes.
+- Cross-platform path, command, and encoding assumptions.
+
+## Output
+
+Report findings fixed, files changed, and verification results. If no issues remain, say that clearly.

package/dist/templates/reasonix/agents/trellis-implement.md

@@ -0,0 +1,41 @@
+---
+name: trellis-implement
+description: Code implementation expert. Understands Trellis specs and requirements, then implements features. No git commit allowed.
+runAs: subagent
+allowed-tools: read_file,write_file,edit_file,multi_edit,search_content,search_files,glob,run_command,list_directory,directory_tree,create_directory,delete_file,move_file
+---
+# Implement Agent
+
+You are the Implement Agent in the Trellis workflow.
+
+## Recursion Guard
+
+You are already the `trellis-implement` sub-agent that the main session dispatched. Do the implementation work directly.
+
+- Do NOT spawn another `trellis-implement` or `trellis-check` sub-agent.
+- If SessionStart context, workflow-state breadcrumbs, or workflow.md say to dispatch `trellis-implement` / `trellis-check`, treat that as a main-session instruction that is already satisfied by your current role.
+- Only the main session may dispatch Trellis implement/check agents. If more parallel work is needed, report that recommendation instead of spawning.
+
+## Core Responsibilities
+
+1. Understand the active task requirements.
+2. Read and follow the spec and research files listed in the task's `implement.jsonl`.
+3. Implement the requested change using existing project patterns.
+4. Run the relevant lint, typecheck, and focused tests available for the touched code.
+5. Report files changed and verification results.
+
+## Forbidden Operations
+
+Do not run:
+
+- `git commit`
+- `git push`
+- `git merge`
+
+## Working Rules
+
+- Read adjacent code and tests before editing.
+- Keep changes scoped to the task.
+- Do not revert unrelated user or concurrent changes.
+- Fix root causes rather than masking symptoms.
+- Prefer existing local helpers and platform patterns over new abstractions.

package/dist/templates/reasonix/index.d.ts

@@ -0,0 +1,13 @@
+/**
+ * Reasonix template module.
+ *
+ * Reasonix (DeepSeek-Reasonix) is a DeepSeek-native AI coding agent.
+ * It stores skills as `.reasonix/skills/<name>/SKILL.md` (Markdown + frontmatter).
+ *
+ * Subagent skills (trellis-implement, trellis-check) use `runAs: subagent`
+ * frontmatter so Reasonix spawns them as isolated subagent loops.
+ */
+import { type AgentTemplate } from "../template-utils.js";
+/** Subagent skill definitions (trellis-implement, trellis-check). */
+export declare function getAllAgents(): AgentTemplate[];
+//# sourceMappingURL=index.d.ts.map

package/dist/templates/reasonix/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/templates/reasonix/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAEH,OAAO,EAAwB,KAAK,aAAa,EAAE,MAAM,sBAAsB,CAAC;AAIhF,qEAAqE;AACrE,wBAAgB,YAAY,IAAI,aAAa,EAAE,CAE9C"}

package/dist/templates/reasonix/index.js

@@ -0,0 +1,16 @@
+/**
+ * Reasonix template module.
+ *
+ * Reasonix (DeepSeek-Reasonix) is a DeepSeek-native AI coding agent.
+ * It stores skills as `.reasonix/skills/<name>/SKILL.md` (Markdown + frontmatter).
+ *
+ * Subagent skills (trellis-implement, trellis-check) use `runAs: subagent`
+ * frontmatter so Reasonix spawns them as isolated subagent loops.
+ */
+import { createTemplateReader } from "../template-utils.js";
+const { listMdAgents } = createTemplateReader(import.meta.url);
+/** Subagent skill definitions (trellis-implement, trellis-check). */
+export function getAllAgents() {
+    return listMdAgents();
+}
+//# sourceMappingURL=index.js.map

package/dist/templates/reasonix/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/templates/reasonix/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAEH,OAAO,EAAE,oBAAoB,EAAsB,MAAM,sBAAsB,CAAC;AAEhF,MAAM,EAAE,YAAY,EAAE,GAAG,oBAAoB,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;AAE/D,qEAAqE;AACrE,MAAM,UAAU,YAAY;IAC1B,OAAO,YAAY,EAAE,CAAC;AACxB,CAAC"}

package/dist/templates/shared-hooks/index.d.ts

@@ -0,0 +1,58 @@
+/**
+ * Shared hook templates — platform-independent Python hook scripts.
+ *
+ * These scripts read only from .cviauto/ paths (JSONL, prd.md, spec/) and
+ * have no platform-specific placeholders. They can be written as-is to any
+ * platform's hooks directory.
+ */
+export interface HookScript {
+    /** Filename (e.g., "session-start.py") */
+    name: string;
+    /** Script content — no placeholders, ready to write directly */
+    content: string;
+}
+export type SharedHookName = "session-start.py" | "inject-shell-session-context.py" | "inject-workflow-state.py" | "inject-subagent-context.py";
+export type SharedHookPlatform = "claude" | "cursor" | "codex" | "gemini" | "qoder" | "copilot" | "codebuddy" | "droid" | "kiro" | "trae";
+/**
+ * Which shared hooks each platform actually invokes. Single source of truth
+ * for shared-hook distribution — both `writeSharedHooks` (runtime install)
+ * and `collectSharedHooks` (`cviauto update` diff) read from this table.
+ *
+ * Routing rules encoded here:
+ * - `session-start.py` — shipped by every platform with a SessionStart
+ *   hook event *except* codex + copilot, which bundle a platform-specific
+ *   session-start.py under their own template dirs.
+ * - `inject-workflow-state.py` — every platform with a UserPromptSubmit
+ *   (or equivalent) event. Kiro + codex self-included; platforms without
+ *   per-turn main-session hooks are excluded.
+ * - `inject-subagent-context.py` — class-1 (push-based) platforms only.
+ *   Class-2 (pull-based) platforms (codex, copilot, gemini, qoder) can't
+ *   have hooks mutate sub-agent prompts — their sub-agents load context
+ *   via a prelude instead.
+ * - Kiro supports per-turn + spawn hooks on both surfaces (per the official
+ *   docs https://kiro.dev/docs/cli/hooks/): the CLI custom agent declares
+ *   `hooks.userPromptSubmit` + `hooks.agentSpawn`, and the IDE declares a
+ *   `.kiro.hook` with `when.type=promptSubmit`. So Kiro ships
+ *   `session-start.py` (agentSpawn overview), `inject-workflow-state.py`
+ *   (per-turn breadcrumb), and `inject-subagent-context.py` (sub-agent
+ *   spawn). The scripts emit a plain-text Kiro branch — Kiro adds a hook's
+ *   stdout directly to the conversation context (no JSON envelope).
+ * - Claude Code `statusLine` is intentionally not installed by default.
+ *   Users can add their own statusLine command in `.claude/settings.json`,
+ *   or opt in to the Trellis one via `cviauto init --with-statusline`
+ *   (installed from `templates/claude/hooks/`, not from this table — no
+ *   other platform has a statusLine event).
+ */
+export declare const SHARED_HOOKS_BY_PLATFORM: Record<SharedHookPlatform, readonly SharedHookName[]>;
+/**
+ * Get all shared hook scripts. Content is platform-independent and can be
+ * written directly without placeholder resolution.
+ */
+export declare function getSharedHookScripts(): HookScript[];
+/**
+ * Get the shared hook scripts that a given platform actually registers.
+ * Drives both `writeSharedHooks` and `collectSharedHooks` so distribution
+ * never drifts from the per-platform capability declared above.
+ */
+export declare function getSharedHookScriptsForPlatform(platform: SharedHookPlatform): HookScript[];
+//# sourceMappingURL=index.d.ts.map

package/dist/templates/shared-hooks/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/templates/shared-hooks/index.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAaH,MAAM,WAAW,UAAU;IACzB,0CAA0C;IAC1C,IAAI,EAAE,MAAM,CAAC;IACb,gEAAgE;IAChE,OAAO,EAAE,MAAM,CAAC;CACjB;AAED,MAAM,MAAM,cAAc,GACtB,kBAAkB,GAClB,iCAAiC,GACjC,0BAA0B,GAC1B,4BAA4B,CAAC;AAEjC,MAAM,MAAM,kBAAkB,GAC1B,QAAQ,GACR,QAAQ,GACR,OAAO,GACP,QAAQ,GACR,OAAO,GACP,SAAS,GACT,WAAW,GACX,OAAO,GACP,MAAM,GACN,MAAM,CAAC;AAEX;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,eAAO,MAAM,wBAAwB,EAAE,MAAM,CAC3C,kBAAkB,EAClB,SAAS,cAAc,EAAE,CAgC1B,CAAC;AAEF;;;GAGG;AACH,wBAAgB,oBAAoB,IAAI,UAAU,EAAE,CAWnD;AAED;;;;GAIG;AACH,wBAAgB,+BAA+B,CAC7C,QAAQ,EAAE,kBAAkB,GAC3B,UAAU,EAAE,CAGd"}