@blxzer/cursor-trellis 0.3.0 → 0.3.3

package/dist/templates/common/commands/start.md

@@ -8,7 +8,7 @@ Enter or refresh the Trellis Framework Context. This is a dashboard entry surfac
 Identity, git status, selected task, Task Dashboard, journal location.
 
 ```bash
-{{PYTHON_CMD}} ./.trellis/scripts/get_context.py
+{{PYTHON_CMD}} ./.cstl/scripts/get_context.py
 ```
 
 If this output includes a line beginning `Trellis update available:`, copy the full line verbatim when summarizing session context. Do not shorten operational command hints.
@@ -17,18 +17,18 @@ If this output includes a line beginning `Trellis update available:`, copy the f
 Compact Phase Index, request triage rules, planning artifact contract, and the step-detail command.
 
 ```bash
-{{PYTHON_CMD}} ./.trellis/scripts/get_context.py --mode phase
+{{PYTHON_CMD}} ./.cstl/scripts/get_context.py --mode phase
 ```
 
-Full guide in `.trellis/workflow.md` (read on demand).
+Full guide in `.cstl/workflow.md` (read on demand).
 
 ## Step 3: Guideline indexes
 Discover packages + spec layers, then read each relevant index file.
 
 ```bash
-{{PYTHON_CMD}} ./.trellis/scripts/get_context.py --mode packages
-cat .trellis/spec/guides/index.md
-cat .trellis/spec/<package>/<layer>/index.md   # for each relevant layer
+{{PYTHON_CMD}} ./.cstl/scripts/get_context.py --mode packages
+cat .cstl/spec/guides/index.md
+cat .cstl/spec/<package>/<layer>/index.md   # for each relevant layer
 ```
 
 Index files list the specific guideline docs to read when you actually start coding.
@@ -47,7 +47,7 @@ If a task is selected, check the task directory:
 - **Selected task status `planning` + `prd.md` exists** → stay in Planning / Execution Gate. Lightweight tasks can be PRD-only; complex tasks need `design.md` + `implement.md`. Run `task.py start-execution <task> --check` and request explicit execution approval before execution.
 - **Selected task status `in_progress`** → Phase 2 step 2.1. Load the step detail:
   ```bash
-  {{PYTHON_CMD}} ./.trellis/scripts/get_context.py --mode phase --step 2.1 --platform {{CLI_FLAG}}
+  {{PYTHON_CMD}} ./.cstl/scripts/get_context.py --mode phase --step 2.1 --platform {{CLI_FLAG}}
   ```
 - **No selected task** → use dashboard routing. Do not auto-select an existing task.
 
@@ -66,4 +66,4 @@ If a task is selected, check the task directory:
 | Stuck / fixed same bug multiple times | `cstl-break-loop` |
 | Learned something worth capturing | `cstl-update-spec` |
 
-Full rules + anti-rationalization table in `.trellis/workflow.md`.
+Full rules + anti-rationalization table in `.cstl/workflow.md`.

package/dist/templates/common/skills/before-dev.md

@@ -2,14 +2,14 @@ Read the relevant development guidelines before starting your task.
 
 Execute these steps:
 
-1. **Read selected task artifacts**:
+1. **Read selected task artifacts**:
    - `prd.md` for requirements and acceptance criteria
    - `design.md` if present for technical design
    - `implement.md` if present for execution order and validation plan
 
 2. **Discover packages and their spec layers**:
    ```bash
-   python3 ./.trellis/scripts/get_context.py --mode packages
+   python3 ./.cstl/scripts/get_context.py --mode packages
    ```
 
 3. **Identify which specs apply** to your task based on:
@@ -19,7 +19,7 @@ Execute these steps:
 
 4. **Read the spec index** for each relevant module:
    ```bash
-   cat .trellis/spec/<package>/<layer>/index.md
+   cat .cstl/spec/<package>/<layer>/index.md
    ```
    Follow the **"Pre-Development Checklist"** section in the index.
 
@@ -27,7 +27,7 @@ Execute these steps:
 
 6. **Always read shared guides**:
    ```bash
-   cat .trellis/spec/guides/index.md
+   cat .cstl/spec/guides/index.md
    ```
 
 7. Understand the coding standards and patterns you need to follow, then proceed with your development plan.

package/dist/templates/common/skills/brainstorm.md

@@ -47,7 +47,7 @@ Use this skill only after task-creation consent has been given and the user is r
 If no task exists yet, create one:
 
 ```bash
-TASK_DIR=$(python ./.trellis/scripts/task.py create "<short task title>" --slug <slug>)
+TASK_DIR=$(python ./.cstl/scripts/task.py create "<short task title>" --slug <slug>)
 ```
 
 Use a concise title from the user's request. Use a slug without a date prefix. `task.py create` adds the `MM-DD-` directory prefix automatically.
@@ -72,12 +72,12 @@ Run **before** any user interview questions.
 Inspect and record in `prd.md` (sections: **Confirmed facts**, initial **Out of scope**, draft **Goal**):
 
 1. **Code & tests** — relevant modules, fixtures, configs, error paths.
-2. **Specs** — `.trellis/spec/` indexes and layer guides for touched packages.
+2. **Specs** — `.cstl/spec/` indexes and layer guides for touched packages.
 3. **History** — archived tasks, active task research, developer journal when useful.
