@blxzer/cursor-trellis 0.3.0 → 0.3.2

package/dist/templates/common/bundled-skills/cstl-meta/references/customize-local/change-hooks.md

@@ -6,9 +6,9 @@ Hooks are the automation layer that connects a platform to Trellis. When the use
 
 1. Target platform settings/config: `.cursor/hooks.json`
 2. Target platform hooks directory
-3. `.trellis/scripts/common/active_task.py`
-4. `.trellis/scripts/common/session_context.py`
-5. `.trellis/workflow.md`
+3. `.cstl/scripts/common/active_task.py`
+4. `.cstl/scripts/common/session_context.py`
+5. `.cstl/workflow.md`
 
 ## Common Hook Types
 
@@ -23,9 +23,9 @@ Hooks are the automation layer that connects a platform to Trellis. When the use
 
 1. Find the hook registration in settings/config.
 2. Confirm the registered script path exists.
-3. Read the hook script and identify inputs, outputs, and called `.trellis/scripts/`.
+3. Read the hook script and identify inputs, outputs, and called `.cstl/scripts/`.
 4. Modify hook behavior.
-5. If the hook depends on workflow content, synchronize `.trellis/workflow.md`.
+5. If the hook depends on workflow content, synchronize `.cstl/workflow.md`.
 
 ## Example: Change New-Session Injection Content
 
@@ -36,15 +36,15 @@ First find the session-start hook:
 .cursor/hooks/session-start.py
 ```
 
-If the hook ultimately calls `.trellis/scripts/get_context.py` or `session_context.py`, editing the local script is usually more robust than hard-coding content in the hook.
+If the hook ultimately calls `.cstl/scripts/get_context.py` or `session_context.py`, editing the local script is usually more robust than hard-coding content in the hook.
 
 ## Example: Agent Did Not Read JSONL
 
 First confirm:
 
 ```bash
