@blxzer/cursor-trellis 0.2.9 → 0.3.2

package/dist/templates/common/bundled-skills/{trellis-spec-bootstrap → cstl-spec-bootstrap}/references/repository-analysis.md

@@ -4,7 +4,7 @@ The goal is to discover the project's real architecture before writing rules. Do
 
 ## Analysis Order
 
-1. Read the existing `.trellis/spec/` tree and note which files are templates, outdated, or already project-specific.
+1. Read the existing `.cstl/spec/` tree and note which files are templates, outdated, or already project-specific.
 2. Inspect package manifests, build scripts, workspace config, and top-level documentation to identify packages and runtime layers.
 3. Use GitNexus for execution flows, module clusters, dependency hubs, and impact-sensitive areas.
 4. Use ABCoder or language-native tooling for exact signatures, types, class boundaries, and implementation examples.

package/dist/templates/common/bundled-skills/{trellis-spec-bootstrap → cstl-spec-bootstrap}/references/spec-task-planning.md

@@ -20,7 +20,7 @@ When a Trellis task is useful, write a concise PRD with these sections:
 # Fill <package-or-layer> Trellis Specs
 
 ## Goal
-Write project-specific `.trellis/spec/` guidance for <scope>.
+Write project-specific `.cstl/spec/` guidance for <scope>.
 
 ## Scope
 - Spec directory:
@@ -32,8 +32,8 @@ Write project-specific `.trellis/spec/` guidance for <scope>.
 Summarize the concrete findings from repository analysis.
 
 ## Files To Create Or Update
-- `.trellis/spec/.../index.md`
-- `.trellis/spec/.../<topic>.md`
+- `.cstl/spec/.../index.md`
+- `.cstl/spec/.../<topic>.md`
 
 ## Rules
 - Adapt the spec file set to the real codebase.

package/dist/templates/common/bundled-skills/{trellis-spec-bootstrap → cstl-spec-bootstrap}/references/spec-writing.md

@@ -64,7 +64,7 @@ Avoid passing raw `process.argv` or unvalidated config objects into shared helpe
 Before finishing:
 
 ```bash
-grep -R "To be filled\\|TODO: fill\\|placeholder" .trellis/spec
+grep -R "To be filled\\|TODO: fill\\|placeholder" .cstl/spec
 ```
 
 Also check links, index files, and whether any spec still describes a template rather than this repository.

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

@@ -1,46 +1,46 @@
-# Continue Selected Task
-
-Resume work only when this live session already has a `selected_task`. If no task is selected, show the Task Dashboard and ask for an explicit route.
+# Continue Selected Task
+
+Resume work only when this live session already has a `selected_task`. If no task is selected, show the Task Dashboard and ask for an explicit route.
 
 ---
 
-## Step 1: Load Framework Context
-
-```bash
-{{PYTHON_CMD}} ./.trellis/scripts/get_context.py
-```
-
-Confirms: selected task, Task Dashboard, git state, recent commits.
-
-If the output says `Selected task: none`, do not auto-resume a previous or unique task. Show the dashboard and ask the user to choose one route:
-
-- select a task with `{{PYTHON_CMD}} ./.trellis/scripts/task.py select <task>`
-- create a task
-- inspect details
-- continue without a task for No Task / Micro-Grill work
+## Step 1: Load Framework Context
+
+```bash
+{{PYTHON_CMD}} ./.cstl/scripts/get_context.py
+```
+
+Confirms: selected task, Task Dashboard, git state, recent commits.
+
+If the output says `Selected task: none`, do not auto-resume a previous or unique task. Show the dashboard and ask the user to choose one route:
+
+- select a task with `{{PYTHON_CMD}} ./.cstl/scripts/task.py select <task>`
+- create a task
+- inspect details
+- continue without a task for No Task / Micro-Grill work
 
 ## Step 2: Load the Phase Index
 
 ```bash
-{{PYTHON_CMD}} ./.trellis/scripts/get_context.py --mode phase
+{{PYTHON_CMD}} ./.cstl/scripts/get_context.py --mode phase
 ```
 
 Shows the Phase Index (Plan / Execute / Finish) with routing + skill mapping.
 
 ## Step 3: Decide Where You Are
 
-When a task is selected, `get_context.py` shows the selected task's `status` field. Route by `status` + artifact presence. This command replaces the user needing to remember the Trellis flow; it does not itself approve implementation.
+When a task is selected, `get_context.py` shows the selected task's `status` field. Route by `status` + artifact presence. This command replaces the user needing to remember the Trellis flow; it does not itself approve implementation.
 
-- `status=planning` + no `prd.md` → **1.1** (load `trellis-brainstorm`)
+- `status=planning` + no `prd.md` → **1.1** (load `cstl-brainstorm`)
 - `status=planning` + `prd.md` only → decide whether the task is lightweight or complex. Lightweight can move to **1.4** review; complex returns to **1.1** to add `design.md` + `implement.md`.
 - `status=planning` + complex artifacts complete + sub-agent jsonl not curated (only the seed `_example` row) → **1.3**
