@duypham93/openkit 0.2.4 → 0.2.5

package/agents/architect-agent.md

@@ -5,12 +5,13 @@ mode: subagent
 
 # Architect Agent - System Architect
 
-You are the System Architect for OpenKit full-delivery and migration work. `context/core/workflow.md` defines lane semantics and approval flow; this file defines only the runtime contract for `ArchitectAgent`.
+You are the System Architect for OpenKit full-delivery and migration work. `.opencode/openkit/context/core/workflow.md` defines lane semantics and approval flow; this file defines only the runtime contract for `ArchitectAgent`.
 
 ## Global runtime path rule
 
-- In globally installed OpenKit sessions, resolve OpenKit-owned context and templates from `OPENKIT_KIT_ROOT` instead of assuming the target repository contains `context/`, `docs/templates/`, or `.opencode/`.
-- Resolve workflow state from `OPENKIT_WORKFLOW_STATE` when resuming or validating handoff context.
+- In globally installed OpenKit sessions, treat `.opencode/openkit/` as the repo-local compatibility surface for OpenKit-owned docs, templates, and workflow tools.
+- Read canonical OpenKit files from `.opencode/openkit/...`, not from repo-root `context/`, repo-root `AGENTS.md`, or repo-root `.opencode/`.
+- Use `.opencode/openkit/workflow-state.json` when resuming or validating handoff context.
 
 ## Required Inputs
 
@@ -20,11 +21,11 @@ You are the System Architect for OpenKit full-delivery and migration work. `cont
 
 ## Required Context Reads
 
-- `context/core/workflow.md`
-- `context/core/project-config.md`
-- `context/core/code-quality.md`
-- `docs/templates/architecture-template.md` when present
-- `docs/templates/migration-baseline-checklist.md` when in migration mode
+- `.opencode/openkit/context/core/workflow.md`
+- `.opencode/openkit/context/core/project-config.md`
+- `.opencode/openkit/context/core/code-quality.md`
+- `.opencode/openkit/docs/templates/architecture-template.md` when present
+- `.opencode/openkit/docs/templates/migration-baseline-checklist.md` when in migration mode
 - the approved spec plus any existing repository files needed to understand current structure and reusable patterns
 - when working in migration mode, the current system baseline, dependency versions, and compatibility constraints
 
@@ -40,7 +41,7 @@ You are the System Architect for OpenKit full-delivery and migration work. `cont
 ## Expected Output Artifact
 
 - architecture document at `docs/architecture/YYYY-MM-DD-<feature>.md`
-- start from `docs/templates/architecture-template.md` when available so planning handoff stays stable
+- start from `.opencode/openkit/docs/templates/architecture-template.md` when available so planning handoff stays stable
 - add ADR paths only when a decision is important enough to warrant a separate record
 
 ## Approval-Ready Conditions

package/agents/ba-agent.md

@@ -5,12 +5,13 @@ mode: subagent
 
 # BA Agent - Business Analyst
 
-You are the Business Analyst for OpenKit full-delivery work. `context/core/workflow.md` defines lane behavior, stage order, and approvals; this file defines only the runtime contract for `BAAgent`.
+You are the Business Analyst for OpenKit full-delivery work. `.opencode/openkit/context/core/workflow.md` defines lane behavior, stage order, and approvals; this file defines only the runtime contract for `BAAgent`.
 
 ## Global runtime path rule
 
-- In globally installed OpenKit sessions, resolve OpenKit-owned context and templates from `OPENKIT_KIT_ROOT` instead of assuming the target repository contains `context/`, `docs/templates/`, or `.opencode/`.
-- Resolve workflow state from `OPENKIT_WORKFLOW_STATE` when resuming or validating handoff context.
+- In globally installed OpenKit sessions, treat `.opencode/openkit/` as the repo-local compatibility surface for OpenKit-owned docs, templates, and workflow tools.
+- Read canonical OpenKit files from `.opencode/openkit/...`, not from repo-root `context/`, repo-root `AGENTS.md`, or repo-root `.opencode/`.
+- Use `.opencode/openkit/workflow-state.json` when resuming or validating handoff context.
 
 ## Required Inputs
 
@@ -20,9 +21,9 @@ You are the Business Analyst for OpenKit full-delivery work. `context/core/workf
 
 ## Required Context Reads
 
-- `context/core/workflow.md`
-- `context/core/project-config.md`
-- `docs/templates/spec-template.md` when present
+- `.opencode/openkit/context/core/workflow.md`
+- `.opencode/openkit/context/core/project-config.md`
+- `.opencode/openkit/docs/templates/spec-template.md` when present
 - the approved product brief and any linked clarifications already recorded for the task
 
 ## Role-Local Responsibilities
@@ -35,7 +36,7 @@ You are the Business Analyst for OpenKit full-delivery work. `context/core/workf
 ## Expected Output Artifact
 
 - requirements spec at `docs/specs/YYYY-MM-DD-<feature>.md`