-python3 ./.trellis/scripts/task.py selected --source
-python3 ./.trellis/scripts/task.py validate <task>
+python3 ./.cstl/scripts/task.py selected --source
+python3 ./.cstl/scripts/task.py validate <task>
 ```
 
 If the task and JSONL are correct, determine whether the platform uses hook push or agent pull. For hook push, edit `inject-subagent-context`; for agent pull, edit the agent file.
@@ -53,5 +53,5 @@ If the task and JSONL are correct, determine whether the platform uses hook push
 
 - Settings handle registration, hook scripts handle behavior; inspect both together.
 - Cursor's hook event surface has changed between releases; confirm against the current Cursor build before wiring a new event.
-- Hooks should read project-local `.trellis/`; they should not depend on Trellis upstream source paths.
+- Hooks should read project-local `.cstl/`; they should not depend on Trellis upstream source paths.
 - Hook failures should produce visible errors so AI does not silently lose context.

package/dist/templates/common/bundled-skills/cstl-meta/references/customize-local/change-skills-or-commands.md

@@ -4,10 +4,10 @@ When the user wants to change AI entry points, auto-trigger rules, or explicit c
 
 ## Read These Files First
 
-1. `.trellis/workflow.md`
+1. `.cstl/workflow.md`
 2. Target platform skill/command/prompt/workflow directory
 3. Related agent or hook files
-4. Whether project rules already exist in `.trellis/spec/`
+4. Whether project rules already exist in `.cstl/spec/`
 
 ## Which Entry Type To Choose
 
@@ -15,8 +15,8 @@ When the user wants to change AI entry points, auto-trigger rules, or explicit c
 | --- | --- |
 | AI should automatically know a capability | Add or modify a skill. |
 | User wants to trigger manually with a command | Add or modify a command/prompt/workflow. |
-| Team project conventions | Prefer `.trellis/spec/` or a project-local skill. |
-| Change Trellis flow semantics | Synchronize `.trellis/workflow.md`. |
+| Team project conventions | Prefer `.cstl/spec/` or a project-local skill. |
+| Change Trellis flow semantics | Synchronize `.cstl/workflow.md`. |
 
 ## Modify A Skill
 
@@ -45,11 +45,11 @@ Do not write vague descriptions such as "helpful project skill"; they can trigge
 Explicit entry points should state:
 
 - How the user triggers it.
-- Which `.trellis/` files to read.
+- Which `.cstl/` files to read.
 - Which scripts to run.
 - How to report after completion.
 
-If a command only repeats workflow rules, prefer making it reference/read `.trellis/workflow.md` instead of maintaining a second copy of the flow.
+If a command only repeats workflow rules, prefer making it reference/read `.cstl/workflow.md` instead of maintaining a second copy of the flow.
 
 ## Common Paths
 
@@ -74,4 +74,4 @@ For shared skill layers across tools, consider `.agents/skills/` on platforms th
 
 - Do not mix platform-specific syntax from removed adapters into the Cursor skill files.
 - Do not change only the dogfooded `.cursor/skills/` copy while forgetting to mirror the published template `packages/cli/src/templates/cursor/skills/` (and vice versa); see `cross-layer-thinking-guide.md.txt` → Cross-Package Template Consistency.
-- Do not hide long-term engineering conventions inside a command; write them to `.trellis/spec/`.
+- Do not hide long-term engineering conventions inside a command; write them to `.cstl/spec/`.

package/dist/templates/common/bundled-skills/cstl-meta/references/customize-local/change-spec-structure.md

@@ -1,23 +1,23 @@
 # Change Local Spec Structure
 
-When the user wants to change the engineering conventions AI follows, add new spec layers, or adjust monorepo package mapping, edit `.trellis/spec/` and `.trellis/config.yaml`.
+When the user wants to change the engineering conventions AI follows, add new spec layers, or adjust monorepo package mapping, edit `.cstl/spec/` and `.cstl/config.yaml`.
 
 ## Read These Files First
 
-1. `.trellis/config.yaml`
-2. `.trellis/spec/`
-3. `.trellis/workflow.md` planning artifact guidance and Phase 3.3
+1. `.cstl/config.yaml`
+2. `.cstl/spec/`
+3. `.cstl/workflow.md` planning artifact guidance and Phase 3.3
 4. Selected task `implement.jsonl` / `check.jsonl`
 
 ## Common Needs
 
 | Need | Edit location |
 | --- | --- |
-| Add backend/frontend/docs/test spec layer | `.trellis/spec/<layer>/` or `.trellis/spec/<package>/<layer>/` |
-| Add shared thinking guides | `.trellis/spec/guides/` |
-| Adjust monorepo packages | `packages` in `.trellis/config.yaml` |
-| Change default package | `default_package` in `.trellis/config.yaml` |
-| Control spec scanning scope | `spec_scope` in `.trellis/config.yaml` |
+| Add backend/frontend/docs/test spec layer | `.cstl/spec/<layer>/` or `.cstl/spec/<package>/<layer>/` |
+| Add shared thinking guides | `.cstl/spec/guides/` |
+| Adjust monorepo packages | `packages` in `.cstl/config.yaml` |
+| Change default package | `default_package` in `.cstl/config.yaml` |
+| Control spec scanning scope | `spec_scope` in `.cstl/config.yaml` |
 | Make a task read a new spec | Task `implement.jsonl` / `check.jsonl` |
 
 ## Add A Spec Layer
@@ -25,7 +25,7 @@ When the user wants to change the engineering conventions AI follows, add new sp
 Single-repository example:
 
 ```text
-.trellis/spec/security/
+.cstl/spec/security/
 ├── index.md
 └── auth.md
 ```
@@ -33,7 +33,7 @@ Single-repository example:
 Monorepo example:
 
 ```text
-.trellis/spec/webapp/security/
+.cstl/spec/webapp/security/
 ├── index.md
 └── auth.md
 ```
@@ -50,13 +50,13 @@ Monorepo example:
 Adding a spec does not mean every task automatically reads it. The selected task must reference it in JSONL:
 
 ```bash
-python3 ./.trellis/scripts/task.py add-context <task> implement ".trellis/spec/webapp/security/index.md" "Security conventions"
-python3 ./.trellis/scripts/task.py add-context <task> check ".trellis/spec/webapp/security/index.md" "Security review rules"
+python3 ./.cstl/scripts/task.py add-context <task> implement ".cstl/spec/webapp/security/index.md" "Security conventions"
+python3 ./.cstl/scripts/task.py add-context <task> check ".cstl/spec/webapp/security/index.md" "Security review rules"
 ```
 
 ## Change Monorepo Packages
 
-Example `.trellis/config.yaml`:
+Example `.cstl/config.yaml`:
 
 ```yaml
 packages:
@@ -70,7 +70,7 @@ default_package: webapp
 After editing, run:
 
 ```bash
-python3 ./.trellis/scripts/get_context.py --mode packages
+python3 ./.cstl/scripts/get_context.py --mode packages
 ```
 
 Use this output to confirm AI can see the correct packages and spec layers.