-4. **Platform** — project platform hooks, agents, and skills (see `.trellis/spec/guides/cursor-subagent-policy.md` when using Cursor); shared `.agents/skills/` when behavior spans platforms.
+4. **Platform** — project platform hooks, agents, and skills (see `.cstl/spec/guides/cursor-subagent-policy.md` when using Cursor); shared `.agents/skills/` when behavior spans platforms.
 5. **Parent/Child** — if multiple independent deliverables, note child split early in `prd.md`.
 
-Use retrieval per `.trellis/spec/guides/retrieval-daily-guide.md` (rg for literals, codegraph for structure, fast-context for semantic sweep).
+Use retrieval per `.cstl/spec/guides/retrieval-daily-guide.md` (rg for literals, codegraph for structure, fast-context for semantic sweep).
 
 Dispatch **`cstl-research`** (writable Agent) when a topic needs a dedicated `{TASK}/research/<topic>.md` file; do **not** use a subagent for PRD Grill itself.
 
@@ -163,7 +163,7 @@ Your recommended answer defaults to Occam's Razor: the **minimal sufficient** op
 - ordered implementation checklist
 - validation commands
 - risky files or rollback points
-- **Development Strategy Contract** (`execution_mode`, `isolation`, …): before finalizing, run `python3 ./.trellis/scripts/task.py suggest-execution-strategy <task-dir>` (or `--json`); reconcile suggestion with scope, then paste the approved YAML block into `implement.md`
+- **Development Strategy Contract** (`execution_mode`, `isolation`, …): before finalizing, run `python3 ./.cstl/scripts/task.py suggest-execution-strategy <task-dir>` (or `--json`); reconcile suggestion with scope, then paste the approved YAML block into `implement.md`
 - follow-up checks before `task.py start-execution --check`
 
 Lightweight tasks may have only `prd.md`. Complex tasks must have `prd.md`, `design.md`, and `implement.md` before `task.py start-execution --check`.

package/dist/templates/common/skills/break-loop.md

@@ -55,8 +55,8 @@ What broader problems does this bug reveal?
 
 Solidify insights into the system:
 
-- [ ] Update `.trellis/spec/guides/` thinking guides
-- [ ] Update relevant `.trellis/spec/` docs
+- [ ] Update `.cstl/spec/guides/` thinking guides
+- [ ] Update relevant `.cstl/spec/` docs
 - [ ] Create issue record (if applicable)
 - [ ] Create feature ticket for root fix
 - [ ] Update check guidelines if needed
@@ -118,7 +118,7 @@ Three levels of insight:
    - If it's a code reuse issue → update `code-reuse-thinking-guide.md`
    - If it's domain-specific → update `backend/*.md` or `frontend/*.md`
 
-2. **Sync templates** - After updating `.trellis/spec/`, sync to `src/templates/markdown/spec/`
+2. **Sync templates** - After updating `.cstl/spec/`, sync to `src/templates/markdown/spec/`
 
 3. **Commit the spec updates** - This is the primary output, not just the analysis text
 

package/dist/templates/common/skills/check.md

@@ -20,13 +20,13 @@ Read the selected task artifacts in order:
 - `implement.md` if present
 
 ```bash
-python ./.trellis/scripts/get_context.py --mode packages
+python ./.cstl/scripts/get_context.py --mode packages
 ```
 
 For each changed package/layer, read the spec index and follow its **Quality Check** section:
 
 ```bash
-cat .trellis/spec/<package>/<layer>/index.md
+cat .cstl/spec/<package>/<layer>/index.md
 ```
 
 Read the specific guideline files referenced — the index is a pointer, not the goal.
@@ -56,12 +56,12 @@ Run the project's lint, type-check, and test commands. Fix any failures before p
 - [ ] `verify.md` contains exactly one token: `Learning decision: update-spec` | `no-update` | `unsure`
 - [ ] If `update-spec` or `unsure`: `research/learning-proposal.md` exists (or documented `N/A` with reason) and matches the decision
 - [ ] If `no-update`: includes `no durable learning` (or guide-equivalent) plus brief rationale
-- [ ] If `update-spec`: spec was written only after confirmation; `Spec update evidence:` points at `.trellis/spec/...`
-- [ ] No silent edits to `.trellis/spec/` without confirmation
+- [ ] If `update-spec`: spec was written only after confirmation; `Spec update evidence:` points at `.cstl/spec/...`
+- [ ] No silent edits to `.cstl/spec/` without confirmation
 
 ### Spec Sync
 
-- [ ] Does `.trellis/spec/` need updates? (route through semi-automatic flow: proposal → confirm → `cstl-update-spec`)
+- [ ] Does `.cstl/spec/` need updates? (route through semi-automatic flow: proposal → confirm → `cstl-update-spec`)
 
 > "If I fixed a bug or discovered something non-obvious, should I document it so future me won't hit the same issue?" → If YES, update the relevant spec doc.
 

package/dist/templates/common/skills/update-spec.md

@@ -9,9 +9,9 @@ When you learn something valuable (from debugging, implementing, or discussion),
 ## Semi-automatic flow (required for durable learning)
 
 1. **Detect** — did this task produce reusable code-spec or guide-worthy learning?