-- `status=planning` + required artifacts complete + required jsonl curated or inline mode → execution gate (run `task.py start-execution <task> --check`, report PASS, ask for explicit execution approval, then run `task.py start-execution <task> --approved`)
+- `status=planning` + required artifacts complete + required jsonl curated or inline mode → execution gate (run `task.py start-execution <task> --check`, report PASS, ask for explicit execution approval, then run `task.py start-execution <task> --approved`)
 - `status=in_progress` + implementation not started → **2.1**
 - `status=in_progress` + implementation done, not yet checked → **2.2**
 - `status=in_progress` + check passed → **3.1**
 - `status=completed` (rare; usually archived immediately) → archive flow
 
-Phase rules (full detail in `.trellis/workflow.md`):
+Phase rules (full detail in `.cstl/workflow.md`):
 
 1. Run steps **in order** within a phase — `[required]` steps must not be skipped
 2. `[once]` steps are already done if the required output exists. `prd.md` alone can be enough only for lightweight tasks; complex tasks also need `design.md` and `implement.md`.
@@ -51,7 +51,7 @@ Phase rules (full detail in `.trellis/workflow.md`):
 Once you know which step to resume at:
 
 ```bash
-{{PYTHON_CMD}} ./.trellis/scripts/get_context.py --mode phase --step <X.X> --platform {{CLI_FLAG}}
+{{PYTHON_CMD}} ./.cstl/scripts/get_context.py --mode phase --step <X.X> --platform {{CLI_FLAG}}
 ```
 
 Follow the loaded instructions. After each `[required]` step completes, move to the next.
@@ -60,4 +60,4 @@ Follow the loaded instructions. After each `[required]` step completes, move to
 
 ## Reference
 
-Full workflow and detailed phase steps live in `.trellis/workflow.md`. This command is only an entry point — the canonical guidance is there.
+Full workflow and detailed phase steps live in `.cstl/workflow.md`. This command is only an entry point — the canonical guidance is there.

package/dist/templates/common/commands/finish-work.md

@@ -2,7 +2,7 @@
 
 Wrap up the current session: archive the selected task (and any other completed-but-unarchived tasks the user wants to clean up) and record the session journal. Code commits are NOT done here — those happen in workflow Phase 3.4 before you invoke this command.
 
-Before archive, confirm `verify.md` includes Phase 3.3 **Learning decision** (`update-spec` | `no-update` | `unsure`) and gate-compatible evidence per `.trellis/spec/guides/durable-learning-decision-guide.md`. Run `task.py archive <task> --check` when unsure.
+Before archive, confirm `verify.md` includes Phase 3.3 **Learning decision** (`update-spec` | `no-update` | `unsure`) and gate-compatible evidence per `.cstl/spec/guides/durable-learning-decision-guide.md`. Run `task.py archive <task> --check` when unsure.
 
 ## Evidence pack reference (optional — graceful skip)
 
@@ -19,7 +19,7 @@ Pack format: `version`, `source` (`retrieval-pack-orchestrator`), `contextPack.s
 ## Step 1: Survey current state
 
 ```bash
-{{PYTHON_CMD}} ./.trellis/scripts/get_context.py --mode record
+{{PYTHON_CMD}} ./.cstl/scripts/get_context.py --mode record
 ```
 
 This prints:
@@ -38,7 +38,7 @@ Run:
 git status --porcelain
 ```
 
-Filter out paths under `.trellis/workspace/` and `.trellis/tasks/` — those are managed by `add_session.py` and `task.py archive` auto-commits and will appear dirty as part of this skill's own work.
+Filter out paths under `.cstl/workspace/` and `.cstl/tasks/` — those are managed by `add_session.py` and `task.py archive` auto-commits and will appear dirty as part of this skill's own work.
 
 For each remaining dirty path, decide whether it belongs to **the selected task** or to **other parallel work** (e.g., another terminal window editing the same repo). Heuristics:
 
@@ -59,7 +59,7 @@ Then route:
 ## Step 3: Archive task(s)
 
 ```bash
-{{PYTHON_CMD}} ./.trellis/scripts/task.py archive <task-name>
+{{PYTHON_CMD}} ./.cstl/scripts/task.py archive <task-name>
 ```
 
 At minimum: the selected task (if any). Plus any extra tasks the user confirmed in Step 1. Each archive produces a `chore(task): archive ...` commit via the script's auto-commit.
