@ulysses-ai/create-workspace 0.14.0-beta.3 → 0.15.0-beta.0

package/template/.claude/skills/aside/SKILL.md

@@ -12,31 +12,34 @@ Capture a drive-by idea without interrupting the current conversation. By defaul
 - `/aside <thought>` — researched mode (default). Background subagent explores the idea.
 - `/aside --quick <thought>` — note only. No subagent, no research. Just park the thought.
 
-Everything after `/aside` (or `/aside --quick`) is the user's thought. No name parameter — the filename is generated from the content.
+Everything after `/aside` (or `/aside --quick`) is the user's thought. No name parameter — the slug is generated from the content.
 
 ## Quick Mode (`--quick`)
 
 No subagent. Execute these steps directly:
 
-1. Parse the user's thought from the arguments (everything after `--quick`)
-2. Generate a kebab-case slug from the content (3-5 words that capture the core idea)
-3. Check if `shared-context/{user}/local-only-{slug}.md` exists. If so, append `-2`, `-3`, etc.
-4. Infer 2-3 threads worth exploring later for the Further Investigation section
-5. Write the file using the Quick Mode template below
-6. Report the file path to the user: "Noted: `shared-context/{user}/local-only-{slug}.md`"
+1. Parse the user's thought from the arguments (everything after `--quick`).
+2. Generate a kebab-case slug from the content (3-5 words that capture the core idea).
+3. Compose the body using the Quick Mode template below (verbatim user thought + a Further Investigation section with 2-3 inferred threads).
+4. Use the centralized helper to compute the path, apply the `braindump_` prefix, write the frontmatter (with `variant: aside`), and stay gitignored:
+
+```bash
+echo "$BODY" | node .claude/scripts/capture-context.mjs \
+  --type braindump \
+  --topic {kebab-slug} \
+  --scope team-member \
+  --user {workspace.user} \
+  --variant aside \
+  --local-only
+```
 
-### Quick Mode Template
+5. Report the printed path to the user: "Noted: `{path}`."
 
-```yaml
----
-state: ephemeral
-lifecycle: active
-type: braindump
-variant: aside
-author: {user}
-updated: {YYYY-MM-DD}
----
+The helper handles collisions automatically by appending `-2`, `-3`, etc.
+
+### Quick Mode Body Template
 
+```markdown
 ## User's Original Thought
 {Verbatim text from the user — copy exactly as provided}
 
@@ -47,37 +50,38 @@ related areas to check. Quick inference, not deep research.}
 
 ## Research Mode (default)
 
-Dispatch the `aside-researcher` agent in the background:
-
-1. Parse the user's thought from the arguments (everything after `/aside`)
-2. Generate a kebab-case slug from the content (3-5 words that capture the core idea)
-3. Check if `shared-context/{user}/local-only-{slug}.md` exists. If so, append `-2`, `-3`, etc.
-4. Determine the target file path: `shared-context/{user}/local-only-{slug}.md`
-5. Dispatch the `aside-researcher` agent using the Agent tool:
+Dispatch the `aside-researcher` agent in the background. The full mode uses `--type research` so the file is named `local-only-research_{slug}.md`, distinguishing it from quick asides.
+
+1. Parse the user's thought from the arguments (everything after `/aside`).
+2. Generate a kebab-case slug from the content.
+3. Compute the target path with `--print-only` so you can hand it to the subagent:
+   ```bash
+   node .claude/scripts/capture-context.mjs \
+     --type research \
+     --topic {kebab-slug} \
+     --scope team-member \
+     --user {workspace.user} \
+     --variant aside \
+     --local-only \
+     --print-only
+   ```
+4. Dispatch the `aside-researcher` agent using the Agent tool:
    - `subagent_type`: use the `aside-researcher` agent definition
    - `run_in_background: true`
    - Prompt must include:
      - The user's verbatim thought
-     - The target file path
+     - The target file path (from step 3)
      - The workspace root path
-     - The Research Mode template (below)
-6. Confirm dispatch to the user: "Researching in the background. I'll let you know when it's done."
-7. When the agent completes, report: file path and a one-line summary of what was found
+     - The Research Mode body template (below)
+   - Tell the agent to write the body via `capture-context.mjs --update` so the same path is reused, and to pipe the rendered body on stdin.
+5. Confirm dispatch to the user: "Researching in the background. I'll let you know when it's done."
+6. When the agent completes, report: file path and a one-line summary of what was found.
 