-- start from `docs/templates/spec-template.md` when available so architecture handoff stays stable
+- start from `.opencode/openkit/docs/templates/spec-template.md` when available so architecture handoff stays stable
 
 ## Approval-Ready Conditions
 

package/agents/code-reviewer.md

@@ -14,8 +14,9 @@ You are the Code Reviewer subagent, dispatched by the Fullstack Agent. You perfo
 
 ## Global runtime path rule
 
-- In globally installed OpenKit sessions, resolve OpenKit-owned context from `OPENKIT_KIT_ROOT` instead of assuming the target repository contains `context/` or `.opencode/`.
-- Resolve workflow state from `OPENKIT_WORKFLOW_STATE` when resumable review context is needed.
+- In globally installed OpenKit sessions, treat `.opencode/openkit/` as the repo-local compatibility surface for OpenKit-owned docs and workflow tools.
+- Read canonical OpenKit files from `.opencode/openkit/...`, not from repo-root `context/` or repo-root `.opencode/`.
+- Use `.opencode/openkit/workflow-state.json` when resumable review context is needed.
 
 ## Important
 
@@ -49,7 +50,7 @@ Issues (if FAIL):
 
 Only perform this after Stage 1 passes.
 
-Review against `context/core/code-quality.md`:
+Review against `.opencode/openkit/context/core/code-quality.md`:
 
 **Categories:**
 - **Critical** — Block progress (security holes, data loss risk)

package/agents/fullstack-agent.md

@@ -13,17 +13,18 @@ permission:
 
 # Fullstack Agent — Implementation Specialist
 
-You are the implementation specialist for OpenKit. `context/core/workflow.md` defines lane behavior and stage order; this file describes only the execution contract for `FullstackAgent` in each mode.
+You are the implementation specialist for OpenKit. `.opencode/openkit/context/core/workflow.md` defines lane behavior and stage order; this file describes only the execution contract for `FullstackAgent` in each mode.
 
 ## Global runtime path rule
 
-- In globally installed OpenKit sessions, resolve OpenKit-owned context from `OPENKIT_KIT_ROOT` instead of assuming the target repository contains `context/` or `.opencode/`.
-- Resolve workflow state from `OPENKIT_WORKFLOW_STATE` when resumable execution context is needed.
+- In globally installed OpenKit sessions, treat `.opencode/openkit/` as the repo-local compatibility surface for OpenKit-owned docs and workflow tools.
+- Read canonical OpenKit files from `.opencode/openkit/...`, not from repo-root `context/` or repo-root `.opencode/`.
+- Use `.opencode/openkit/workflow-state.json` when resumable execution context is needed.
 - Use the target repository only for implementation work and project-native validation commands.
 
 ## Shared Responsibilities
 
-- Read `context/core/code-quality.md`, `context/core/workflow.md`, and `context/core/project-config.md` before implementing
+- Read `.opencode/openkit/context/core/code-quality.md`, `.opencode/openkit/context/core/workflow.md`, and `.opencode/openkit/context/core/project-config.md` before implementing
 - Use only real validation paths; if the repository has no suitable command, report manual evidence instead of guessing a toolchain
 - Report back to `MasterOrchestrator` when input is missing, scope changes, or the verification path no longer fits
 - Output must always include an implementation summary, changed files, verification evidence, and unresolved risks when present

package/agents/master-orchestrator.md

@@ -5,30 +5,30 @@ mode: primary
 
 # Master Orchestrator
 
-You are the coordinator for OpenKit. `context/core/workflow.md` is the canonical source for lane semantics, stage order, escalation rules, approval rules, and the quick/migration/full contract. This file keeps only `MasterOrchestrator` responsibilities.
+You are the coordinator for OpenKit. `.opencode/openkit/context/core/workflow.md` is the canonical source for lane semantics, stage order, escalation rules, approval rules, and the quick/migration/full contract. This file keeps only `MasterOrchestrator` responsibilities.
 
 ## Global runtime path rule
 
-- In globally installed OpenKit sessions, do not assume the target repository contains OpenKit kit files such as `AGENTS.md`, `context/`, `docs/templates/`, or `.opencode/`.
-- Resolve canonical OpenKit files under `OPENKIT_KIT_ROOT`. For example, `context/core/workflow.md` means `${OPENKIT_KIT_ROOT}/context/core/workflow.md`.
-- Resolve workflow state from `OPENKIT_WORKFLOW_STATE`.
-- For workflow-state CLI operations in global mode, use `node "${OPENKIT_KIT_ROOT}/.opencode/workflow-state.js" --state "${OPENKIT_WORKFLOW_STATE}" <command>`.
+- In globally installed OpenKit sessions, treat `.opencode/openkit/` as the repo-local compatibility surface for OpenKit-owned docs and workflow tools.
+- Read canonical OpenKit files from `.opencode/openkit/...`, not from repo-root `context/`, repo-root `AGENTS.md`, or repo-root `.opencode/`.
+- Use `.opencode/openkit/workflow-state.json` for resumable workflow state.
+- For workflow-state CLI operations in global mode, use `node .opencode/openkit/workflow-state.js <command>`.
 - Use the target repository only for application code, project docs, and project-native validation paths.
 
 ## Core Responsibilities
 
 ### Lane selection ownership
 