@@ -69,7 +69,7 @@ If there is no selected task and the user did not confirm any cleanup archives,
 ## Step 4: Record session journal
 
 ```bash
-{{PYTHON_CMD}} ./.trellis/scripts/add_session.py \
+{{PYTHON_CMD}} ./.cstl/scripts/add_session.py \
   --title "Session Title" \
   --commit "hash1,hash2" \
   --summary "Brief summary"

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.
@@ -36,18 +36,18 @@ Index files list the specific guideline docs to read when you actually start cod
 ## Step 4: Decide next action
 From Step 1 you know whether a task is selected.
 
-- If `Selected task: none` → show the Task Dashboard; do **not** load `trellis-continue`. For a **small** request without a task, use `trellis-micro-grill` first.
-- If a task **is** selected and you need the next workflow step → use `trellis-continue` instead of repeating Steps 1–3 here.
+- If `Selected task: none` → show the Task Dashboard; do **not** load `cstl-continue`. For a **small** request without a task, use `cstl-micro-grill` first.
+- If a task **is** selected and you need the next workflow step → use `cstl-continue` instead of repeating Steps 1–3 here.
 
 If `Selected task: none`, ask the user to choose: select a task, create a task, inspect details, or continue without a task.
 
 If a task is selected, check the task directory:
 
-- **Selected task status `planning` + no `prd.md`** → Phase 1.1. Load the `trellis-brainstorm` skill.
+- **Selected task status `planning` + no `prd.md`** → Phase 1.1. Load the `cstl-brainstorm` skill.
 - **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.
 
@@ -57,13 +57,13 @@ If a task is selected, check the task directory:
 
 | User intent | Skill |
 |---|---|
-| Resume **selected** in-progress task | `trellis-continue` |
-| New feature / unclear requirements | `trellis-brainstorm` |
-| Small request, no task yet | `trellis-micro-grill` |
-| About to write code | `trellis-before-dev` |
-| Done coding / quality check | `trellis-check` |
-| Session wrap-up after Phase 3.4 commit | `trellis-finish-work` |
-| Stuck / fixed same bug multiple times | `trellis-break-loop` |
-| Learned something worth capturing | `trellis-update-spec` |
-
-Full rules + anti-rationalization table in `.trellis/workflow.md`.
+| Resume **selected** in-progress task | `cstl-continue` |
+| New feature / unclear requirements | `cstl-brainstorm` |
+| Small request, no task yet | `cstl-micro-grill` |
+| About to write code | `cstl-before-dev` |
+| Done coding / quality check | `cstl-check` |
+| Session wrap-up after Phase 3.4 commit | `cstl-finish-work` |
+| Stuck / fixed same bug multiple times | `cstl-break-loop` |
+| Learned something worth capturing | `cstl-update-spec` |
+
+Full rules + anti-rationalization table in `.cstl/workflow.md`.

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

@@ -23,7 +23,7 @@ export interface CommonBundledSkillFile {
     content: string;
 }
 export interface CommonBundledSkill {
-    /** Skill directory name, e.g. "trellis-meta" */
+    /** Skill directory name, e.g. "cstl-meta" */
     name: string;
     /** Files that must be written under the skill directory */
     files: CommonBundledSkillFile[];

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

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/templates/common/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAuBH,MAAM,WAAW,cAAc;IAC7B,oEAAoE;IACpE,IAAI,EAAE,MAAM,CAAC;IACb,0EAA0E;IAC1E,OAAO,EAAE,MAAM,CAAC;CACjB;AAED,MAAM,WAAW,sBAAsB;IACrC,4EAA4E;IAC5E,YAAY,EAAE,MAAM,CAAC;IACrB,0EAA0E;IAC1E,OAAO,EAAE,MAAM,CAAC;CACjB;AAED,MAAM,WAAW,kBAAkB;IACjC,gDAAgD;IAChD,IAAI,EAAE,MAAM,CAAC;IACb,2DAA2D;IAC3D,KAAK,EAAE,sBAAsB,EAAE,CAAC;CACjC;AAOD;;;GAGG;AACH,wBAAgB,mBAAmB,IAAI,cAAc,EAAE,CAMtD;AAED;;;GAGG;AACH,wBAAgB,iBAAiB,IAAI,cAAc,EAAE,CAMpD;AAuCD;;;;;GAKG;AACH,wBAAgB,wBAAwB,IAAI,kBAAkB,EAAE,CAM/D"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/templates/common/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAuBH,MAAM,WAAW,cAAc;IAC7B,oEAAoE;IACpE,IAAI,EAAE,MAAM,CAAC;IACb,0EAA0E;IAC1E,OAAO,EAAE,MAAM,CAAC;CACjB;AAED,MAAM,WAAW,sBAAsB;IACrC,4EAA4E;IAC5E,YAAY,EAAE,MAAM,CAAC;IACrB,0EAA0E;IAC1E,OAAO,EAAE,MAAM,CAAC;CACjB;AAED,MAAM,WAAW,kBAAkB;IACjC,6CAA6C;IAC7C,IAAI,EAAE,MAAM,CAAC;IACb,2DAA2D;IAC3D,KAAK,EAAE,sBAAsB,EAAE,CAAC;CACjC;AAOD;;;GAGG;AACH,wBAAgB,mBAAmB,IAAI,cAAc,EAAE,CAMtD;AAED;;;GAGG;AACH,wBAAgB,iBAAiB,IAAI,cAAc,EAAE,CAMpD;AAuCD;;;;;GAKG;AACH,wBAAgB,wBAAwB,IAAI,kBAAkB,EAAE,CAM/D"}

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.