-### Research Mode Template
+### Research Mode Body Template
 
 Include this template in the agent's prompt so it writes the correct format:
 
-```yaml
----
-state: ephemeral
-lifecycle: active
-type: braindump
-variant: aside
-author: {user}
-updated: {YYYY-MM-DD}
----
-
+```markdown
 ## User's Original Thought
 {Verbatim text from the user — copy exactly as provided, never paraphrase}
 
@@ -98,15 +102,16 @@ Topics that would benefit from deeper exploration or user input.}
 
 ## File Naming
 
-- **Location:** `shared-context/{user}/local-only-{slug}.md`
-- **Slug:** Generated from the thought content. Kebab-case, 3-5 words. E.g., `refresh-token-caching`, `deploy-pipeline-idea`
-- **Collision handling:** If the file exists, append `-2`, `-3`, etc.
-- **Always `local-only-`** — gitignored, never auto-committed
+- **Quick mode:** `workspace-context/team-member/{user}/local-only-braindump_{slug}.md`
+- **Research mode:** `workspace-context/team-member/{user}/local-only-research_{slug}.md`
+- **Slug:** Kebab-case, 3-5 words. E.g., `refresh-token-caching`, `deploy-pipeline-idea`.
+- **Collision handling:** Helper auto-appends `-2`, `-3`, …
+- **Always `local-only-`** — gitignored, never auto-committed.
 
 ## Session Behavior
 
 Asides are session-agnostic. Regardless of whether a work session is active:
-- Files always go to `shared-context/{user}/`
+- Files always go to `workspace-context/team-member/{user}/`
 - No interaction with the session tracker
 - No interaction with `/complete-work` synthesis
 

package/template/.claude/skills/braindump/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: braindump
-description: Capture discussion-heavy topics into shared context. Use when reasoning, exploration, or design rationale should be preserved. Accepts optional name parameter.
+description: Capture discussion-heavy topics into workspace-context. Use when reasoning, exploration, or design rationale should be preserved. Accepts optional name parameter.
 ---
 
 # Braindump
 
-Capture discussion reasoning, exploration results, and design rationale into shared context. More freeform than /handoff — designed for "why we chose X" content. User-scoped by default.
+Capture discussion reasoning, exploration results, and design rationale into workspace-context. More freeform than /handoff — designed for "why we chose X" content. Per-user (`team-member/{user}/`) is the default scope.
 
 ## Parameters
 - `/braindump {name}` — create or update a named braindump