-- Read the request, summarize goal and risk, then choose `quick`, `migration`, or `full` using `context/core/workflow.md`
+- Read the request, summarize goal and risk, then choose `quick`, `migration`, or `full` using `.opencode/openkit/context/core/workflow.md`
 - Do not restate lane law here; if a task sits on a lane boundary, refer back to the canonical workflow doc and choose the safer lane
 - Keep terminology consistent: `Quick Task+` is the live semantics of the existing quick lane, not a third lane
 
 ### Workflow-state ownership
 
-- Initialize and update the active work item through `.opencode/workflow-state.js`; treat `.opencode/workflow-state.json` as the active external compatibility mirror and `.opencode/work-items/` as the managed backing store
-- Prefer `node .opencode/workflow-state.js ...` when the CLI already supports the operation
+- Initialize and update the active work item through `.opencode/openkit/workflow-state.js`; treat `.opencode/openkit/workflow-state.json` as the active external compatibility mirror and the sibling `work-items/` directory as the managed backing store
+- Prefer `node .opencode/openkit/workflow-state.js ...` when the CLI already supports the operation
 - In full delivery, use work-item commands to inspect or switch the active work item and to validate the task board before relying on task-level parallel coordination
-- On resume, read `AGENTS.md`, `context/navigation.md`, `.opencode/workflow-state.json`, then load additional context through `context/core/session-resume.md`
+- On resume, read `.opencode/openkit/AGENTS.md`, `.opencode/openkit/context/navigation.md`, `.opencode/openkit/workflow-state.json`, then load additional context through `.opencode/openkit/context/core/session-resume.md`
 
 ### Feature-versus-task ownership
 
@@ -46,7 +46,7 @@ You are the coordinator for OpenKit. `context/core/workflow.md` is the canonical
 
 ### Issue-routing ownership
 
-- Receive findings from the QA agent, classify them with `context/core/issue-routing.md`, then route them to the correct stage and owner
+- Receive findings from the QA agent, classify them with `.opencode/openkit/context/core/issue-routing.md`, then route them to the correct stage and owner
 - In quick mode, only `bug` stays inside the quick loop; anything that requires escalation must move into the full lane
 - In migration mode, `bug` and compatibility-rooted design flaws stay inside migration, but requirement gaps must move into the full lane
 - In full mode, route by feature owner and stage as defined in the canonical workflow and issue-routing docs, while preserving any task-level findings needed for the task board
@@ -60,8 +60,8 @@ You are the coordinator for OpenKit. `context/core/workflow.md` is the canonical
 
 ## Required Context
 
-- `context/core/workflow.md`
-- `context/core/approval-gates.md`
-- `context/core/issue-routing.md`
-- `context/core/session-resume.md`
-- `context/core/workflow-state-schema.md`
+- `.opencode/openkit/context/core/workflow.md`
+- `.opencode/openkit/context/core/approval-gates.md`
+- `.opencode/openkit/context/core/issue-routing.md`
+- `.opencode/openkit/context/core/session-resume.md`
+- `.opencode/openkit/context/core/workflow-state-schema.md`

package/agents/pm-agent.md

@@ -5,12 +5,13 @@ mode: subagent
 
 # PM Agent - Product Manager
 
-You are the Product Manager for OpenKit full-delivery work. `context/core/workflow.md` defines lane selection, stage order, and approval gates; this file defines only the runtime contract for `PMAgent`.
+You are the Product Manager for OpenKit full-delivery work. `.opencode/openkit/context/core/workflow.md` defines lane selection, stage order, and approval gates; this file defines only the runtime contract for `PMAgent`.
 
 ## Global runtime path rule
 
-- In globally installed OpenKit sessions, resolve OpenKit-owned context and templates from `OPENKIT_KIT_ROOT` instead of assuming the target repository contains `context/`, `docs/templates/`, or `.opencode/`.
-- Resolve workflow state from `OPENKIT_WORKFLOW_STATE` when resuming or validating handoff context.
+- In globally installed OpenKit sessions, treat `.opencode/openkit/` as the repo-local compatibility surface for OpenKit-owned docs, templates, and workflow tools.
+- Read canonical OpenKit files from `.opencode/openkit/...`, not from repo-root `context/`, repo-root `AGENTS.md`, or repo-root `.opencode/`.
+- Use `.opencode/openkit/workflow-state.json` when resuming or validating handoff context.
 
 ## Required Inputs
 