package/dist/templates/common/bundled-skills/cstl-meta/references/customize-local/change-task-lifecycle.md

@@ -1,39 +1,39 @@
 # Change Local Task Lifecycle
 
-Task lifecycle includes creation, selection, execution start, context configuration, archive, parent/child tasks, and lifecycle hooks. The default customization targets are `.trellis/tasks/`, `.trellis/config.yaml`, and `.trellis/scripts/`.
+Task lifecycle includes creation, selection, execution start, context configuration, archive, parent/child tasks, and lifecycle hooks. The default customization targets are `.cstl/tasks/`, `.cstl/config.yaml`, and `.cstl/scripts/`.
 
 ## Read These Files First
 
-1. `.trellis/workflow.md`
-2. `.trellis/config.yaml`
-3. `.trellis/scripts/task.py`
-4. `.trellis/scripts/common/task_store.py`
-5. `.trellis/scripts/common/task_utils.py`
-6. The selected task's `.trellis/tasks/<task>/task.json`
+1. `.cstl/workflow.md`
+2. `.cstl/config.yaml`
+3. `.cstl/scripts/task.py`
+4. `.cstl/scripts/common/task_store.py`
+5. `.cstl/scripts/common/task_utils.py`
+6. The selected task's `.cstl/tasks/<task>/task.json`
 
 ## Common Needs And Edit Points
 
 | Need | Edit point |
 | --- | --- |
-| Automatically sync an external system after task creation | `hooks.after_create` in `.trellis/config.yaml`. |
-| Automatically update status after execution start | `hooks.after_start` in `.trellis/config.yaml`. |
-| Clean external resources after archive | `hooks.after_archive` in `.trellis/config.yaml`. |
-| Change default task fields | `.trellis/scripts/common/task_store.py`. |
-| Change task parsing/search | `.trellis/scripts/common/task_utils.py`. |
-| Change selected task behavior | `.trellis/scripts/common/active_task.py`. |
+| Automatically sync an external system after task creation | `hooks.after_create` in `.cstl/config.yaml`. |
+| Automatically update status after execution start | `hooks.after_start` in `.cstl/config.yaml`. |
+| Clean external resources after archive | `hooks.after_archive` in `.cstl/config.yaml`. |
+| Change default task fields | `.cstl/scripts/common/task_store.py`. |
+| Change task parsing/search | `.cstl/scripts/common/task_utils.py`. |
+| Change selected task behavior | `.cstl/scripts/common/active_task.py`. |
 
 ## lifecycle hooks
 
-`.trellis/config.yaml` supports:
+`.cstl/config.yaml` supports:
 
 ```yaml
 hooks:
   after_create:
-    - "python3 .trellis/scripts/hooks/my_sync.py create"
+    - "python3 .cstl/scripts/hooks/my_sync.py create"
   after_start:
-    - "python3 .trellis/scripts/hooks/my_sync.py start"
+    - "python3 .cstl/scripts/hooks/my_sync.py start"
   after_archive:
-    - "python3 .trellis/scripts/hooks/my_sync.py archive"
+    - "python3 .cstl/scripts/hooks/my_sync.py archive"
 ```
 
 Hook commands receive the `TASK_JSON_PATH` environment variable, pointing to the task's `task.json`. Hook failures should usually warn, but not block the main task operation.
@@ -55,15 +55,15 @@ If standard fields really need to change, inspect every local script that reads
 
 ## Change Selected Task
 
-Selected task is session-level state stored in `.trellis/.runtime/sessions/`. Do not fall back to a global `.current-task` model. If the user wants to change selected task behavior, edit:
+Selected task is session-level state stored in `.cstl/.runtime/sessions/`. Do not fall back to a global `.current-task` model. If the user wants to change selected task behavior, edit:
 
-- `.trellis/scripts/common/active_task.py`
+- `.cstl/scripts/common/active_task.py`
 - platform hooks or shell session bridges
-- selected task descriptions in `.trellis/workflow.md`
+- selected task descriptions in `.cstl/workflow.md`
 
 ### `task.py create` Does Not Select
 
-`cmd_create` in `.trellis/scripts/common/task_store.py` writes the task directory and planning artifacts only. The behavior:
+`cmd_create` in `.cstl/scripts/common/task_store.py` writes the task directory and planning artifacts only. The behavior:
 
 - The task's `status=planning` is written.
 - No selected-task pointer is written, even when session identity exists.
@@ -71,18 +71,18 @@ Selected task is session-level state stored in `.trellis/.runtime/sessions/`. Do
 
 This keeps new sessions and bare task creation at `Selected task: none` until a live-session choice is made.
 