-2. **Proposal** — write `{TASK}/research/learning-proposal.md` (target spec paths, draft bullets; **do not** edit `.trellis/spec/` yet).
+2. **Proposal** — write `{TASK}/research/learning-proposal.md` (target spec paths, draft bullets; **do not** edit `.cstl/spec/` yet).
 3. **Confirm** — user or task owner explicitly approves (`Learning decision: update-spec` in `verify.md`).
-4. **Write** — only then edit spec files; add `Spec update evidence: .trellis/spec/...` to `verify.md`.
+4. **Write** — only then edit spec files; add `Spec update evidence: .cstl/spec/...` to `verify.md`.
 
 **Forbidden:** silent spec edits; writing spec when `Learning decision: no-update` or `unsure` without follow-up; auto-updating spec from hooks or check alone.
 
@@ -68,7 +68,7 @@ For triggered tasks, include all sections below:
 ## Spec Structure Overview
 
 ```
-.trellis/spec/
+.cstl/spec/
 ├── <layer>/           # Per-layer coding standards (e.g., backend/, frontend/, api/)
 │   ├── index.md       # Overview and links
 │   └── *.md           # Topic-specific guidelines
@@ -130,7 +130,7 @@ Before editing, read the current code-spec to:
 - Find the right section for your update
 
 ```bash
-cat .trellis/spec/<category>/<file>.md
+cat .cstl/spec/<category>/<file>.md
 ```
 
 ### Step 4: Make the Update

package/dist/templates/cursor/agents/cstl-check.md

@@ -7,7 +7,7 @@ tools: Read, Write, Edit, Bash, Glob, Grep, mcp__exa__web_search_exa, mcp__exa__
 ## Entry points
 
 - **Agent session:** Open this agent file manually in a new chat — context from this file + your main-session prompt.
-- **Task dispatch:** Run `python ./.trellis/scripts/generate_dispatch_prompt.py --agent check` → pass stdout as `Task(..., prompt=...)` — context from the Layer 2 prompt.
+- **Task dispatch:** Run `python ./.cstl/scripts/generate_dispatch_prompt.py --agent check` → pass stdout as `Task(..., prompt=...)` — context from the Layer 2 prompt.
 
 ## Context source
 
@@ -21,7 +21,7 @@ You are the Check Agent in the Trellis workflow.
 ## Model policy
 
 - **Default:** no `model:` → **inherit** parent session.
-- **Per dispatch:** main session asks user → one-shot `model:` overlay → `Task` → restore (architecture review uses the same flow). See `.trellis/spec/guides/cursor-subagent-policy.md`.
+- **Per dispatch:** main session asks user → one-shot `model:` overlay → `Task` → restore (architecture review uses the same flow). See `.cstl/spec/guides/cursor-subagent-policy.md`.
 
 ## Recursion Guard
 
@@ -47,7 +47,7 @@ Look for the `<!-- cstl-hook-injected -->` marker in your input above.
 ## Context
 
 Before checking, read:
-- `.trellis/spec/` - Development guidelines
+- `.cstl/spec/` - Development guidelines
 - Task `prd.md` - Requirements document
 - Task `design.md` - Technical design (if exists)
 - Task `implement.md` - Execution plan (if exists)
@@ -65,7 +65,7 @@ Before checking, read:
 
 - Reviewer id: `cursor`.
 - When `implement.md` quality_gates requires a reviewer gate for the current transition, write human-readable evidence in `verify.md` before recording the machine-checkable gate result. Parent/Child integration evidence may also belong in Parent `task-map.md`.
-- Record non-baseline gates with `python ./.trellis/scripts/task.py record-gate <task> --transition <transition> --gate <gate> --result PASS --reviewer cursor --evidence verify.md`.
+- Record non-baseline gates with `python ./.cstl/scripts/task.py record-gate <task> --transition <transition> --gate <gate> --result PASS --reviewer cursor --evidence verify.md`.
 - For FAIL, add `--root-cause implementation-defect|contract-changing-defect|validation-environment-blocker` and `--issue-fingerprint <short-stable-id>`. Route implementation defects back to Execution, contract-changing defects to Planning, and validation blockers to Verification / Review.
 - For SKIPPED, use only explicit user approval: `--skip-approved-by user --skip-reason <reason>`.
 - Never record `baseline-check`; the CLI owns it. Do not pass review bodies, logs, screenshots, or long issue lists through `record-gate` arguments.
@@ -89,7 +89,7 @@ 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 `.trellis/spec/` to check code:
+Read the task's prd.md, design.md if present, and implement.md if present, then read relevant specs in `.cstl/spec/` to check code:
 
 - Does it satisfy the task requirements
 - Does it follow the technical design and implementation plan when present
@@ -124,7 +124,7 @@ When the pack exists:
 
 ```bash
 # Optional: confirm path from selected task