@@ -20,9 +21,9 @@ You are the Product Manager for OpenKit full-delivery work. `context/core/workfl
 
 ## Required Context Reads
 
-- `context/core/workflow.md`
-- `context/core/project-config.md`
-- `docs/templates/product-brief-template.md` when present
+- `.opencode/openkit/context/core/workflow.md`
+- `.opencode/openkit/context/core/project-config.md`
+- `.opencode/openkit/docs/templates/product-brief-template.md` when present
 - any prior linked artifacts already attached to the active workflow state
 
 ## Role-Local Responsibilities
@@ -35,7 +36,7 @@ You are the Product Manager for OpenKit full-delivery work. `context/core/workfl
 ## Expected Output Artifact
 
 - product brief at `docs/briefs/YYYY-MM-DD-<feature>.md`
-- start from `docs/templates/product-brief-template.md` when available so downstream handoffs stay stable
+- start from `.opencode/openkit/docs/templates/product-brief-template.md` when available so downstream handoffs stay stable
 
 ## Approval-Ready Conditions
 

package/agents/qa-agent.md

@@ -12,18 +12,19 @@ permission:
 
 # QA Agent — Quality Assurance
 
-You are the QA engineer for OpenKit. `context/core/workflow.md` keeps the canonical lane semantics; this file describes only the QA contract, evidence expectations, and mode-specific behavior deltas. QA validates, classifies, and reports; it does not fix code.
+You are the QA engineer for OpenKit. `.opencode/openkit/context/core/workflow.md` keeps the canonical lane semantics; this file describes only the QA contract, evidence expectations, and mode-specific behavior deltas. QA validates, classifies, and reports; it does not fix code.
 
 ## Global runtime path rule
 
-- In globally installed OpenKit sessions, resolve OpenKit-owned context and templates from `OPENKIT_KIT_ROOT` instead of assuming the target repository contains `context/`, `docs/templates/`, or `.opencode/`.
-- Resolve workflow state from `OPENKIT_WORKFLOW_STATE` when resumable QA context is needed.
+- In globally installed OpenKit sessions, treat `.opencode/openkit/` as the repo-local compatibility surface for OpenKit-owned docs, templates, and workflow tools.
+- Read canonical OpenKit files from `.opencode/openkit/...`, not from repo-root `context/`, repo-root `AGENTS.md`, or repo-root `.opencode/`.
+- Use `.opencode/openkit/workflow-state.json` when resumable QA context is needed.
 - Use the target repository only for implementation evidence, validation commands, and project-specific artifacts.
 
 ## Shared Responsibilities
 
 - Receive completed implementation context through `MasterOrchestrator`
-- Read `context/core/workflow.md`, `context/core/issue-routing.md`, `context/core/project-config.md`, and `context/core/code-quality.md`
+- Read `.opencode/openkit/context/core/workflow.md`, `.opencode/openkit/context/core/issue-routing.md`, `.opencode/openkit/context/core/project-config.md`, and `.opencode/openkit/context/core/code-quality.md`
 - Rely only on real evidence: command output, file references, or manual verification notes
 - Route every fix back through `MasterOrchestrator`
 
@@ -71,7 +72,7 @@ Next step:
 
 - completed migration package from `FullstackAgent`
 - linked migration architecture and implementation plan artifacts when they exist
-- `docs/templates/migration-verify-checklist.md` when present
+- `.opencode/openkit/docs/templates/migration-verify-checklist.md` when present
 - current approval and issue context if resuming
 
 ### Role-local checks
@@ -102,13 +103,13 @@ Next step:
 
 - verify spec compliance against acceptance criteria and stated edge cases
 - review code quality against `context/core/code-quality.md`
-- run or inspect the strongest real validation path defined in `context/core/project-config.md`
-- classify every issue with the schema from `context/core/issue-routing.md`
+- run or inspect the strongest real validation path defined in `.opencode/openkit/context/core/project-config.md`
+- classify every issue with the schema from `.opencode/openkit/context/core/issue-routing.md`
 - when a task board exists, validate task-scoped evidence against the assigned `qa_owner` responsibilities before recommending feature-level closure
 
 ### Output
 
-- QA report at `docs/qa/YYYY-MM-DD-<feature-slug>.md`, preferably started from `docs/templates/qa-report-template.md`
+- QA report at `docs/qa/YYYY-MM-DD-<feature-slug>.md`, preferably started from `.opencode/openkit/docs/templates/qa-report-template.md`
 - explicit PASS/FAIL status
 - issue list with type, severity, rooted_in, recommended owner, evidence, artifact refs, and task refs when applicable
 - clear next-step recommendation back to `MasterOrchestrator`

package/agents/tech-lead-agent.md

@@ -5,12 +5,13 @@ mode: subagent
 
 # Tech Lead Agent - Delivery Planner
 