-If you fork `task.py` to add a new creation path (e.g. an external import that bypasses `cmd_create`), audit that it does not auto-select or auto-start the created task. The full status writer table is in `.trellis/spec/cli/backend/workflow-state-contract.md`.
+If you fork `task.py` to add a new creation path (e.g. an external import that bypasses `cmd_create`), audit that it does not auto-select or auto-start the created task. The full status writer table is in `.cstl/spec/cli/backend/workflow-state-contract.md`.
 
 ## Modification Steps
 
-1. Confirm the selected task with `python3 ./.trellis/scripts/task.py selected --source`.
+1. Confirm the selected task with `python3 ./.cstl/scripts/task.py selected --source`.
 2. Read the selected task's `task.json` and confirm status and fields.
-3. For configuration needs, edit `.trellis/config.yaml` first.
-4. For script behavior needs, then edit `.trellis/scripts/`.
-5. If the AI flow changed, synchronize `.trellis/workflow.md`.
+3. For configuration needs, edit `.cstl/config.yaml` first.
+4. For script behavior needs, then edit `.cstl/scripts/`.
+5. If the AI flow changed, synchronize `.cstl/workflow.md`.
 
 ## Do Not
 
-- Do not directly edit `.trellis/.runtime/sessions/` to "fix" business state.
+- Do not directly edit `.cstl/.runtime/sessions/` to "fix" business state.
 - Do not hard-code project-private fields into scripts; prefer `meta`.
 - Do not default to asking the user to fork Trellis CLI.

package/dist/templates/common/bundled-skills/cstl-meta/references/customize-local/change-workflow.md

@@ -1,10 +1,10 @@
 # Change Local Workflow
 
-When the user wants to change Trellis phases, next-action hints, whether to create tasks, whether to use sub-agents, or when to check/wrap up, edit `.trellis/workflow.md` first.
+When the user wants to change Trellis phases, next-action hints, whether to create tasks, whether to use sub-agents, or when to check/wrap up, edit `.cstl/workflow.md` first.
 
 ## Read These Files First
 
-1. `.trellis/workflow.md`
+1. `.cstl/workflow.md`
 2. Entry files for the current platform, such as skills/commands/prompts/workflows
 3. The selected task's `task.json` and `prd.md`
 
@@ -21,11 +21,11 @@ When the user wants to change Trellis phases, next-action hints, whether to crea
 
 ## Modification Steps
 
-1. Find the relevant section in `.trellis/workflow.md`.
+1. Find the relevant section in `.cstl/workflow.md`.
 2. When changing rules, keep explicit trigger conditions and next actions.
 3. If adding or renaming a skill/agent, synchronize the corresponding files in platform directories.
-4. Workflow-state changes only need an edit to the `[workflow-state:STATUS]` block in `.trellis/workflow.md`. The hook is parser-only — it reads whatever you put in the block. Keep the opening and closing tags' STATUS strings identical (`[workflow-state:foo]…[/workflow-state:foo]`); mismatched STATUS pairs are silently dropped.
-5. Make the AI reread `.trellis/workflow.md`; do not keep using rules from the old conversation.
+4. Workflow-state changes only need an edit to the `[workflow-state:STATUS]` block in `.cstl/workflow.md`. The hook is parser-only — it reads whatever you put in the block. Keep the opening and closing tags' STATUS strings identical (`[workflow-state:foo]…[/workflow-state:foo]`); mismatched STATUS pairs are silently dropped.
+5. Make the AI reread `.cstl/workflow.md`; do not keep using rules from the old conversation.
 
 ## Example: Relax Task Creation Requirements
 
@@ -58,8 +58,8 @@ If the user wants only one platform to avoid sub-agents, first confirm whether t
 | `in_progress` | check passed | Phase 3.1 (verify quality + spec update) |
 | `completed` | task is still in active tree | Phase 3.5 (run `cstl-finish-work` to archive) |
 
-When you add a custom status (e.g. `in-review`), add a `[workflow-state:in-review]` block in `.trellis/workflow.md` for the per-turn breadcrumb AND extend this route table — usually by editing the `cstl-continue` skill (`.cursor/skills/cstl-continue/` or the equivalent command file) to add a row that decides where to resume from. Without the route entry, the resume flow will fall through to a default branch and the user will not land on the step you intended.
+When you add a custom status (e.g. `in-review`), add a `[workflow-state:in-review]` block in `.cstl/workflow.md` for the per-turn breadcrumb AND extend this route table — usually by editing the `cstl-continue` skill (`.cursor/skills/cstl-continue/` or the equivalent command file) to add a row that decides where to resume from. Without the route entry, the resume flow will fall through to a default branch and the user will not land on the step you intended.
 
 ## Notes
 
