@elevasis/sdk 0.5.14 → 0.5.16

package/reference/framework/index.mdx

@@ -21,7 +21,7 @@ Running `elevasis-sdk init my-project` produces the following agent infrastructu
 │   ├── tutorial.md             # Progressive learning path (3 tracks)
 │   └── work.md                 # Task tracking
 ├── hooks/
-│   └── enforce-sdk-boundary.mjs  # Blocks destructive git, gh CLI, external writes
+│   └── enforce-sdk-boundary.mjs  # Blocks file modifications outside project boundary
 ├── skills/
 │   └── creds/SKILL.md          # Credential management (auto-triggers)
 └── rules/
@@ -167,15 +167,15 @@ Section templates by doc type:
 
 **Command Routing Reference:**
 
-| Scenario                                | Command        |
-| --------------------------------------- | -------------- |
-| Starting new work                       | `/work create` |
-| Resuming yesterday's work               | `/work resume` |
-| Browsing what docs exist                | `/docs`        |
-| Creating a reference doc (not a task)   | `/docs create` |
-| Checking if docs match current code     | `/docs verify` |
-| Full maintenance pipeline (8 steps)     | `/meta fix`    |
-| Deploying code and auto-generating maps | `/meta deploy` |
+| Scenario                                | Command                                               |
+| --------------------------------------- | ----------------------------------------------------- |
+| Starting new work                       | `/work` (auto-detects new work from your description) |
+| Resuming yesterday's work               | `/work` (auto-resumes if one task is in-progress)     |
+| Browsing what docs exist                | `/docs`                                               |
+| Creating a reference doc (not a task)   | `/docs create`                                        |
+| Checking if docs match current code     | `/docs verify`                                        |
+| Full maintenance pipeline (8 steps)     | `/meta fix`                                           |
+| Deploying code and auto-generating maps | `/meta deploy`                                        |
 
 ---
 

package/reference/framework/project-structure.mdx

@@ -54,7 +54,7 @@ Project-level configuration. The scaffolded file includes `templateVersion`, whi
 import type { ElevasConfig } from '@elevasis/sdk'
 
 export default {
-  templateVersion: 27,
+  templateVersion: 28,
   // defaultStatus: 'dev',     // Default status for new resources ('dev' | 'prod')
   // dev: { port: 5170 },      // Local API port (internal development only)
 } satisfies ElevasConfig
@@ -96,7 +96,7 @@ This file is NOT scaffolded by default. The agent creates it the first time you
 
 ### `docs/in-progress/`
 
-Work-in-progress task documents created by `/work create`. Each file represents an active work item with objective, plan, progress markers, and resume context. `/work complete` moves finished items to their permanent location in `docs/`.
+Work-in-progress task documents managed by `/work`. Each file represents an active work item with objective, plan, progress markers, and resume context. When all steps are complete, the agent suggests finalizing the task, which moves finished items to their permanent location in `docs/`.
 
 This directory is NOT deployed -- it is filtered out during the doc scan in `elevasis-sdk deploy`.
 
@@ -112,7 +112,7 @@ Only `src/` and `docs/` are scaffolded by `elevasis-sdk init`. The following dir
 | `src/example/`         | `elevasis-sdk init` (default)    | Always -- echo starter workflow lives here (replace with your own) |
 | `src/shared/`          | `elevasis-sdk init` (default)    | Always -- cross-domain shared utilities (starts empty)             |
 | `docs/`                | `elevasis-sdk init` (default)    | Always                                                             |
-| `docs/in-progress/`    | Agent (on first `/work create`)  | When you create a task doc for in-progress work                    |
+| `docs/in-progress/`    | Agent (on first `/work`)         | When you create a task doc for in-progress work                    |
 | `docs/project-map.mdx` | `elevasis-sdk deploy`            | Auto-generated on every deploy                                     |
 | `docs/priorities.mdx`  | Agent (on first goal discussion) | When you discuss project goals or priorities                       |
 | `data/`                | Agent (on demand)                | When you connect a database                                        |
@@ -195,7 +195,7 @@ Do not remove or heavily edit `CLAUDE.md`. It is the primary context source that
 
 ### `.claude/settings.json`
 
-Sets `autoCompact: false`. This prevents Claude Code from automatically compacting context during long sessions, which can lose important earlier context about your project.
+Configures Claude Code for the workspace: disables auto-compaction (prevents losing earlier context in long sessions) and registers three hooks -- a PreToolUse boundary hook, a PostToolUse formatting/type-check hook, and a PostToolUseFailure error recovery hook.
 
 ### `.claude/memory/`
 
@@ -224,7 +224,7 @@ The `.claude/commands/` directory contains four commands covering the core devel
 
 - **`/meta`** -- Project lifecycle: init, status, fix, deploy, health
 - **`/docs`** -- Browse, create, and verify permanent documentation
-- **`/work`** -- Task tracking across sessions: list, create, save, resume, complete
+- **`/work`** -- Task tracking across sessions: auto-detects intent (create, save, resume); suggests complete
 - **`/tutorial`** -- Progressive learning path adapted to your skill profile
 
 For detailed command documentation, see [Agent System](agent).
@@ -235,7 +235,7 @@ For detailed command documentation, see [Agent System](agent).
 
 Not all scaffolded files participate in template updates. Files fall into two categories:
 
-**SCAFFOLD_FILES total: 30**
+**SCAFFOLD_FILES total: 32**
 
 **INIT_ONLY** (14 files) -- Written once during `elevasis-sdk init`, never updated by `elevasis-sdk update`:
 
@@ -245,10 +245,10 @@ Not all scaffolded files participate in template updates. Files fall into two ca
 - `docs/index.mdx`, `docs/in-progress/.gitkeep`
 - `.claude/rules/workspace-patterns.md`
 
-**MANAGED** (16 files) -- Written during `elevasis-sdk init` and checked/updatable by `elevasis-sdk update`:
+**MANAGED** (18 files) -- Written during `elevasis-sdk init` and checked/updatable by `elevasis-sdk update`:
 
 - `elevasis.config.ts`, `.gitignore`, `CLAUDE.md`, `.claude/settings.json`
-- One hook: `.claude/hooks/enforce-sdk-boundary.mjs`
+- Three hooks: `.claude/hooks/enforce-sdk-boundary.mjs`, `.claude/hooks/post-edit-validate.mjs`, `.claude/hooks/tool-failure-recovery.mjs`
 - Four command files: `.claude/commands/meta.md`, `.claude/commands/docs.md`, `.claude/commands/tutorial.md`, `.claude/commands/work.md`
 - One skill: `.claude/skills/creds/SKILL.md`
 - Five rule files: `.claude/rules/sdk-patterns.md`, `.claude/rules/docs-authoring.md`, `.claude/rules/memory-conventions.md`, `.claude/rules/project-map.md`, `.claude/rules/task-tracking.md`

package/reference/getting-started.mdx

@@ -31,7 +31,7 @@ my-project/
 │   │   ├── tutorial.md             # Progressive learning
 │   │   └── work.md                 # Task tracking
 │   ├── hooks/
-│   │   └── enforce-sdk-boundary.mjs # Blocks destructive commands (auto-loaded)
+│   │   └── enforce-sdk-boundary.mjs # Blocks file modifications outside project (auto-loaded)
 │   ├── scripts/
 │   │   └── statusline-command.js   # Dynamic status line script
 │   ├── skills/