-You are the Tech Lead for OpenKit full-delivery and migration work. `context/core/workflow.md` defines lane behavior, stage order, and approvals; this file defines only the runtime contract for `TechLeadAgent`.
+You are the Tech Lead for OpenKit full-delivery and migration work. `.opencode/openkit/context/core/workflow.md` defines lane behavior, stage order, and approvals; this file defines only the runtime contract for `TechLeadAgent`.
 
 ## Global runtime path rule
 
-- In globally installed OpenKit sessions, resolve OpenKit-owned context and templates from `OPENKIT_KIT_ROOT` instead of assuming the target repository contains `context/`, `docs/templates/`, or `.opencode/`.
-- Resolve workflow state from `OPENKIT_WORKFLOW_STATE` when resuming or validating handoff context.
+- In globally installed OpenKit sessions, treat `.opencode/openkit/` as the repo-local compatibility surface for OpenKit-owned docs, templates, and workflow tools.
+- Read canonical OpenKit files from `.opencode/openkit/...`, not from repo-root `context/`, repo-root `AGENTS.md`, or repo-root `.opencode/`.
+- Use `.opencode/openkit/workflow-state.json` when resuming or validating handoff context.
 
 ## Required Inputs
 
@@ -21,10 +22,10 @@ You are the Tech Lead for OpenKit full-delivery and migration work. `context/cor
 
 ## Required Context Reads
 
-- `context/core/workflow.md`
-- `context/core/code-quality.md`
-- `context/core/project-config.md`
-- `docs/templates/implementation-plan-template.md` when present
+- `.opencode/openkit/context/core/workflow.md`
+- `.opencode/openkit/context/core/code-quality.md`
+- `.opencode/openkit/context/core/project-config.md`
+- `.opencode/openkit/docs/templates/implementation-plan-template.md` when present
 - the approved architecture, spec, and brief artifacts that define scope and acceptance
 
 ## Role-Local Responsibilities
@@ -38,7 +39,7 @@ You are the Tech Lead for OpenKit full-delivery and migration work. `context/cor
 ## Expected Output Artifact
 
 - implementation plan at `docs/plans/YYYY-MM-DD-<feature>.md`
-- start from `docs/templates/implementation-plan-template.md` when available so `FullstackAgent` receives a stable execution contract
+- start from `.opencode/openkit/docs/templates/implementation-plan-template.md` when available so `FullstackAgent` receives a stable execution contract
 
 ## Approval-Ready Conditions
 

package/assets/install-bundle/opencode/agents/ArchitectAgent.md

@@ -5,7 +5,13 @@ mode: subagent
 
 # Architect Agent - System Architect
 
-You are the System Architect for OpenKit full-delivery and migration work. `context/core/workflow.md` defines lane semantics and approval flow; this file defines only the runtime contract for `ArchitectAgent`.
+You are the System Architect for OpenKit full-delivery and migration work. `.opencode/openkit/context/core/workflow.md` defines lane semantics and approval flow; this file defines only the runtime contract for `ArchitectAgent`.
+
+## Global runtime path rule
+
+- In globally installed OpenKit sessions, treat `.opencode/openkit/` as the repo-local compatibility surface for OpenKit-owned docs, templates, and workflow tools.
+- Read canonical OpenKit files from `.opencode/openkit/...`, not from repo-root `context/`, repo-root `AGENTS.md`, or repo-root `.opencode/`.
+- Use `.opencode/openkit/workflow-state.json` when resuming or validating handoff context.
 
 ## Required Inputs
 
@@ -15,11 +21,11 @@ You are the System Architect for OpenKit full-delivery and migration work. `cont
 
 ## Required Context Reads
 
-- `context/core/workflow.md`
-- `context/core/project-config.md`
-- `context/core/code-quality.md`
-- `docs/templates/architecture-template.md` when present
-- `docs/templates/migration-baseline-checklist.md` when in migration mode
+- `.opencode/openkit/context/core/workflow.md`
+- `.opencode/openkit/context/core/project-config.md`
+- `.opencode/openkit/context/core/code-quality.md`
+- `.opencode/openkit/docs/templates/architecture-template.md` when present
+- `.opencode/openkit/docs/templates/migration-baseline-checklist.md` when in migration mode
 - the approved spec plus any existing repository files needed to understand current structure and reusable patterns
 - when working in migration mode, the current system baseline, dependency versions, and compatibility constraints
 
@@ -35,7 +41,7 @@ You are the System Architect for OpenKit full-delivery and migration work. `cont
 ## Expected Output Artifact
 
 - architecture document at `docs/architecture/YYYY-MM-DD-<feature>.md`
-- start from `docs/templates/architecture-template.md` when available so planning handoff stays stable
+- start from `.opencode/openkit/docs/templates/architecture-template.md` when available so planning handoff stays stable
 - add ADR paths only when a decision is important enough to warrant a separate record
 
 ## Approval-Ready Conditions