-`.trellis/workflow.md` is the local project workflow, not an immutable template. The user can adapt it to team habits. After editing it, platform entry files may still contain old descriptions, so inspect them too.
+`.cstl/workflow.md` is the local project workflow, not an immutable template. The user can adapt it to team habits. After editing it, platform entry files may still contain old descriptions, so inspect them too.

package/dist/templates/common/bundled-skills/cstl-meta/references/customize-local/overview.md

@@ -1,6 +1,6 @@
 # Local Customization Overview
 
-This directory is for local AI working in a user project where Trellis was installed through npm and `cstl init` has already been run. The AI should modify generated `.trellis/` and platform directories inside the project, not Trellis CLI upstream source code.
+This directory is for local AI working in a user project where Trellis was installed through npm and `cstl init` has already been run. The AI should modify generated `.cstl/` and platform directories inside the project, not Trellis CLI upstream source code.
 
 ## First Determine What The User Actually Wants To Change
 
@@ -17,21 +17,21 @@ This directory is for local AI working in a user project where Trellis was insta
 
 ## General Operation Order
 
-1. **Confirm platform and directories**: inspect which directories exist; on a fresh `cstl init --cursor` only `.cursor/` and `.trellis/` are created.
-2. **Confirm the selected task**: run `python3 ./.trellis/scripts/task.py selected --source`.
-3. **Read the local source of truth**: prefer `.trellis/workflow.md`, `.trellis/config.yaml`, and relevant platform files.
+1. **Confirm platform and directories**: inspect which directories exist; on a fresh `cstl init --cursor` only `.cursor/` and `.cstl/` are created.
+2. **Confirm the selected task**: run `python3 ./.cstl/scripts/task.py selected --source`.
+3. **Read the local source of truth**: prefer `.cstl/workflow.md`, `.cstl/config.yaml`, and relevant platform files.
 4. **Modify narrowly**: edit only files related to the user's request.
-5. **Synchronize semantics**: if a shared flow changes, check whether platform entry points also need changes; if a platform entry changes, check whether `.trellis/workflow.md` still agrees.
+5. **Synchronize semantics**: if a shared flow changes, check whether platform entry points also need changes; if a platform entry changes, check whether `.cstl/workflow.md` still agrees.
 
 ## Local File Priority
 
 | Layer | Files |
 | --- | --- |
-| Workflow | `.trellis/workflow.md` |
-| Project configuration | `.trellis/config.yaml` |
-| Task material | `.trellis/tasks/<task>/` |
-| Project specs | `.trellis/spec/` |
-| Runtime scripts | `.trellis/scripts/` |
+| Workflow | `.cstl/workflow.md` |
+| Project configuration | `.cstl/config.yaml` |
+| Task material | `.cstl/tasks/<task>/` |
+| Project specs | `.cstl/spec/` |
+| Runtime scripts | `.cstl/scripts/` |
 | Platform integration | `.cursor/` plus legacy adapter directories preserved by `cstl update` |
 | Shared skill | `.agents/skills/` |
 
@@ -41,7 +41,7 @@ This directory is for local AI working in a user project where Trellis was insta
 - Do not edit `node_modules/@blxzer/cursor-trellis`.
 - Do not assume the user has the Trellis GitHub repository.
 - Do not overwrite local files already modified by the user with default templates.
-- Do not put team project rules into public `cstl-meta`; project rules belong in `.trellis/spec/` or a local skill.
+- Do not put team project rules into public `cstl-meta`; project rules belong in `.cstl/spec/` or a local skill.
 
 ## When To Inspect Upstream Source
 

package/dist/templates/common/bundled-skills/cstl-meta/references/local-architecture/context-injection.md

@@ -1,15 +1,15 @@
 # Local Context Injection System
 
-Trellis context injection aims to make AI read the right files at the right time instead of relying on model memory. In a user project, injection is implemented by `.trellis/` scripts together with platform hooks, agents, and skills.
+Trellis context injection aims to make AI read the right files at the right time instead of relying on model memory. In a user project, injection is implemented by `.cstl/` scripts together with platform hooks, agents, and skills.
 
 ## Injected Context Types
 
 | Type | Source | Purpose |
 | --- | --- | --- |