-python ./.trellis/scripts/task.py selected --source
+python ./.cstl/scripts/task.py selected --source
 ```
 
 Read `{TASK}/research/retrieval-pack-latest.json` and use `contextPack.selected` (top items: `title`, `source`, `reference`, `score`). Add or update `verify.md` with:

package/dist/templates/cursor/agents/cstl-implement.md

@@ -7,7 +7,7 @@ tools: Read, Write, Edit, Bash, Glob, Grep, mcp__exa__web_search_exa, mcp__exa__
 ## Entry points
 
 - **Agent session:** Open this agent file manually in a new chat — context from this file + your main-session prompt.
-- **Task dispatch:** Run `python ./.trellis/scripts/generate_dispatch_prompt.py --agent implement` → pass stdout as `Task(..., prompt=...)` — context from the Layer 2 prompt.
+- **Task dispatch:** Run `python ./.cstl/scripts/generate_dispatch_prompt.py --agent implement` → pass stdout as `Task(..., prompt=...)` — context from the Layer 2 prompt.
 
 ## Context source
 
@@ -21,7 +21,7 @@ You are the Implement Agent in the Trellis workflow.
 ## Model policy
 
 - **Default:** no `model:` → **inherit** parent session.
-- **Per dispatch / Child worker:** main session asks user → one-shot `model:` overlay on this file → `Task` → restore. Child session uses the same overlay pattern on `cstl-implement`. See `.trellis/spec/guides/cursor-subagent-policy.md`.
+- **Per dispatch / Child worker:** main session asks user → one-shot `model:` overlay on this file → `Task` → restore. Child session uses the same overlay pattern on `cstl-implement`. See `.cstl/spec/guides/cursor-subagent-policy.md`.
 
 ## Recursion Guard
 
@@ -46,15 +46,15 @@ Look for the `<!-- cstl-hook-injected -->` marker in your input above.
 ## Context
 
 Before implementing, read:
-- `.trellis/workflow.md` - Project workflow
-- `.trellis/spec/` - Development guidelines
+- `.cstl/workflow.md` - Project workflow
+- `.cstl/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 `.trellis/spec/`
+1. **Understand specs** - Read relevant spec files in `.cstl/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
@@ -76,8 +76,8 @@ Before implementing, read:
 
 Read relevant specs based on task type:
 
-- Spec layers: `.trellis/spec/<package>/<layer>/`
-- Shared guides: `.trellis/spec/guides/`
+- Spec layers: `.cstl/spec/<package>/<layer>/`
+- Shared guides: `.cstl/spec/guides/`
 
 ### 2. Understand Requirements
 

package/dist/templates/cursor/agents/cstl-research.md

@@ -7,7 +7,7 @@ tools: Read, Write, Glob, Grep, Bash, WebSearch, WebFetch, mcp__exa__web_search_
 ## Entry points
 
 - **Agent session:** Open this agent file manually in a new chat — context from this file + your main-session prompt.
-- **Task dispatch:** Run `python ./.trellis/scripts/generate_dispatch_prompt.py --agent research` → pass stdout as `Task(..., prompt=...)` — context from the Layer 2 prompt.
+- **Task dispatch:** Run `python ./.cstl/scripts/generate_dispatch_prompt.py --agent research` → pass stdout as `Task(..., prompt=...)` — context from the Layer 2 prompt.
 
 ## Context source
 
@@ -21,7 +21,7 @@ You are the Research Agent in the Trellis workflow.
 ## Model policy
 
 - **Default:** no `model:` in this file → **inherit** parent session at spawn.
-- **Per dispatch:** main session asks the user, writes a **one-shot** `model:` here, runs `Task`, then **removes** `model:` (ephemeral overlay). See `.trellis/spec/guides/cursor-subagent-policy.md`.
+- **Per dispatch:** main session asks the user, writes a **one-shot** `model:` here, runs `Task`, then **removes** `model:` (ephemeral overlay). See `.cstl/spec/guides/cursor-subagent-policy.md`.
 - Dispatch: Cursor **Agent mode** (writable).
 
 ## Core Principle
@@ -50,7 +50,7 @@ Conversations get compacted; files don't. Every research output MUST end up as a
 
 ### Step 1: Resolve Selected Task
 
-Run `python ./.trellis/scripts/task.py selected --source` → selected task path. If no task is selected, ask the user where to write output; do NOT guess.
+Run `python ./.cstl/scripts/task.py selected --source` → selected task path. If no task is selected, ask the user where to write output; do NOT guess.
 
 Ensure `{TASK_DIR}/research/` exists:
 
@@ -68,9 +68,9 @@ Run independent searches in parallel (Glob + Grep + smart-search CLI for externa
 
 #### External search — provider relevance caveats
 
-- **Context7** and generic third-party library docs are often **irrelevant** to Trellis/Cursor platform questions. Prefer **Cursor / Cursor++ official documentation**, `docs.cursor.com`, and **local `.trellis/spec/`** before trusting Context7 hits.
+- **Context7** and generic third-party library docs are often **irrelevant** to Trellis/Cursor platform questions. Prefer **Cursor / Cursor++ official documentation**, `docs.cursor.com`, and **local `.cstl/spec/`** before trusting Context7 hits.
 - Every smart-search result you persist must **label the provider source** (e.g. `exa`, `context7`, `cursor-docs`, `tavily`) in the research file — in frontmatter or per bullet — so downstream check/finish can audit provenance.
-- Trellis harness facts: `./.trellis/scripts/run_smart_search.py` writes manifests under `{TASK}/research/smart-search/<run-id>/`; scored pack output (when built) is `{TASK}/research/retrieval-pack-latest.json`.
+- Trellis harness facts: `./.cstl/scripts/run_smart_search.py` writes manifests under `{TASK}/research/smart-search/<run-id>/`; scored pack output (when built) is `{TASK}/research/retrieval-pack-latest.json`.
 
 #### External search — manual query refinement
 
@@ -80,7 +80,7 @@ When the first smart-search pass returns irrelevant results, **refine before fal
 2. Add product scope: `+Trellis`, `+cursor-trellis`, or the exact API/hook name
 3. Switch route: `--intent official-source --include-domain cursor.com` or `--intent docs` for API reference
 4. Narrow time or topic: shorter query, version number, or feature name from local spec
-5. Re-run: `python ./.trellis/scripts/run_smart_search.py "<refined query>" --intent deep-research --json`
+5. Re-run: `python ./.cstl/scripts/run_smart_search.py "<refined query>" --intent deep-research --json`
 
 Only use Cursor WebSearch/WebFetch when smart-search is unavailable (`not_configured` / `failed` / timeout) — then persist with `source: cursor-web-fallback`.
 
@@ -110,8 +110,8 @@ Do NOT paste full research content into the reply. The files are the contract.
 ### Write FORBIDDEN
 
 - Code files (`src/`, `lib/`, …)
-- Spec files (`.trellis/spec/`) — main agent should use `update-spec` skill instead
-- `.trellis/scripts/`, `.trellis/workflow.md`, platform config (`.claude/`, `.cursor/`, etc.)
+- Spec files (`.cstl/spec/`) — main agent should use `update-spec` skill instead
+- `.cstl/scripts/`, `.cstl/workflow.md`, platform config (`.claude/`, `.cursor/`, etc.)
 - Other task directories
 - Any git operation (commit / push / branch / merge)
 
@@ -149,7 +149,7 @@ Each `{TASK_DIR}/research/<topic>.md` should follow:
 
 ### Related Specs
 
-- `.trellis/spec/xxx.md` — <description>
+- `.cstl/spec/xxx.md` — <description>
 
 ## Caveats / Not Found
 

package/dist/templates/cursor/commands/cursor2plus-setup.md

@@ -10,15 +10,15 @@ Native Cursor API (no Cursor++): stop — this does not apply; agent frontmatter
 
 Confirm the Cursor++ data directory exists:
 
-- `~/.ccursor/providers.json` (or a custom path in `.trellis/local/cursor2plus/config.local.json`)
+- `~/.ccursor/providers.json` (or a custom path in `.cstl/local/cursor2plus/config.local.json`)
 
 If missing, Cursor++ is not set up — ask the user to install/configure it first.
 
 ## Step 2: List available models + roles
 
 ```bash