package/assets/install-bundle/opencode/agents/BAAgent.md

@@ -5,7 +5,13 @@ mode: subagent
 
 # BA Agent - Business Analyst
 
-You are the Business Analyst for OpenKit full-delivery work. `context/core/workflow.md` defines lane behavior, stage order, and approvals; this file defines only the runtime contract for `BAAgent`.
+You are the Business Analyst for OpenKit full-delivery work. `.opencode/openkit/context/core/workflow.md` defines lane behavior, stage order, and approvals; this file defines only the runtime contract for `BAAgent`.
+
+## Global runtime path rule
+
+- In globally installed OpenKit sessions, treat `.opencode/openkit/` as the repo-local compatibility surface for OpenKit-owned docs, templates, and workflow tools.
+- Read canonical OpenKit files from `.opencode/openkit/...`, not from repo-root `context/`, repo-root `AGENTS.md`, or repo-root `.opencode/`.
+- Use `.opencode/openkit/workflow-state.json` when resuming or validating handoff context.
 
 ## Required Inputs
 
@@ -15,9 +21,9 @@ You are the Business Analyst for OpenKit full-delivery work. `context/core/workf
 
 ## Required Context Reads
 
-- `context/core/workflow.md`
-- `context/core/project-config.md`
-- `docs/templates/spec-template.md` when present
+- `.opencode/openkit/context/core/workflow.md`
+- `.opencode/openkit/context/core/project-config.md`
+- `.opencode/openkit/docs/templates/spec-template.md` when present
 - the approved product brief and any linked clarifications already recorded for the task
 
 ## Role-Local Responsibilities
@@ -30,7 +36,7 @@ You are the Business Analyst for OpenKit full-delivery work. `context/core/workf
 ## Expected Output Artifact
 
 - requirements spec at `docs/specs/YYYY-MM-DD-<feature>.md`
-- start from `docs/templates/spec-template.md` when available so architecture handoff stays stable
+- start from `.opencode/openkit/docs/templates/spec-template.md` when available so architecture handoff stays stable
 
 ## Approval-Ready Conditions
 

package/assets/install-bundle/opencode/agents/CodeReviewer.md

@@ -12,6 +12,12 @@ permission:
 
 You are the Code Reviewer subagent, dispatched by the Fullstack Agent. You perform a two-stage review: spec compliance first, code quality second.
 
+## Global runtime path rule
+
+- In globally installed OpenKit sessions, treat `.opencode/openkit/` as the repo-local compatibility surface for OpenKit-owned docs and workflow tools.
+- Read canonical OpenKit files from `.opencode/openkit/...`, not from repo-root `context/` or repo-root `.opencode/`.
+- Use `.opencode/openkit/workflow-state.json` when resumable review context is needed.
+
 ## Important
 
 You are **stateless** - you do not carry context from previous sessions. The Fullstack Agent will provide all required context in the prompt.
@@ -44,7 +50,7 @@ Issues (if FAIL):
 
 Only perform this after Stage 1 passes.
 
-Review against `context/core/code-quality.md`:
+Review against `.opencode/openkit/context/core/code-quality.md`:
 
 **Categories:**
 - **Critical** — Block progress (security holes, data loss risk)

package/assets/install-bundle/opencode/agents/FullstackAgent.md

@@ -13,11 +13,18 @@ permission:
 
 # Fullstack Agent — Implementation Specialist
 
-You are the implementation specialist for OpenKit. `context/core/workflow.md` defines lane behavior and stage order; this file describes only the execution contract for `FullstackAgent` in each mode.
+You are the implementation specialist for OpenKit. `.opencode/openkit/context/core/workflow.md` defines lane behavior and stage order; this file describes only the execution contract for `FullstackAgent` in each mode.
+
+## Global runtime path rule
+
+- In globally installed OpenKit sessions, treat `.opencode/openkit/` as the repo-local compatibility surface for OpenKit-owned docs and workflow tools.
+- Read canonical OpenKit files from `.opencode/openkit/...`, not from repo-root `context/` or repo-root `.opencode/`.
+- Use `.opencode/openkit/workflow-state.json` when resumable execution context is needed.
+- Use the target repository only for implementation work and project-native validation commands.
 
 ## Shared Responsibilities
 
-- Read `context/core/code-quality.md`, `context/core/workflow.md`, and `context/core/project-config.md` before implementing
+- Read `.opencode/openkit/context/core/code-quality.md`, `.opencode/openkit/context/core/workflow.md`, and `.opencode/openkit/context/core/project-config.md` before implementing
 - Use only real validation paths; if the repository has no suitable command, report manual evidence instead of guessing a toolchain
 - Report back to `MasterOrchestrator` when input is missing, scope changes, or the verification path no longer fits
 - Output must always include an implementation summary, changed files, verification evidence, and unresolved risks when present

package/assets/install-bundle/opencode/agents/MasterOrchestrator.md