-| session context | `.trellis/scripts/get_context.py` | Current developer, git status, selected task, Task Dashboard, active tasks, journal, packages. |
-| workflow context | `.trellis/workflow.md` | Current Trellis flow and next action. |
-| spec context | `.trellis/spec/` + task JSONL | Specs that must be followed during implementation/checking. |
-| task context | `.trellis/tasks/<task>/prd.md`, `design.md`, `implement.md`, `research/` | Selected task requirements, design, execution plan, and research. |
+| session context | `.cstl/scripts/get_context.py` | Current developer, git status, selected task, Task Dashboard, active tasks, journal, packages. |
+| workflow context | `.cstl/workflow.md` | Current Trellis flow and next action. |
+| spec context | `.cstl/spec/` + task JSONL | Specs that must be followed during implementation/checking. |
+| task context | `.cstl/tasks/<task>/prd.md`, `design.md`, `implement.md`, `research/` | Selected task requirements, design, execution plan, and research. |
 | platform context | Platform hooks/settings/agents | Lets different AI tools read the files above through their own mechanisms. |
 
 ## session-start
@@ -26,9 +26,9 @@ If the user feels the AI does not know the selected task in a new session, first
 
 ## workflow-state
 
-workflow-state is a lightweight hint injected around each user turn. Based on selected task status, it selects a block from `.trellis/workflow.md`, such as `no_task`, `planning`, `in_progress`, or `completed`.
+workflow-state is a lightweight hint injected around each user turn. Based on selected task status, it selects a block from `.cstl/workflow.md`, such as `no_task`, `planning`, `in_progress`, or `completed`.
 
-If the user wants to change "what the AI should do next in a given state," edit the corresponding state block in `.trellis/workflow.md` first.
+If the user wants to change "what the AI should do next in a given state," edit the corresponding state block in `.cstl/workflow.md` first.
 
 ## sub-agent context
 
@@ -44,14 +44,14 @@ In both modes, JSONL files in the task directory are the manifest for spec/resea
 `implement.jsonl` and `check.jsonl` contain one JSON object per line:
 
 ```jsonl
-{"file": ".trellis/spec/backend/index.md", "reason": "Backend rules"}
+{"file": ".cstl/spec/backend/index.md", "reason": "Backend rules"}
 ```
 
 Readers should skip seed rows without a `file` field. When configuring JSONL, the AI should include only spec/research files, not pre-register code files that will be modified.
 
 ## Selected Task And Context Key
 
-Selected task state lives in `.trellis/.runtime/sessions/` and is isolated per session. Hooks try to resolve the context key from platform events, environment variables, transcript paths, or `TRELLIS_CONTEXT_ID`.
+Selected task state lives in `.cstl/.runtime/sessions/` and is isolated per session. Hooks try to resolve the context key from platform events, environment variables, transcript paths, or `TRELLIS_CONTEXT_ID`.
 
 If shell commands cannot see the same context key, `task.py selected --source` may report no selected task. In that case, check whether the platform passes session identity into the shell instead of hand-writing a global current-task file.
 
@@ -60,9 +60,9 @@ If shell commands cannot see the same context key, `task.py selected --source` m
 | Need | Edit location |
 | --- | --- |
 | Change session-start injected content | The platform's `session-start` hook or plugin file. |
-| Change per-turn workflow-state rules | `[workflow-state:STATUS]` block in `.trellis/workflow.md`. The platform workflow-state hook parses these blocks verbatim and embeds no fallback text. |
+| Change per-turn workflow-state rules | `[workflow-state:STATUS]` block in `.cstl/workflow.md`. The platform workflow-state hook parses these blocks verbatim and embeds no fallback text. |
 | Change how sub-agents read context | Platform agent definitions, the `inject-subagent-context` hook, or agent preludes. |
-| Change JSONL validation/display | `.trellis/scripts/common/task_context.py`. |
-| Change selected task resolution | `.trellis/scripts/common/active_task.py`. |
+| Change JSONL validation/display | `.cstl/scripts/common/task_context.py`. |
+| Change selected task resolution | `.cstl/scripts/common/active_task.py`. |
 
 When modifying context injection, verify two things: new sessions can see the correct task, and sub-agents can see the correct task artifacts/spec/research.

package/dist/templates/common/bundled-skills/cstl-meta/references/local-architecture/generated-files.md

@@ -1,13 +1,13 @@
 # Local Files Generated After Init
 
