@blxzer/cursor-trellis 0.2.9 → 0.3.2

package/dist/utils/workflow-resolver.js

@@ -20,7 +20,7 @@ import { TIMEOUTS, TEMPLATE_INDEX_URL, RegistryBackendError, parseRegistrySource
  * The id used to refer to the bundled native workflow.
  *
  * Treated as Trellis-managed for hash-tracking: when this id is selected by
- * `init --workflow` or `trellis workflow`, `.trellis/workflow.md` stays in
+ * `init --workflow` or `trellis workflow`, `.cstl/workflow.md` stays in
  * `.template-hashes.json`. Any other id is user-managed local workflow and
  * must be removed from the hash file (the durable-state contract in
  * design.md "Durable-state contract").

package/package.json

@@ -1,13 +1,12 @@
 {
   "name": "@blxzer/cursor-trellis",
-  "version": "0.2.9",
+  "version": "0.3.2",
   "description": "AI capabilities grow like ivy — Trellis provides the structure to guide them along a disciplined path",
   "type": "module",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
   "bin": {
-    "trellis": "./bin/trellis.js",
-    "tl": "./bin/trellis.js",
+    "cstl": "./bin/cstl.js",
     "smart-search": "./bin/smart-search.js"
   },
   "publishConfig": {
@@ -36,7 +35,7 @@
     "inquirer": "^9.3.7",
     "undici": "^6.21.0",
     "zod": "^4.4.2",
-    "@blxzer/cursor-trellis-core": "0.2.9"
+    "@blxzer/cursor-trellis-core": "0.3.2"
   },
   "devDependencies": {
     "@eslint/js": "^9.18.0",

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

@@ -1,83 +0,0 @@
-# Local Files Generated After Init
-
-`trellis init` writes the Trellis runtime into the user project. Later, `trellis 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.
-
-This page only describes files that are visible and editable inside the user project.
-
-## `.trellis/`
-
-```text
-.trellis/
-├── workflow.md
-├── config.yaml
-├── .developer
-├── .version
-├── .template-hashes.json
-├── .runtime/
-├── scripts/
-├── spec/
-├── tasks/
-└── workspace/
-```
-
-| 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. |
-
-## Platform Directories
-
-On a fresh `trellis init --cursor`, the only platform directory created is `.cursor/`. Trellis previously generated per-platform directories for many AI tools (`.claude/`, `.codex/`, `.opencode/`, etc.); those legacy directories are preserved by `trellis update` but new Trellis behavior ships to `.cursor/` only.
-
-Common categories inside `.cursor/`:
-
-| Category | Path | Purpose |
-| --- | --- | --- |
-| hooks | `.cursor/hooks/` | Hook scripts invoked from `.cursor/hooks.json`. Inject session context, workflow-state, and sub-agent context. |
-| settings/registration | `.cursor/hooks.json` | Registers which scripts run on which Cursor events. |
-| rules | `.cursor/rules/*.mdc` (`alwaysApply: true`) | Per-turn policy prepended before every prompt. |
-| agents | `.cursor/agents/` | Define agents such as `trellis-research`, `trellis-implement`, and `trellis-check`. |
-| 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.
-
-## Meaning Of Template Hashes
-
-`.trellis/.template-hashes.json` records the content hash from the last time Trellis wrote a template file. `trellis update` uses it to distinguish three cases:
-
-| Case | Update behavior |
-| --- | --- |
-| File was not modified by the user | It can be updated automatically. |
-| File was modified by the user | Prompt the user to overwrite, keep, or generate `.new`. |
-| File is no longer a current template | It may be deleted, renamed, or preserved according to migration rules. |
-
-When an AI customizes local Trellis files, it does not need to maintain hashes manually. It is normal for Trellis update to recognize the result as "modified by the user."
-
-## Local Customization Boundaries
-
-Editable by default:
-
-- `.trellis/workflow.md`
-- `.trellis/config.yaml`
-- `.trellis/spec/**`
-- `.trellis/scripts/**`
-- Platform hooks, settings, agents, skills, commands, prompts, and workflows
-
-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`
-
-Switch to the Trellis CLI source-code perspective only when the user explicitly wants to contribute upstream.