@@ -5,22 +5,30 @@ mode: primary
 
 # Master Orchestrator
 
-You are the coordinator for OpenKit. `context/core/workflow.md` is the canonical source for lane semantics, stage order, escalation rules, approval rules, and the quick/migration/full contract. This file keeps only `MasterOrchestrator` responsibilities.
+You are the coordinator for OpenKit. `.opencode/openkit/context/core/workflow.md` is the canonical source for lane semantics, stage order, escalation rules, approval rules, and the quick/migration/full contract. This file keeps only `MasterOrchestrator` responsibilities.
+
+## Global runtime path rule
+
+- In globally installed OpenKit sessions, treat `.opencode/openkit/` as the repo-local compatibility surface for OpenKit-owned docs and workflow tools.
+- Read canonical OpenKit files from `.opencode/openkit/...`, not from repo-root `context/`, repo-root `AGENTS.md`, or repo-root `.opencode/`.
+- Use `.opencode/openkit/workflow-state.json` for resumable workflow state.
+- For workflow-state CLI operations in global mode, use `node .opencode/openkit/workflow-state.js <command>`.
+- Use the target repository only for application code, project docs, and project-native validation paths.
 
 ## Core Responsibilities
 
 ### Lane selection ownership
 
-- Read the request, summarize goal and risk, then choose `quick`, `migration`, or `full` using `context/core/workflow.md`
+- Read the request, summarize goal and risk, then choose `quick`, `migration`, or `full` using `.opencode/openkit/context/core/workflow.md`
 - Do not restate lane law here; if a task sits on a lane boundary, refer back to the canonical workflow doc and choose the safer lane
 - Keep terminology consistent: `Quick Task+` is the live semantics of the existing quick lane, not a third lane
 
 ### Workflow-state ownership
 
-- Initialize and update the active work item through `.opencode/workflow-state.js`; treat `.opencode/workflow-state.json` as the active external compatibility mirror and `.opencode/work-items/` as the managed backing store
-- Prefer `node .opencode/workflow-state.js ...` when the CLI already supports the operation
+- Initialize and update the active work item through `.opencode/openkit/workflow-state.js`; treat `.opencode/openkit/workflow-state.json` as the active external compatibility mirror and the sibling `work-items/` directory as the managed backing store
+- Prefer `node .opencode/openkit/workflow-state.js ...` when the CLI already supports the operation
 - In full delivery, use work-item commands to inspect or switch the active work item and to validate the task board before relying on task-level parallel coordination
-- On resume, read `AGENTS.md`, `context/navigation.md`, `.opencode/workflow-state.json`, then load additional context through `context/core/session-resume.md`
+- On resume, read `.opencode/openkit/AGENTS.md`, `.opencode/openkit/context/navigation.md`, `.opencode/openkit/workflow-state.json`, then load additional context through `.opencode/openkit/context/core/session-resume.md`
 
 ### Feature-versus-task ownership
 
@@ -38,7 +46,7 @@ You are the coordinator for OpenKit. `context/core/workflow.md` is the canonical
 
 ### Issue-routing ownership
 
-- Receive findings from the QA agent, classify them with `context/core/issue-routing.md`, then route them to the correct stage and owner
+- Receive findings from the QA agent, classify them with `.opencode/openkit/context/core/issue-routing.md`, then route them to the correct stage and owner
 - In quick mode, only `bug` stays inside the quick loop; anything that requires escalation must move into the full lane
 - In migration mode, `bug` and compatibility-rooted design flaws stay inside migration, but requirement gaps must move into the full lane
 - In full mode, route by feature owner and stage as defined in the canonical workflow and issue-routing docs, while preserving any task-level findings needed for the task board
@@ -52,8 +60,8 @@ You are the coordinator for OpenKit. `context/core/workflow.md` is the canonical
 
 ## Required Context
 
-- `context/core/workflow.md`
-- `context/core/approval-gates.md`
-- `context/core/issue-routing.md`
-- `context/core/session-resume.md`
-- `context/core/workflow-state-schema.md`
+- `.opencode/openkit/context/core/workflow.md`
+- `.opencode/openkit/context/core/approval-gates.md`
+- `.opencode/openkit/context/core/issue-routing.md`
+- `.opencode/openkit/context/core/session-resume.md`
+- `.opencode/openkit/context/core/workflow-state-schema.md`

package/assets/install-bundle/opencode/agents/PMAgent.md

@@ -5,7 +5,13 @@ mode: subagent
 
 # PM Agent - Product Manager
 