-python ./.trellis/local/cursor2plus/patch_wpelc8.py --list-models
-python ./.trellis/local/cursor2plus/patch_wpelc8.py --explain
+python ./.cstl/local/cursor2plus/patch_wpelc8.py --list-models
+python ./.cstl/local/cursor2plus/patch_wpelc8.py --explain
 ```
 
 `--list-models` shows the model catalog (apiModel / displayName / slug / provider) from `providers.json`.
@@ -35,7 +35,7 @@ The user may skip types they don't use — omit those from the map.
 
 ## Step 4: Write the routing map
 
-Write `~/.ccursor/trellis-task-models.json5` (or `~/.ccursor/` on Unix) using the structure from `.trellis/local/trellis-task-models.json5.example`:
+Write `~/.ccursor/trellis-task-models.json5` (or `~/.ccursor/` on Unix) using the structure from `.cstl/local/trellis-task-models.json5.example`:
 
 ```json5
 // Trellis + Cursor++ BYOK — per-subagent-type model routing
@@ -49,13 +49,13 @@ Write `~/.ccursor/trellis-task-models.json5` (or `~/.ccursor/` on Unix) using th
 }
 ```
 
-Project-level override (optional, wins on same key): `.trellis/local/subagent-models.json5`.
+Project-level override (optional, wins on same key): `.cstl/local/subagent-models.json5`.
 
 ## Step 5: Apply the patch + verify
 
 ```bash