-`cstl init` writes the Trellis runtime into the user project. Later, `cstl update` tries to update Trellis-managed template files, but it uses `.trellis/.template-hashes.json` to determine which files have already been modified by the user.
+`cstl init` writes the Trellis runtime into the user project. Later, `cstl update` tries to update Trellis-managed template files, but it uses `.cstl/.template-hashes.json` to determine which files have already been modified by the user.
 
 This page only describes files that are visible and editable inside the user project.
 
-## `.trellis/`
+## `.cstl/`
 
 ```text
-.trellis/
+.cstl/
 ├── workflow.md
 ├── config.yaml
 ├── .developer
@@ -22,16 +22,16 @@ This page only describes files that are visible and editable inside the user pro
 
 | Path | Usually editable? | Notes |
 | --- | --- | --- |
-| `.trellis/workflow.md` | Yes | Local workflow documentation and AI routing rules. |
-| `.trellis/config.yaml` | Yes | Project configuration, hooks, packages, journal line limits, and related settings. |
-| `.trellis/spec/` | Yes | Project specs, intended to be updated regularly by users and AI. |
-| `.trellis/tasks/` | Yes | Task material and research artifacts, maintained by the task workflow. |
-| `.trellis/workspace/` | Yes | Session records, usually written by `add_session.py`. |
-| `.trellis/scripts/` | Carefully | Local runtime. It can be customized, but only after understanding the call chain. |
-| `.trellis/.runtime/` | No | Runtime state, usually written automatically by hooks/scripts. |
-| `.trellis/.developer` | Carefully | Current developer identity. |
-| `.trellis/.version` | No | Trellis version record used by update/migration logic. |
-| `.trellis/.template-hashes.json` | No | Template hash record. Do not hand-write business rules here. |
+| `.cstl/workflow.md` | Yes | Local workflow documentation and AI routing rules. |
+| `.cstl/config.yaml` | Yes | Project configuration, hooks, packages, journal line limits, and related settings. |
+| `.cstl/spec/` | Yes | Project specs, intended to be updated regularly by users and AI. |
+| `.cstl/tasks/` | Yes | Task material and research artifacts, maintained by the task workflow. |
+| `.cstl/workspace/` | Yes | Session records, usually written by `add_session.py`. |
+| `.cstl/scripts/` | Carefully | Local runtime. It can be customized, but only after understanding the call chain. |
+| `.cstl/.runtime/` | No | Runtime state, usually written automatically by hooks/scripts. |
+| `.cstl/.developer` | Carefully | Current developer identity. |
+| `.cstl/.version` | No | Trellis version record used by update/migration logic. |
+| `.cstl/.template-hashes.json` | No | Template hash record. Do not hand-write business rules here. |
 
 ## Platform Directories
 
@@ -48,11 +48,11 @@ Common categories inside `.cursor/`:
 | skills | `.cursor/skills/` | Skills that auto-trigger or can be read by AI. |
 | commands | `.cursor/commands/` | Legacy compatibility-only user-invoked entry points. |
 
-When modifying a platform directory, also confirm whether `.trellis/workflow.md` still describes the same flow.
+When modifying a platform directory, also confirm whether `.cstl/workflow.md` still describes the same flow.
 
 ## Meaning Of Template Hashes
 
-`.trellis/.template-hashes.json` records the content hash from the last time Trellis wrote a template file. `cstl update` uses it to distinguish three cases:
+`.cstl/.template-hashes.json` records the content hash from the last time Trellis wrote a template file. `cstl update` uses it to distinguish three cases:
 
 | Case | Update behavior |
 | --- | --- |
@@ -66,10 +66,10 @@ When an AI customizes local Trellis files, it does not need to maintain hashes m
 
 Editable by default:
 
-- `.trellis/workflow.md`
-- `.trellis/config.yaml`
-- `.trellis/spec/**`
-- `.trellis/scripts/**`
+- `.cstl/workflow.md`
+- `.cstl/config.yaml`
+- `.cstl/spec/**`
+- `.cstl/scripts/**`
 - Platform hooks, settings, agents, skills, commands, prompts, and workflows
 
 Do not edit by default:
@@ -77,7 +77,7 @@ Do not edit by default:
 - Global npm install directory
 - `node_modules/@blxzer/cursor-trellis`
 - Trellis GitHub repository source code
-- Concrete state files under `.trellis/.runtime/**`
-- Hash contents inside `.trellis/.template-hashes.json`
+- Concrete state files under `.cstl/.runtime/**`
+- Hash contents inside `.cstl/.template-hashes.json`
 
 Switch to the Trellis CLI source-code perspective only when the user explicitly wants to contribute upstream.

package/dist/templates/common/bundled-skills/cstl-meta/references/local-architecture/overview.md

@@ -4,7 +4,7 @@
 
 Therefore, when an AI uses this skill, the default customization target is local files inside the user project:
 
-- `.trellis/`: workflow, tasks, specs, memory, scripts, and runtime state.
+- `.cstl/`: workflow, tasks, specs, memory, scripts, and runtime state.
 - Platform directory: `.cursor/` — skills, agents, hooks, commands, rules.
 - Shared skill layer: `.agents/skills/` (industry skill-sharing path; kept when present but not extended by new Trellis behavior).
 
@@ -14,8 +14,8 @@ Do not default to guiding the user to fork the Trellis CLI repository. Treat ups
 
 Trellis provides three layers inside a user project:
 
-1. **Workflow layer**: `.trellis/workflow.md` defines phases, routing, next actions, and prompt blocks.
-2. **Persistence layer**: `.trellis/tasks/`, `.trellis/spec/`, and `.trellis/workspace/` store tasks, specs, and session memory.
+1. **Workflow layer**: `.cstl/workflow.md` defines phases, routing, next actions, and prompt blocks.
+2. **Persistence layer**: `.cstl/tasks/`, `.cstl/spec/`, and `.cstl/workspace/` store tasks, specs, and session memory.
 3. **Platform integration layer**: hooks, settings, agents, skills, commands, prompts, and workflows in platform directories connect the Trellis workflow to different AI tools.
 
 All three layers live inside the user project, so an AI can read and modify them directly.
@@ -24,21 +24,21 @@ All three layers live inside the user project, so an AI can read and modify them
 
 | Path | Purpose |
 | --- | --- |
-| `.trellis/workflow.md` | Workflow phases, skill routing, and workflow-state prompt blocks. |
-| `.trellis/config.yaml` | Project configuration, task lifecycle hooks, monorepo package configuration, and journal configuration. |
-| `.trellis/spec/` | The user's project-specific coding conventions and thinking guides. |
-| `.trellis/tasks/` | Each task's PRD, technical notes, research files, and JSONL context. |
-| `.trellis/workspace/` | Per-developer journals and cross-session memory. |
-| `.trellis/scripts/` | Local Python runtime used by commands, hooks, and context injection. |
-| `.trellis/.runtime/` | Session-level runtime state, such as the selected task pointer. |
-| `.trellis/.template-hashes.json` | Template hashes for Trellis-managed files, used by update to determine whether local files were modified by the user. |
+| `.cstl/workflow.md` | Workflow phases, skill routing, and workflow-state prompt blocks. |
+| `.cstl/config.yaml` | Project configuration, task lifecycle hooks, monorepo package configuration, and journal configuration. |
+| `.cstl/spec/` | The user's project-specific coding conventions and thinking guides. |
+| `.cstl/tasks/` | Each task's PRD, technical notes, research files, and JSONL context. |
+| `.cstl/workspace/` | Per-developer journals and cross-session memory. |
+| `.cstl/scripts/` | Local Python runtime used by commands, hooks, and context injection. |
+| `.cstl/.runtime/` | Session-level runtime state, such as the selected task pointer. |
+| `.cstl/.template-hashes.json` | Template hashes for Trellis-managed files, used by update to determine whether local files were modified by the user. |
 
 ## AI Customization Principles
 
-1. **Find the local source of truth first**: Do not edit from memory. Read `.trellis/workflow.md`, `.trellis/config.yaml`, the relevant platform directory, and related task files first.
+1. **Find the local source of truth first**: Do not edit from memory. Read `.cstl/workflow.md`, `.cstl/config.yaml`, the relevant platform directory, and related task files first.
 2. **Edit the user project, not the npm package cache**: Modify generated files inside the project, not `node_modules` or the global npm install directory.
-3. **Keep platform files aligned with `.trellis/`**: If workflow routing changes, also check whether platform skills or commands still describe the same flow.
-4. **Put project-specific rules in `.trellis/spec/` or a local skill**: Do not put team conventions into `cstl-meta`.
+3. **Keep platform files aligned with `.cstl/`**: If workflow routing changes, also check whether platform skills or commands still describe the same flow.
+4. **Put project-specific rules in `.cstl/spec/` or a local skill**: Do not put team conventions into `cstl-meta`.
 5. **Preserve user changes**: If a file was already modified locally, work from the current content instead of overwriting it with a default template.
 
 ## How To Use This Directory