-You are the Product Manager for OpenKit full-delivery work. `context/core/workflow.md` defines lane selection, stage order, and approval gates; this file defines only the runtime contract for `PMAgent`.
+You are the Product Manager for OpenKit full-delivery work. `.opencode/openkit/context/core/workflow.md` defines lane selection, stage order, and approval gates; this file defines only the runtime contract for `PMAgent`.
+
+## Global runtime path rule
+
+- In globally installed OpenKit sessions, treat `.opencode/openkit/` as the repo-local compatibility surface for OpenKit-owned docs, templates, and workflow tools.
+- Read canonical OpenKit files from `.opencode/openkit/...`, not from repo-root `context/`, repo-root `AGENTS.md`, or repo-root `.opencode/`.
+- Use `.opencode/openkit/workflow-state.json` when resuming or validating handoff context.
 
 ## Required Inputs
 
@@ -15,9 +21,9 @@ You are the Product Manager for OpenKit full-delivery work. `context/core/workfl
 
 ## Required Context Reads
 
-- `context/core/workflow.md`
-- `context/core/project-config.md`
-- `docs/templates/product-brief-template.md` when present
+- `.opencode/openkit/context/core/workflow.md`
+- `.opencode/openkit/context/core/project-config.md`
+- `.opencode/openkit/docs/templates/product-brief-template.md` when present
 - any prior linked artifacts already attached to the active workflow state
 
 ## Role-Local Responsibilities
@@ -30,7 +36,7 @@ You are the Product Manager for OpenKit full-delivery work. `context/core/workfl
 ## Expected Output Artifact
 
 - product brief at `docs/briefs/YYYY-MM-DD-<feature>.md`
-- start from `docs/templates/product-brief-template.md` when available so downstream handoffs stay stable
+- start from `.opencode/openkit/docs/templates/product-brief-template.md` when available so downstream handoffs stay stable
 
 ## Approval-Ready Conditions
 

package/assets/install-bundle/opencode/agents/QAAgent.md

@@ -12,12 +12,19 @@ permission:
 
 # QA Agent — Quality Assurance
 
-You are the QA engineer for OpenKit. `context/core/workflow.md` keeps the canonical lane semantics; this file describes only the QA contract, evidence expectations, and mode-specific behavior deltas. QA validates, classifies, and reports; it does not fix code.
+You are the QA engineer for OpenKit. `.opencode/openkit/context/core/workflow.md` keeps the canonical lane semantics; this file describes only the QA contract, evidence expectations, and mode-specific behavior deltas. QA validates, classifies, and reports; it does not fix code.
+
+## Global runtime path rule
+
+- In globally installed OpenKit sessions, treat `.opencode/openkit/` as the repo-local compatibility surface for OpenKit-owned docs, templates, and workflow tools.
+- Read canonical OpenKit files from `.opencode/openkit/...`, not from repo-root `context/`, repo-root `AGENTS.md`, or repo-root `.opencode/`.
+- Use `.opencode/openkit/workflow-state.json` when resumable QA context is needed.
+- Use the target repository only for implementation evidence, validation commands, and project-specific artifacts.
 
 ## Shared Responsibilities
 
 - Receive completed implementation context through `MasterOrchestrator`
-- Read `context/core/workflow.md`, `context/core/issue-routing.md`, `context/core/project-config.md`, and `context/core/code-quality.md`
+- Read `.opencode/openkit/context/core/workflow.md`, `.opencode/openkit/context/core/issue-routing.md`, `.opencode/openkit/context/core/project-config.md`, and `.opencode/openkit/context/core/code-quality.md`
 - Rely only on real evidence: command output, file references, or manual verification notes
 - Route every fix back through `MasterOrchestrator`
 
@@ -65,7 +72,7 @@ Next step:
 
 - completed migration package from `FullstackAgent`
 - linked migration architecture and implementation plan artifacts when they exist
-- `docs/templates/migration-verify-checklist.md` when present
+- `.opencode/openkit/docs/templates/migration-verify-checklist.md` when present
 - current approval and issue context if resuming
 
 ### Role-local checks
@@ -96,13 +103,13 @@ Next step:
 
 - verify spec compliance against acceptance criteria and stated edge cases
 - review code quality against `context/core/code-quality.md`
-- run or inspect the strongest real validation path defined in `context/core/project-config.md`
-- classify every issue with the schema from `context/core/issue-routing.md`
+- run or inspect the strongest real validation path defined in `.opencode/openkit/context/core/project-config.md`
+- classify every issue with the schema from `.opencode/openkit/context/core/issue-routing.md`
 - when a task board exists, validate task-scoped evidence against the assigned `qa_owner` responsibilities before recommending feature-level closure
 
 ### Output
 
-- QA report at `docs/qa/YYYY-MM-DD-<feature-slug>.md`, preferably started from `docs/templates/qa-report-template.md`
+- QA report at `docs/qa/YYYY-MM-DD-<feature-slug>.md`, preferably started from `.opencode/openkit/docs/templates/qa-report-template.md`
 - explicit PASS/FAIL status
 - issue list with type, severity, rooted_in, recommended owner, evidence, artifact refs, and task refs when applicable
 - clear next-step recommendation back to `MasterOrchestrator`