@@ -27,25 +27,29 @@ When called within an active work session (the active-session pointer at `.claud
   ```
 
 When called from the workspace root (no active session):
-- Create a `local-only-{name}.md` file (root only allows local-only writes)
+- Use `--local-only` so the captured file is gitignored (the root only allows local-only writes)
 - Suggest starting a work session if the braindump is about actionable work
 
 The flows below apply when NOT in an active work session, or when the user explicitly asks for a standalone braindump file.
 
 ## Flow: Named
 
-Follows the same naming, scoping (user/team/local-only), and commit flow as `/handoff` but with a different file format:
+Use the centralized `capture-context.mjs` helper — it computes the path, applies the `braindump_` prefix, and writes the frontmatter so this skill doesn't have to:
 
-```yaml
----
-state: ephemeral
-lifecycle: active
-type: braindump
-topic: {name}
-author: {user}
-updated: {YYYY-MM-DD}
----
+```bash
+echo "$BODY" | node .claude/scripts/capture-context.mjs \
+  --type braindump \
+  --topic {kebab-case-name} \
+  --scope team-member \
+  --user {workspace.user} \
+  --description "{one-line summary}"
+```
 
+Add `--scope shared` (and drop `--user`) to put the file in `workspace-context/shared/` for team visibility. Add `--local-only` to keep it gitignored. Add `--update` to overwrite an existing file with the same name; without it, the helper appends `-2`, `-3`, etc. on collision.
+
+The body content sent on stdin should follow this template:
+
+```markdown
 ## Context
 {What prompted this discussion}
 
@@ -59,6 +63,8 @@ updated: {YYYY-MM-DD}
 {What this decision means for future work}
 ```
 
+The helper writes the frontmatter (`state: ephemeral`, `lifecycle: active`, `type: braindump`, `topic`, `author`, `updated`) and prints the absolute path on stdout so the skill can `git add` and commit it.
+
 ## Flow: Side Braindump (deprecated)
 
 `/braindump side` has been replaced by the `/aside` skill. If invoked:
@@ -74,7 +80,7 @@ updated: {YYYY-MM-DD}
 
 ## Include task snapshot
 
-If an active session exists (detected via `.claude/.active-session.json`), include a `## Tasks at capture time` section in the braindump artifact with a snapshot of the current `TodoWrite` state:
+If an active session exists (detected via `.claude/.active-session.json`), include a `## Tasks at capture time` section in the braindump body before piping it to `capture-context.mjs`:
 
 ```markdown
 ## Tasks at capture time
@@ -85,11 +91,11 @@ If an active session exists (detected via `.claude/.active-session.json`), inclu
 - [ ] Complete work
 ```
 
-Use the same GFM checkbox format as `session.md`'s `## Tasks` section (just `content` and `status` per task — no `activeForm` field, no blockquote line) and render it inline in the braindump. Do NOT call `sync-tasks.mjs --write` — braindumps are snapshots, not the canonical store.
+Use the same GFM checkbox format as `session.md`'s `## Tasks` section (just `content` and `status` per task — no `activeForm` field, no blockquote line). Do NOT call `sync-tasks.mjs --write` — braindumps are snapshots, not the canonical store.
 
 ## Updating Existing Braindumps
 
-When updating, rewrite as a fresh snapshot (coherent-revisions rule). The updated braindump should read as if written in one pass.
+When updating, rewrite as a fresh snapshot (coherent-revisions rule) and pass `--update` to `capture-context.mjs`. The updated braindump should read as if written in one pass.
 
 ## Key Differences from /handoff
 - `/handoff` is structured around work state (branch, status, next steps)
@@ -98,14 +104,14 @@ When updating, rewrite as a fresh snapshot (coherent-revisions rule). The update
 - Use `/braindump` when you're capturing a discussion or decision
 
 ## Auto-commit
-Same as `/handoff` — commit the file alone:
+Use the path that `capture-context.mjs` printed:
 ```bash
-git add shared-context/{path-to-file}
+git add {printed-path}
 git commit -m "braindump: {name}"
 ```
 
 ## Notes
-- User-scoped is the default
+- Per-user (`team-member/{user}/`) is the default scope
 - One topic, one file — don't mix unrelated ideas in one braindump
 - Drive-by ideas now use `/aside` instead of `/braindump side`
 - Auto-committing context files without user request is a workflow artifact — this intentionally bypasses the "do not commit unless asked" convention

package/template/.claude/skills/build-docs-site/SKILL.md

@@ -96,7 +96,7 @@ For the codebase:
 - Read actual implementations, not just existing docs about them
 
 For shared context:
-- Walk `shared-context/` for handoffs, braindumps, locked team knowledge, release notes
+- Walk `workspace-context/` for handoffs, braindumps, locked team knowledge, release notes
 
 For work-session history:
 - Walk `work-sessions/*/workspace/session.md` for any currently-active session trackers — their bodies may contain decisions not yet consumed into release notes

package/template/.claude/skills/build-docs-site/checklists/framing.md

@@ -52,7 +52,7 @@ For each selected option, **ask for specific paths**.
 
 > What other sources should I pull from?
 >
-> - Shared context files in the workspace
+> - Workspace-context files in the workspace
 > - Claude chat history from prior sessions on this project
 > - Notion export (zip)
 > - Confluence / wiki export

package/template/.claude/skills/complete-work/SKILL.md

@@ -60,9 +60,9 @@ Formally read ALL sources before synthesizing — do not write release notes fro
    - `work-sessions/{session-name}/workspace/plan-*.md` files
    - Read each one fully
 
-3. **Handoffs** — any shared-context entries referencing this branch:
+3. **Handoffs** — any workspace-context entries referencing this branch:
    ```bash
-   grep -rl "branch: {branch}" shared-context/
+   grep -rl "branch: {branch}" workspace-context/
    ```
    Read each matching file.
 
@@ -349,7 +349,7 @@ If /complete-work is called but changes were made without a formal work session
 Ask: "These changes weren't part of a formal work session. What do you want to do?"
 - **Accept as work** — create a session retroactively, proceed with normal completion
 - **Stash for later** — create a user-scoped handoff describing what was done, stash the changes
-- **Hand off to someone** — create a team-visible handoff at root shared-context/ for another member to pick up
+- **Hand off to someone** — create a team-visible handoff at root workspace-context/ for another member to pick up
 - **Revert** — undo the changes (with confirmation)
 
 ## Notes

package/template/.claude/skills/handoff/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: handoff
-description: Save workstream state as shared context. Use anytime during work to capture progress, decisions, and next steps. Accepts optional name parameter.
+description: Save workstream state as workspace-context. Use anytime during work to capture progress, decisions, and next steps. Accepts optional name parameter.
 ---
 
 # Handoff
 
-Save structured workstream state to shared context. Usable anytime, any number of times. User-scoped by default.
+Save structured workstream state to workspace-context. Usable anytime, any number of times. Per-user (`team-member/{user}/`) is the default scope.
 
 ## Parameters
 - `/handoff {name}` — create or update a named handoff
@@ -28,34 +28,33 @@ When called within an active work session (the active-session pointer at `.claud
 
 When called from the workspace root (no active session):
 - Only `local-only-*` files are writable from the root
-- Suggest starting a work session first, or create a `local-only-{name}.md` file
+- Suggest starting a work session first, or use the helper with `--local-only`
 
 The flows below apply when NOT in an active work session, or when the user explicitly asks for a standalone handoff file.
 
 ## Flow: Named
 
 1. Read workspace user identity from `.claude/settings.local.json` (`workspace.user`)
-2. Check if handoff already exists in `shared-context/{user}/` or `shared-context/` root
-3. If exists: read it, prepare to update with current session state
-4. If new: prepare to create
-5. Ask: "Should this be user-scoped (default), team-visible, or local-only?"
-   - User-scoped (default): `shared-context/{user}/{name}.md`
-   - Team-visible: `shared-context/{name}.md`
-   - Local-only: `shared-context/local-only-{name}.md`
-6. Write the handoff file:
-
-```yaml
----
-state: ephemeral
-lifecycle: active
-type: handoff
-topic: {name}
-branch: {current-branch-if-any}
-repo: {current-repo-if-any}
-author: {user}
-updated: {YYYY-MM-DD}
----
+2. Ask: "Should this be user-scoped (default), team-visible, or local-only?"
+   - User-scoped (default): `--scope team-member --user {user}`
+   - Team-visible: `--scope shared`
+   - Local-only: add `--local-only` to either scope
+3. Use the centralized helper to compute the path, apply the `handoff_` prefix, and write the file with full frontmatter:
+
+```bash
+echo "$BODY" | node .claude/scripts/capture-context.mjs \
+  --type handoff \
+  --topic {kebab-case-name} \
+  --scope team-member \
+  --user {workspace.user} \
+  --description "{one-line summary}"
+```
+
+Pass `--update` to overwrite an existing handoff with the same name (otherwise the helper appends `-2`, `-3`, … to avoid clobbering). The helper prints the absolute path of the written file on stdout — use that path for the commit step.
 
+The body content sent on stdin should follow this template:
+
+```markdown
 ## Status
 {What was accomplished in this session}
 
@@ -69,9 +68,11 @@ updated: {YYYY-MM-DD}
 {Unresolved questions, if any}
 ```
 
-7. Auto-commit the handoff file alone:
+The helper writes the frontmatter (`state: ephemeral`, `lifecycle: active`, `type: handoff`, `topic`, `author`, `updated`). If you need extra fields like `branch:` or `repo:`, append them to the frontmatter after the helper writes (or include them inline in the body).
+
+4. Auto-commit the handoff file alone:
    ```bash
-   git add shared-context/{path-to-file}
+   git add {printed-path}
    git commit -m "handoff: {name}"
    ```
 
@@ -86,7 +87,7 @@ updated: {YYYY-MM-DD}
 
 ## Include task snapshot
 
-If an active session exists (detected via `.claude/.active-session.json`), include a `## Tasks at capture time` section in the handoff artifact with a snapshot of the current `TodoWrite` state:
+If an active session exists (detected via `.claude/.active-session.json`), include a `## Tasks at capture time` section in the handoff body before piping it to `capture-context.mjs`:
 
 ```markdown
 ## Tasks at capture time
@@ -97,16 +98,16 @@ If an active session exists (detected via `.claude/.active-session.json`), inclu
 - [ ] Complete work
 ```
 
-Use the same GFM checkbox format as `session.md`'s `## Tasks` section (just `content` and `status` per task — no `activeForm` field, no blockquote line) and render it inline in the handoff. Do NOT call `sync-tasks.mjs --write` — handoffs are snapshots, not the canonical store.
+Use the same GFM checkbox format as `session.md`'s `## Tasks` section (just `content` and `status` per task — no `activeForm` field, no blockquote line). Do NOT call `sync-tasks.mjs --write` — handoffs are snapshots, not the canonical store.
 
 ## Updating Existing Handoffs
 
-When updating an existing handoff, rewrite it as a fresh snapshot of current understanding (coherent-revisions rule). Don't append below the old content. The updated handoff should read as if written in one pass reflecting the current state.
+When updating an existing handoff, rewrite it as a fresh snapshot of current understanding (coherent-revisions rule) and pass `--update` to `capture-context.mjs`. Don't append below the old content. The updated handoff should read as if written in one pass reflecting the current state.
 
-Update the `updated` date in frontmatter. Keep the `lifecycle` as-is unless the user indicates a change.
+The helper updates the `updated` date in frontmatter automatically.
 
 ## Notes
-- User-scoped is the default — root is only for content deliberately made team-visible
+- Per-user is the default — `--scope shared` is for content deliberately made team-visible
 - Handoffs are always committed individually — never bundled with code commits
 - One topic, one file — don't let handoffs become grab-bags
 - Name before writing — the name forces you to identify the single topic

package/template/.claude/skills/maintenance/SKILL.md

@@ -17,13 +17,13 @@ Keep the workspace healthy. Combines integrity auditing with active cleanup reco
 Read-only integrity checks. Reports problems but never modifies files.
 
 ### 1. Cross-reference consistency
-Scan all shared-context files against each other:
+Scan all workspace-context files against each other:
 - **Stale references** — file A mentions "2 mandatory rules" but there are now 4
 - **Path references** — file A mentions a file that was moved or deleted
 - **Contradictions** — file A says "user-scoped is default" but file B says "root is default"
 
 ### 2. Frontmatter integrity
-For each shared-context `.md` file and each `work-sessions/*/workspace/session.md`:
+For each workspace-context `.md` file and each `work-sessions/*/workspace/session.md`:
 - Valid frontmatter? (state, lifecycle, type, topic, author, updated; plus name/status/branch/repos for session trackers)
 - `branch` field references a branch that still exists?
 - `repo`/`repos` field references repos that exist in workspace.json?
@@ -45,23 +45,23 @@ For each shared-context `.md` file and each `work-sessions/*/workspace/session.m
 - Workspace repo on expected branch?
 - Orphan worktree records in project repos — run `git -C repos/{repo} worktree list` for each repo and flag any `prunable` markers. These usually come from a workspace-first teardown (the unsafe order) leaving stale admin records behind. Suggest `git worktree prune` on the affected repo.
 
-### 5. Shared-context index integrity
+### 5. Workspace-context auto-file integrity
 
-`shared-context/index.md` is auto-generated from frontmatter. Run the check:
+`workspace-context/index.md`, `workspace-context/canonical.md`, and each `workspace-context/team-member/{user}/index.md` are auto-generated from frontmatter and locked content. Run the check:
 
 ```bash
-node .claude/scripts/build-shared-context-index.mjs --check --root .
+node .claude/scripts/build-workspace-context.mjs --check --root .
 ```
 
-Three failure modes (script exits 1 with a JSON status):
+The script exits 1 if any of the three artifact types is missing or stale, and reports per-file status as JSON:
 
-- `missing` — `shared-context/` exists but `index.md` does not. Run `--write` to create.
-- `stale` — `index.md` exists but its entries no longer match the filesystem. Causes: a file was added or deleted, a `description:` was changed, a `.indexignore` rule was added. Run `--write` to regenerate.
-- (no failure) — `current` with the entry count.
+- `missing` — `workspace-context/` exists but the artifact does not. Run `--write` to create.
+- `stale` — the artifact exists but no longer matches the filesystem. Causes: a file was added or deleted, a `description:` was changed, a `shared/locked/` file was edited, an `.indexignore` rule was added. Run `--write` to regenerate.
+- `current` — everything matches.
 
 Audit mode reports the status. Cleanup mode runs `--write` if stale or missing, then re-checks.
 
-While the index is being read, also flag entries with weak fallbacks: filename-slug-only descriptions (e.g., "project status" with no period) usually indicate the underlying file is missing a `description:` or has no usable opening sentence. Suggest adding `description:` to those source files — the index will pick it up on the next regeneration.
+While the indexes are being read, also flag entries with weak fallbacks: filename-slug-only descriptions (e.g., "project status" with no period) usually indicate the underlying file is missing a `description:` or has no usable opening sentence. Suggest adding `description:` to those source files — the index will pick it up on the next regeneration.
 
 ### 6. Template freshness
 
@@ -96,13 +96,13 @@ Active recommendations. Flags problems and suggests fixes, but asks before actin
 - Handoffs referencing deleted branches — suggest resolve or remove
 
 ### 8. Context reconciliation
-- Read recent shared-context writes (last session or last N files by updated date)
-- For each, scan other shared-context files for references that are now stale
+- Read recent workspace-context writes (last session or last N files by updated date)
+- For each, scan other workspace-context files for references that are now stale
 - Surface: "{file} says X but {newer-file} now says Y. Update {file}?"
 - This is the capture-time cross-check, run retroactively instead of inline
 
 ### 9. Health metrics
-- Size of `shared-context/locked/` relative to the active model's context window — flag if over 5% (yellow) or 15% (red). Absolute byte count is a weak proxy; contradictions, stale references, and duplicated coverage across files matter more than total size.
+- Size of `workspace-context/shared/locked/` relative to the active model's context window — flag if over 5% (yellow) or 15% (red). Absolute byte count is a weak proxy; contradictions, stale references, and duplicated coverage across files matter more than total size.
 - Number of ephemeral files — flag if accumulating without resolution
 - Session log stats (if `workspace-scratchpad/session-log.jsonl` exists):
   - Sessions without capture
@@ -115,13 +115,13 @@ Active recommendations. Flags problems and suggests fixes, but asks before actin
 /maintenance results:
 
 Issues (3):
-  ✗ shared-context/alice/old-handoff.md references branch feature/old
+  ✗ workspace-context/team-member/alice/old-handoff.md references branch feature/old
     but that branch was deleted
   ✗ 2 inflight files exist but no active work session (orphaned?)
   ✗ Locked context is 18% of model context window (red threshold: 15%)
 
 Warnings (2):
-  ⚠ shared-context/alice/workspace-analytics.md not updated in 8 days
+  ⚠ workspace-context/team-member/alice/workspace-analytics.md not updated in 8 days
   ⚠ Worktree work-sessions/old-feature/workspace has no commits in 5 days
 
 Cleanup suggestions (2):
@@ -140,14 +140,14 @@ OK (5):
 
 ## Flow
 
-1. Scan shared-context/ recursively — read all `.md` files and their frontmatter
+1. Scan workspace-context/ recursively — read all `.md` files and their frontmatter
 2. Read CLAUDE.md — extract skill and rule references
 3. Read workspace.json — extract repo manifest
 4. Check `.claude/rules/`, `.claude/skills/`, `.claude/agents/` against references
 5. Check git state (worktrees, branches, remotes)
-6. Run `node .claude/scripts/build-shared-context-index.mjs --check --root .` — capture status
+6. Run `node .claude/scripts/build-workspace-context.mjs --check --root .` — capture status
 7. Read session-log.jsonl if it exists
-8. If cleanup mode: regenerate the shared-context index if stale; compare files pairwise for overlap; scan for stale cross-references
+8. If cleanup mode: regenerate the workspace-context auto-files if stale (index.md, canonical.md, per-user team-member indexes); compare files pairwise for overlap; scan for stale cross-references
 9. Compile and present findings grouped by severity
 
 ## Notes

package/template/.claude/skills/pause-work/SKILL.md

@@ -113,7 +113,7 @@ If PRs already exist, update them to draft status if needed.
 No worktree cleanup — the session is meant to be resumed. The `work-sessions/{session-name}/` folder stays intact.
 
 ## Notes
-- Pause writes ONLY to `work-sessions/{session-name}/workspace/session.md` — never to ongoing or root shared-context
+- Pause writes ONLY to `work-sessions/{session-name}/workspace/session.md` — never to ongoing or root workspace-context
 - The session tracker's frontmatter stays in the session folder — it's the resume mechanism
 - Draft PRs signal work-in-progress without implying merge readiness
 - Auto-committing the pause capture is a workflow artifact — this intentionally bypasses normal commit conventions

package/template/.claude/skills/promote/SKILL.md

@@ -1,17 +1,17 @@
 ---
 name: promote
-description: Move personal auto-memory or local-only files into shared context. Use when you've discovered something valuable that the team should know.
+description: Move personal auto-memory or local-only files into workspace-context. Use when you've discovered something valuable that the team should know.
 ---
 
 # Promote
 
-Promote personal knowledge into shared context. Assess all candidates, recommend actions, let the user decide with coded references.
+Promote personal knowledge into workspace-context. Assess all candidates, recommend actions, let the user decide with coded references.
 
 ## Sources
 
 This skill can promote from three sources:
 1. **Auto-memory (AM)** — files in `~/.claude/projects/*/memory/`
-2. **Local-only context (LOC)** — `shared-context/local-only-*.md`
+2. **Local-only context (LOC)** — `workspace-context/team-member/{user}/local-only-*.md` (and any other `local-only-*.md` under `workspace-context/`)
 3. **Local-only rules (LOR)** — `.claude/rules/local-only-*.md`
 
 ## Flow
@@ -47,9 +47,19 @@ The user responds using codes:
 **Step 3: Execute decisions**
 
 For each **promote** action:
-- Ask: "Team-visible, user-scoped (default), or locked?"
-- Copy to destination, set `type: promoted` in frontmatter
-- Remove the local-only original
+- Ask: "Team-visible (`workspace-context/shared/`), user-scoped (default, `workspace-context/team-member/{user}/`), or locked (`workspace-context/shared/locked/`)?"
+- Use `capture-context.mjs --update` to write to the destination with the right frontmatter:
+  ```bash
+  cat {source-file} | node .claude/scripts/capture-context.mjs \
+    --type {braindump|handoff|research} \
+    --topic {kebab-name} \
+    --scope {team-member|shared} \
+    [--user {workspace.user}] \
+    --update
+  ```
+  When promoting *to locked*, write directly to `workspace-context/shared/locked/{bare-name}.md` instead — locked files use bare names (location signals the type) and don't take a prefix. Strip the `braindump_/handoff_/research_` prefix when locking.
+- Set `type: promoted` in the destination frontmatter (the helper writes the standard fields; edit `type` afterward, or have the body's frontmatter override).
+- Remove the `local-only-` original.
 - Commit individually: `git commit -m "promote: {name}"`
 
 For each **drop** action:
@@ -65,13 +75,13 @@ For each **keep** action:
 
 ## Rewrite on Promote
 
-Auto-memory files are terse notes written for Claude's internal use. When promoting to shared context, rewrite into proper format with:
+Auto-memory files are terse notes written for Claude's internal use. When promoting to workspace-context, rewrite into proper format with:
 - Frontmatter (state, lifecycle, type: promoted, topic, author, updated)
 - Sections with enough context to be useful to someone who wasn't in the original session
 - Local-only files may already be well-formatted — copy as-is if so, just update frontmatter
 
 ## Notes
-- Promotion is one-way: shared context should not be demoted back to local-only
+- Promotion is one-way: workspace-context should not be demoted back to local-only
 - Use this when you discover a pattern, convention, or decision that would benefit the team
 - The coded table makes bulk decisions fast — no need to type full filenames
 - Assess everything upfront so the user sees the full picture before deciding

package/template/.claude/skills/release/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: release
-description: Prepend a new CHANGELOG.md entry per project repo by synthesizing unreleased branch notes. Deletes consumed branch notes and synthesizes workspace shared-context into locked entries. Use at release time.
+description: Prepend a new CHANGELOG.md entry per project repo by synthesizing unreleased branch notes. Deletes consumed branch notes and synthesizes workspace-context into canonical (locked) entries. Use at release time.
 ---
 
 # Release
 
-Synthesize unreleased branch notes (in the **workspace** repo) into a concise, user-facing entry at the top of each project repo's `CHANGELOG.md`. Delete the consumed branch notes from the workspace. Bump the project repo's `package.json` version. In parallel, promote resolved workspace shared-context into locked team knowledge.
+Synthesize unreleased branch notes (in the **workspace** repo) into a concise, user-facing entry at the top of each project repo's `CHANGELOG.md`. Delete the consumed branch notes from the workspace. Bump the project repo's `package.json` version. In parallel, promote resolved workspace-context into canonical (locked) team knowledge.
 
 ## Why this shape
 
@@ -104,28 +104,32 @@ git commit -m "release: consume {repo} branch notes for v{version}"
 Workspace and project repos have separate commits — they are separate git histories.
 
 **Step 8: Consume project-scoped specs**
-Project-scoped specs and plans in `shared-context/{user}/` (ongoing) that are fully covered by this release:
+Project-scoped specs and plans in `workspace-context/team-member/{user}/` (ongoing) that are fully covered by this release:
 - Consume into the CHANGELOG entry (their content is now captured there)
 - Remove the source files
 - If partially covered: rewrite the spec to reflect only what remains unimplemented
 
-**Step 9: Synthesize workspace shared context**
-Process ephemeral shared-context entries:
+**Step 9: Synthesize workspace-context for canonical promotion**
+Process ephemeral workspace-context entries:
 
-1. List all ephemeral entries with `lifecycle: resolved`
+1. List all ephemeral entries with `lifecycle: resolved` (across `shared/` and any `team-member/{user}/`).
 2. For each, determine:
    - Does an existing locked entry cover this topic? → Merge into it (enrich)
    - Are there related resolved entries? → Combine into a new locked entry
    - Is it stale/fully consumed by release notes? → Archive or delete
-   - Is it unresolvable but still valuable? → Move to `{user}/` ongoing or keep as root ephemeral
+   - Is it unresolvable but still valuable? → Move to `team-member/{user}/` ongoing or keep at `shared/` root ephemeral
 3. For merged/new locked entries:
-   - Set `state: locked`, `type: synthesized`
-   - Move to `shared-context/locked/`
+   - Set `state: locked`, `type: synthesized` (or `type: reference` for clean truths)
+   - Write to `workspace-context/shared/locked/{bare-name}.md` — locked files use bare names (location signals the type), so strip any `braindump_/handoff_/research_` prefix when promoting
    - Write concise, focused content — team truths, not session history
-4. Commit:
+4. Regenerate auto-files so `canonical.md` and `index.md` reflect the new locked content:
    ```bash
-   git add shared-context/
-   git commit -m "release: synthesize shared context for v{version}"
+   node .claude/scripts/build-workspace-context.mjs --write --root .
+   ```
+5. Commit:
+   ```bash
+   git add workspace-context/
+   git commit -m "release: synthesize workspace-context for v{version}"
    ```
 
 **Step 10: Report**
@@ -137,6 +141,6 @@ Process ephemeral shared-context entries:
 - Branch notes live in the WORKSPACE at `release-notes/unreleased/{repo}/`. `/complete-work` writes them; `/release` consumes and deletes them. They never reach project repos.
 - Versions are bumped here, not in `/complete-work`. This keeps the version semantics aligned with what actually shipped (accumulated changes since last release).
 - The public repo stays lean. Detailed per-branch retrospection exists in workspace git history (the consumed-notes commit) but is not surfaced as standalone files in either repo.
-- Context synthesis happens in the WORKSPACE repo — Step 7c (consumed-notes) and Step 9 (shared-context synthesis) are separate workspace commits.
+- Context synthesis happens in the WORKSPACE repo — Step 7c (consumed-notes) and Step 9 (workspace-context synthesis) are separate workspace commits.
 - Per-repo is the default — each project repo has its own release cadence.
 - The coherent-revisions rule applies: write the CHANGELOG entry from scratch, don't concatenate branch notes.