-python ./.trellis/local/cursor2plus/patch_wpelc8.py --print-map
-python ./.trellis/local/cursor2plus/patch_wpelc8.py
+python ./.cstl/local/cursor2plus/patch_wpelc8.py --print-map
+python ./.cstl/local/cursor2plus/patch_wpelc8.py
 ```
 
 Then tell the user: **Developer: Reload Window** in Cursor (required once per patch for the resolver change to take effect).
@@ -76,7 +76,7 @@ Then tell the user: **Developer: Reload Window** in Cursor (required once per pa
 
 - User catalog: `~/.ccursor/providers.json`
 - User routing doc: `~/.ccursor/trellis-task-models.json5` (machine-local, gitignored)
-- Project override (optional): `.trellis/local/subagent-models.json5`
-- Patch bundle: `.trellis/local/cursor2plus/`
+- Project override (optional): `.cstl/local/subagent-models.json5`
+- Patch bundle: `.cstl/local/cursor2plus/`
 
-Policy: `.trellis/spec/guides/cursor-subagent-policy.md` (Method 2.5 / 2.6).
+Policy: `.cstl/spec/guides/cursor-subagent-policy.md` (Method 2.5 / 2.6).

package/dist/templates/cursor/rules/cstl-subagent-dispatch.mdc

@@ -14,7 +14,7 @@ Before calling `Task(subagent_type="cstl-research|cstl-implement|cstl-check", ..
 1. Generate a complete dispatch prompt via CLI:
 
    ```powershell
-   python ./.trellis/scripts/generate_dispatch_prompt.py --agent <research|implement|check> --task "<task-path>" --repo-root "<repo-root>"
+   python ./.cstl/scripts/generate_dispatch_prompt.py --agent <research|implement|check> --task "<task-path>" --repo-root "<repo-root>"
    ```
 
 2. Use the CLI output as the `prompt` parameter value for `Task(...)`.
@@ -27,7 +27,7 @@ The generated prompt carries role identity ("You are the Trellis Research/Implem
 
 ## Auto-detection
 
-If `--task` is omitted, the script resolves the currently selected task. If `--repo-root` is omitted, it auto-detects via `.trellis` or `.git` upward search.
+If `--task` is omitted, the script resolves the currently selected task. If `--repo-root` is omitted, it auto-detects via `.cstl` or `.git` upward search.
 
 ## Exception
 

package/dist/templates/cursor/rules/cstl-triage.mdc

@@ -33,6 +33,6 @@ If the user declines a task for a simple request, skip Trellis for this session.
 
 ## Why this rule exists
 
-Cursor's `sessionStart` hook has a confirmed bug (#158452): `additional_context` is never injected into the agent's system context. The Triage rules in `.trellis/workflow.md` therefore never reach you via that channel. This `.cursor/rules` file is the reliable workaround — Cursor prepends rules to your context before every prompt, independent of the broken sessionStart path.
+Cursor's `sessionStart` hook has a confirmed bug (#158452): `additional_context` is never injected into the agent's system context. The Triage rules in `.cstl/workflow.md` therefore never reach you via that channel. This `.cursor/rules` file is the reliable workaround — Cursor prepends rules to your context before every prompt, independent of the broken sessionStart path.
 
-Full decision-tree details, trigger-signal keywords, and the Task Ladder table: see `.trellis/workflow.md` → `### Request Triage`.
+Full decision-tree details, trigger-signal keywords, and the Task Ladder table: see `.cstl/workflow.md` → `### Request Triage`.

package/dist/templates/cursor/rules/retrieval-routing.mdc

@@ -18,13 +18,13 @@ If the user message or Trellis context contains a block starting with `## 代码
 Generate a fresh plan when needed:
 
 ```powershell
-python ./.trellis/scripts/route_codebase_retrieval.py "<question>" --instructions
+python ./.cstl/scripts/route_codebase_retrieval.py "<question>" --instructions
 ```
 
 JSON (includes `agentInstructions`):
 
 ```powershell
-python ./.trellis/scripts/route_codebase_retrieval.py "<question>" --json
+python ./.cstl/scripts/route_codebase_retrieval.py "<question>" --json
 ```
 
 ## Default tool order (no plan block)
@@ -36,7 +36,7 @@ python ./.trellis/scripts/route_codebase_retrieval.py "<question>" --json
 | Same name across packages (trap) | **codegraph_search** / **codegraph_explore** → Grep |
 | Extension symbols | **codegraph_search** under `extensions/` |
 | Conceptual / how does X work | **Native:** built-in `@codebase` / semantic search. **BYOK:** **fast_context_search** (fast-context MCP). Plans show `cursorEnv`. |
-| Policy / architecture / boundaries / storage rules | **Grep** on `AGENTS.md`, `**/AGENTS.md`, `.trellis/spec/**`, `README.md` (router `policy-docs-rg`) before implementation modules |
+| Policy / architecture / boundaries / storage rules | **Grep** on `AGENTS.md`, `**/AGENTS.md`, `.cstl/spec/**`, `README.md` (router `policy-docs-rg`) before implementation modules |
 | Definition jump | **codegraph_node** / **codegraph_search**, then **Read** (Agent does not expose GO_TO_DEFINITION / LSP) |
 | Wide cross-cutting explore | **Native:** DEEP_SEARCH or Explore subagent. **BYOK:** **Task explore** subagent, then Grep/codegraph/Read |
 
@@ -56,4 +56,4 @@ Use codegraph for **call chains**, **cross-package trap disambiguation**, **exte
 
 ## External facts
 
-Web/current events: **smart-search** first per `.trellis/spec/guides/retrieval-daily-guide.md`.
+Web/current events: **smart-search** first per `.cstl/spec/guides/retrieval-daily-guide.md`.

package/dist/templates/extract.d.ts

@@ -1,6 +1,6 @@
 type TemplateCategory = "scripts" | "markdown" | "commands";
 /**
- * Get the path to the trellis templates directory (.trellis/ scaffolding).
+ * Get the path to the trellis templates directory (.cstl/ scaffolding).
  */
 export declare function getTrellisTemplatePath(): string;
 /** @deprecated Use getTrellisTemplatePath() instead. */

package/dist/templates/extract.js

@@ -6,7 +6,7 @@ import { replacePythonCommandLiterals } from "../configurators/shared.js";
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = path.dirname(__filename);
 /**
- * Get the path to the trellis templates directory (.trellis/ scaffolding).
+ * Get the path to the trellis templates directory (.cstl/ scaffolding).
  */
 export function getTrellisTemplatePath() {
     const templatePath = path.join(__dirname, "trellis");

package/dist/templates/markdown/agents.md

@@ -1,16 +1,16 @@
-<!-- TRELLIS:START -->
-# Trellis Instructions
+<!-- CSTL:START -->
+# Cursor-Trellis (cstl) Instructions
 
 These instructions are for AI assistants working in this project.
 
-This project is managed by Trellis. The working knowledge you need lives under `.trellis/`:
+This project is managed by cursor-trellis. The working knowledge you need lives under `.cstl/`:
 
-- `.trellis/workflow.md` — development phases, when to create tasks, skill routing
-- `.trellis/spec/` — package- and layer-scoped coding guidelines (read before writing code in a given layer)
-- `.trellis/workspace/` — per-developer journals and session traces
-- `.trellis/tasks/` — active and archived tasks (PRDs, research, jsonl context)
+- `.cstl/workflow.md` — development phases, when to create tasks, skill routing
+- `.cstl/spec/` — package- and layer-scoped coding guidelines (read before writing code in a given layer)
+- `.cstl/workspace/` — per-developer journals and session traces
+- `.cstl/tasks/` — active and archived tasks (PRDs, research, jsonl context)
 
-If a Trellis command is available on Cursor (e.g. `cstl-finish-work`, `cstl-continue`), prefer it over manual steps.
+If a cstl command is available on Cursor (e.g. `cstl-finish-work`, `cstl-continue`), prefer it over manual steps.
 
 ## Command surface (what is user-invocable vs internal)
 
@@ -21,8 +21,8 @@ Only a handful of Trellis entry points are meant for **manual `/` invocation**.
 
 ## Web research routing (smart-search first)
 
-For **any external / current / web fact**, run **`python ./.trellis/scripts/run_smart_search.py "<question>" --intent deep-research --json`** first. That script is the **only** Trellis web-research evidence entrypoint (it shells out to the `smart-search` CLI). Do not guess paths under package source trees or sibling repos. Platform built-in web tools (Cursor `WebSearch` / `WebFetch`, or native web tools elsewhere) are **downgrade-only fallbacks**, used solely when smart-search is unavailable (`doctor` not ok, status `not_configured` / `failed`, or search timeout). Do not reach for built-in web search while smart-search is healthy. On Cursor, `smart-search-cli` is an **internal workflow skill name** only (not shipped under `.cursor/skills/`); follow `.trellis/spec/guides/retrieval-daily-guide.md` and `.cursor/rules/retrieval-routing.mdc` for the executable contract.
+For **any external / current / web fact**, run **`python ./.cstl/scripts/run_smart_search.py "<question>" --intent deep-research --json`** first. That script is the **only** Trellis web-research evidence entrypoint (it shells out to the `smart-search` CLI). Do not guess paths under package source trees or sibling repos. Platform built-in web tools (Cursor `WebSearch` / `WebFetch`, or native web tools elsewhere) are **downgrade-only fallbacks**, used solely when smart-search is unavailable (`doctor` not ok, status `not_configured` / `failed`, or search timeout). Do not reach for built-in web search while smart-search is healthy. On Cursor, `smart-search-cli` is an **internal workflow skill name** only (not shipped under `.cursor/skills/`); follow `.cstl/spec/guides/retrieval-daily-guide.md` and `.cursor/rules/retrieval-routing.mdc` for the executable contract.
 
-Managed by Trellis. Edits outside this block are preserved; edits inside may be overwritten by a future `cstl update`.
+Managed by cursor-trellis. Edits outside this block are preserved; edits inside may be overwritten by a future `cstl update`.
 
-<!-- TRELLIS:END -->
+<!-- CSTL:END -->

package/dist/templates/markdown/prompts/run-semantic-slice-12.md.txt

@@ -7,7 +7,7 @@
 For each query in `queries-semantic-slice.jsonl`:
 
 ```powershell
-python .trellis/scripts/route_codebase_retrieval.py "<question>" --json
+python .cstl/scripts/route_codebase_retrieval.py "<question>" --json
 ```
 
 Record `semantic_in_plan` / route list from the envelope.

package/dist/templates/markdown/spec/guides/cross-platform-thinking-guide.md.txt

@@ -40,7 +40,7 @@ print("Run: script.py <args>")
 
 # GOOD - Platform-aware wording
 print("Usage: python on Windows, python3 elsewhere")
-print("Run: {{PYTHON_CMD}} ./.trellis/scripts/task.py <args>")
+print("Run: {{PYTHON_CMD}} ./.cstl/scripts/task.py <args>")
 ```
 
 **Rule 2**: When generating config files at init time, use placeholder + platform detection:
@@ -356,7 +356,7 @@ When making platform-related changes, check **all these locations**:
 
 ### Code Locations
 - [ ] `src/templates/` - Template files for new projects
-- [ ] `.trellis/scripts/` - Project's own scripts (if self-hosting)
+- [ ] `.cstl/scripts/` - Project's own scripts (if self-hosting)
 - [ ] `dist/` - Built output (rebuild after changes)
 
 ### Search Pattern
@@ -530,7 +530,7 @@ subprocess.run(["./script.py"])  # FileNotFoundError
 
 ```
 src/templates/script.py  ← Updated
-.trellis/scripts/script.py  ← Forgot to sync!
+.cstl/scripts/script.py  ← Forgot to sync!
 ```
 
 ### 4. "Python 3 is always python3"
@@ -606,7 +606,7 @@ included with Trellis, verify the whole distribution path:
 - [ ] `pnpm build` copies the asset into `dist/templates/**`.
 - [ ] `npm pack --dry-run --json` includes the expected `dist/**` path.
 - [ ] The built binary installs the asset in a fresh temp repository.
-- [ ] `.trellis/.template-hashes.json` tracks the generated asset path.
+- [ ] `.cstl/.template-hashes.json` tracks the generated asset path.
 - [ ] `cstl update --dry-run` reports `Already up to date!` in that temp
   repository.
 
@@ -628,7 +628,7 @@ git -C "$tmpdir" init -q
   cd "$tmpdir"
   node /path/to/Trellis/packages/cli/bin/trellis.js init -u smoke --yes --cursor
   test -f .cursor/skills/<skill>/SKILL.md
-  grep -q '<skill>' .trellis/.template-hashes.json
+  grep -q '<skill>' .cstl/.template-hashes.json
   node /path/to/Trellis/packages/cli/bin/trellis.js update --dry-run
 )
 ```

package/dist/templates/markdown/spec/guides/cursor-context-injection-guide.md.txt

@@ -14,7 +14,7 @@ Cursor has **four** channels that can put text in front of the model. They are *
 | `beforeSubmitPrompt` hook → `additional_context` | Per user message; router emits `## 代码库检索计划` | ⚠️ **Verify on your Cursor build** (docs list field; forum reports vary) | `inject-retrieval-plan.py` + `retrieval-routing.mdc` enforcement |
 | `AGENTS.md` (repo root + nested) | Read automatically, treated as an always-on rule | ✅ **Yes** | smart-search-first rule, command surface, remote policy (the `<!-- TRELLIS:START -->` block) |
 | `sessionStart` hook → `additional_context` | Hook fires, JSON parsed... **but content never reaches the model's system context** | ❌ **No (confirmed bug)** | workflow.md Phase Index + Task Dashboard + first-reply notice |
-| `.trellis/workflow.md` (read on demand) | Only if the agent explicitly runs `get_context.py` or reads the file | ⚠️ Depends on agent taking action | Full Request Triage section, Task Ladder, workflow-state breadcrumbs |
+| `.cstl/workflow.md` (read on demand) | Only if the agent explicitly runs `get_context.py` or reads the file | ⚠️ Depends on agent taking action | Full Request Triage section, Task Ladder, workflow-state breadcrumbs |
 | **`task.py generate-dispatch-prompt` → Task `prompt`** (CLI Layer 2) | Main session runs Trellis script before `Task(...)` | ✅ **Yes (primary for subagent task context on Cursor)** | Full embed: marker, `Selected task:`, prd/jsonl/spec bodies |
 
 **Key takeaway**: anything that must reach the model **every turn without the agent choosing to load it** must live in `.cursor/rules` or `AGENTS.md`. Subagent task context on Cursor uses **CLI Layer 2** before Task dispatch; `preToolUse` hook injection is best-effort only (see forum reports + 2026-06-22 spike). Anything in `workflow.md` that depends on `sessionStart` injection is **invisible to Cursor agents** until the bug is fixed.
@@ -45,7 +45,7 @@ Because of the bug, Trellis routes content by reliability on Cursor:
 | **Request Triage hard gate** (classify every turn, emit `[Triage: <Mode>]`) | `.cursor/rules/cstl-triage.mdc` (`alwaysApply: true`) | Must be visible every turn; sessionStart path is broken |
 | **smart-search-first web routing** | `AGENTS.md` (TRELLIS:START block) | AGENTS.md is a reliable always-on channel |
 | **Command surface** (what's user-invocable vs internal skill) | `AGENTS.md` (TRELLIS:START block) | Same |
-| **Workflow phases, Task Ladder, workflow-state breadcrumbs** | `.trellis/workflow.md` | Loaded on demand via `get_context.py` / `cstl-start` / `cstl-continue`; NOT auto-injected on Cursor |
+| **Workflow phases, Task Ladder, workflow-state breadcrumbs** | `.cstl/workflow.md` | Loaded on demand via `get_context.py` / `cstl-start` / `cstl-continue`; NOT auto-injected on Cursor |
 
 **If a new "must-always-be-visible" rule is added to Trellis**: ship it as a `.cursor/rules/*.mdc` (Cursor) — do **not** rely on adding it to `workflow.md` and expecting sessionStart to deliver it.
 
@@ -62,6 +62,6 @@ Because of the bug, Trellis routes content by reliability on Cursor:
 ## Related
 
 - `cursor-subagent-policy.md` — Task tool scenes, model routing (this guide is about **context injection**, that one is about **subagent dispatch**).
-- `.trellis/workflow.md` → `### Request Triage` — the full Triage decision tree (the rule in `.cursor/rules/cstl-triage.mdc` is the slim always-apply version pointing here).
+- `.cstl/workflow.md` → `### Request Triage` — the full Triage decision tree (the rule in `.cursor/rules/cstl-triage.mdc` is the slim always-apply version pointing here).
 - Task `06-19-cursor-rules-triage` (archive) — the investigation that produced this guide.
 - Cursor forum thread: https://forum.cursor.com/t/sessionstart-hook-additional-context-is-never-injected-into-agents-initial-system-context/158452