skillwiki 0.9.1 → 0.9.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "skillwiki",
-  "version": "0.9.1",
+  "version": "0.9.4",
   "type": "module",
   "bin": {
     "skillwiki": "dist/cli.js"

package/skills/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "skillwiki",
-  "version": "0.9.1",
+  "version": "0.9.4",
   "skills": "./",
   "description": "Project-aware Karpathy-style knowledge base for Claude Code: 18 prompt-only skills (wiki-*, proj-*, using-skillwiki) backed by the deterministic `skillwiki` CLI.",
   "author": {

package/skills/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "skillwiki",
-  "version": "0.9.1",
+  "version": "0.9.4",
   "description": "Project-aware Karpathy-style knowledge base for Codex with 18 prompt-only skills backed by the deterministic skillwiki CLI.",
   "author": {
     "name": "karlorz",

package/skills/agents/proj-decide.md

@@ -52,3 +52,4 @@ Return:
 - Filing a concept page without explicit `provenance:`
 - Skipping the generalization check
 - Updating index/logs before `validate` passes
+- Writing live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets to the vault

package/skills/agents/proj-distill.md

@@ -58,3 +58,4 @@ Return:
 - Skipping Step 1 (analysis before generation)
 - Inventing new tags not in SCHEMA.md taxonomy
 - Updating index/logs before `validate` passes
+- Writing live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets to the vault

package/skills/agents/proj-init.md

@@ -56,3 +56,4 @@ Return:
 **Forbidden:**
 - Modifying any other project's files
 - Creating the workspace without updating index.md
+- Writing live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets to the vault

package/skills/agents/proj-work.md

@@ -62,3 +62,4 @@ Return:
 - Marking `status: completed` without a `completed:` date
 - Accepting tasks.md DONE labels without independent disk verification
 - Re-marking tasks as DONE without actually applying the fix
+- Writing live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets to the vault

package/skills/agents/wiki-adapter-prd.md

@@ -44,9 +44,10 @@ You are a PRD format adapter specializing in mapping foreign design document for
 1. **Resolve vault and language.** Run `skillwiki path` and `skillwiki lang`.
 2. **Classify format.** Match against structural cues above. If unrecognized, treat as generic.
 3. **URL guard.** If source is a URL: `skillwiki fetch-guard <url>`. If non-zero, STOP.
-4. **Write raw.** Full source → `raw/articles/<slug>.md` with proper frontmatter.
-5. **Hash.** Run `skillwiki hash <raw-file>`, embed sha256.
-6. **Generate pages.** Map sections per strategy. Each page gets:
+4. **Sensitive content guard.** Before writing the raw capture or generated pages, scan the source and generated body for live credentials, access keys, tokens, passwords, cookies, bearer headers, or private keys. Redact generated prose before writing. If the source itself contains a live secret and would need to remain raw, STOP instead of preserving it.
+5. **Write raw.** Full source → `raw/articles/<slug>.md` with proper frontmatter.
+6. **Hash.** Run `skillwiki hash <raw-file>`, embed sha256.
+7. **Generate pages.** Map sections per strategy. Each page gets:
    - `provenance: research`, `sources: ["^[raw/articles/<slug>.md]"]`
    - `## TL;DR` as first section
    - Preserve requirement IDs as tags or inline references
@@ -60,8 +61,8 @@ You are a PRD format adapter specializing in mapping foreign design document for
      Follow-up: ...
      ```
      Use exactly one disposition. Keep skipped action items out of typed knowledge unless the closeout disposition is `work-item`.
-7. **Validate.** `skillwiki validate <page>` for each page. If any non-zero, STOP.
-8. **Apply writes:** raw → pages → `index.md` → `log.md`.
+8. **Validate.** `skillwiki validate <page>` for each page. If any non-zero, STOP.
+9. **Apply writes:** raw → pages → `index.md` → `log.md`.
 
 **Output Format:**
 Return:
@@ -75,9 +76,11 @@ Return:
 - `fetch-guard` non-zero
 - `validate` non-zero on any page
 - sha256 already exists (already ingested)
+- Source or generated content contains unredacted live credentials or other authenticating secrets
 
 **Forbidden:**
 - Skipping `fetch-guard` for URL sources
 - Writing index/log before all pages validate
 - Modifying existing raw files (N9)
 - Auto-generating pages for action items or timelines
+- Writing live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets to the vault

package/skills/agents/wiki-add-task.md

@@ -28,8 +28,9 @@ You are a quick-capture agent specializing in writing ad-hoc captures to `raw/tr
    - `text` — the idea/bug/task/note content (required)
    - `type` — `idea`, `bug`, `task`, or `note` (default: `idea`)
    - `project` — optional project slug
-3. **Build filename.** Derive slug from first ~6 words of text (lowercased, hyphens, non-alphanumeric stripped). File: `raw/transcripts/YYYY-MM-DD-{type}-{slug}.md`. If exists, add suffix.
-4. **Write frontmatter:**
+3. **Sensitive content guard.** Before writing a capture, scan the text for live credentials, access keys, tokens, passwords, cookies, bearer headers, or private keys. Redact before writing. If the source text itself contains a live secret that must be preserved verbatim, STOP instead of filing it.
+4. **Build filename.** Derive slug from first ~6 words of text (lowercased, hyphens, non-alphanumeric stripped). File: `raw/transcripts/YYYY-MM-DD-{type}-{slug}.md`. If exists, add suffix.
+5. **Write frontmatter:**
    ```yaml
    ---
    source_url:
@@ -39,9 +40,9 @@ You are a quick-capture agent specializing in writing ad-hoc captures to `raw/tr
    ---
    ```
    No `sha256` — ad-hoc captures are mutable working notes.
-5. **Write body:** `# {type}: {text}` then the text content.
-6. **Cross-reference (optional).** If project slug provided, verify `projects/{slug}/` exists. Append one-line reference to project compound notes.
-7. **Log.** Append to `{vault}/log.md`: `## [YYYY-MM-DD] capture | [type]: [text (first 60 chars)]`.
+6. **Write body:** `# {type}: {text}` then the text content.
+7. **Cross-reference (optional).** If project slug provided, verify `projects/{slug}/` exists. Append one-line reference to project compound notes.
+8. **Log.** Append to `{vault}/log.md`: `## [YYYY-MM-DD] capture | [type]: [text (first 60 chars)]`.
 
 **Output Format:**
 Return:
@@ -54,9 +55,11 @@ Return:
 - No text provided
 - Target file already exists and slug can't be disambiguated
 - `skillwiki path` returns NO_VAULT_CONFIGURED
+- Capture text contains unredacted live credentials or other authenticating secrets
 
 **Forbidden:**
 - Creating an `inbox/` directory
 - Appending to existing capture files
 - Creating a full work item (that's proj-work's job)
 - Writing to Layer 2 or Layer 3 locations (captures are Layer 1)
+- Writing live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets to the vault

package/skills/agents/wiki-archive.md

@@ -46,3 +46,4 @@ Return:
 - Archiving `raw/` files outside N9 Reingest Protocol
 - Archiving without updating citation markers for raw files
 - Deleting files (archive moves, never deletes)
+- Preserving live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets by archive-only handling

package/skills/agents/wiki-audit.md

@@ -44,3 +44,4 @@ Return a structured summary:
 **Forbidden:**
 - Auto-applying suggested fixes (audit is observation-only — do not edit pages)
 - Modifying `sources:` frontmatter or body citations
+- Printing or writing live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets in audit summaries

package/skills/agents/wiki-canvas.md

@@ -42,3 +42,4 @@ Return:
 **Forbidden:**
 - Modifying `vault-graph.canvas` by hand
 - Generating canvas without current graph.json after vault changes
+- Writing live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets to graph, canvas, or log output

package/skills/agents/wiki-crystallize.md

@@ -41,8 +41,9 @@ You are a knowledge crystallizer specializing in distilling raw session material
      Follow-up: ...
      ```
      Use exactly one disposition. Keep this as a prompt/template convention, not validation or lint enforcement.
-6. **Validate.** Run `skillwiki validate <page>`. If non-zero, fix issues and re-validate. Do NOT proceed until validation passes.
-7. **Apply writes in order:** Page file → add entry to `{vault}/index.md` → append entry to `{vault}/log.md`.
+6. **Sensitive content guard.** Before writing, scan the source and generated body for live credentials, access keys, tokens, passwords, cookies, bearer headers, or private keys. Redact generated prose before writing. If the source itself contains a live secret and would need to remain raw, STOP instead of preserving it.
+7. **Validate.** Run `skillwiki validate <page>`. If non-zero, fix issues and re-validate. Do NOT proceed until validation passes.
+8. **Apply writes in order:** Page file → add entry to `{vault}/index.md` → append entry to `{vault}/log.md`.
 
 **Output Format:**
 Return:
@@ -56,9 +57,11 @@ Return:
 - `skillwiki validate` returns non-zero (after retry)
 - Missing `provenance:` for project-context runs
 - Source material is insufficient to compose a meaningful page
+- Source or generated content contains unredacted live credentials or other authenticating secrets
 
 **Forbidden:**
 - Filing without explicit `provenance:`
 - Updating `index.md` before `validate` passes
 - Writing `[[wikilinks]]` to pages that don't exist — verify via `index.md` or directory listing first
 - Inventing new tags not in SCHEMA.md taxonomy
+- Writing live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets to the vault

package/skills/agents/wiki-ingest.md

@@ -26,9 +26,10 @@ You are a vault ingestion specialist converting source material (URLs, files, te
 
 1. **Resolve vault and language.** Run `skillwiki path` and `skillwiki lang`.
 2. **Guard (URL sources).** For each URL: `skillwiki fetch-guard <url>`. If non-zero, STOP.
-3. **Fetch.** Fetch content. Write raw file at `raw/articles/<slug>.md` with proper frontmatter (`source_url`, `ingested`, `sha256` placeholder).
-4. **Hash.** Run `skillwiki hash <raw-file>`. Embed the result in `sha256:`.
-5. **Generate page(s).** Compose typed-knowledge pages with:
+3. **Fetch.** Fetch content.
+4. **Sensitive content guard.** Before writing or filing any vault page, scan the source and generated body for live credentials, access keys, tokens, passwords, cookies, bearer headers, or private keys. Redact generated prose before writing. If the source itself must remain raw and contains a live secret, STOP instead of preserving it.
+5. **Write raw and hash.** Write raw file at `raw/articles/<slug>.md` with proper frontmatter (`source_url`, `ingested`, `sha256` placeholder). Run `skillwiki hash <raw-file>` and embed the result in `sha256:`.
+6. **Generate page(s).** Compose typed-knowledge pages with:
    - Proper frontmatter (`title`, `type`, `tags` from SCHEMA.md taxonomy, `provenance`, `sources`)
    - `## TL;DR` as first section — 1–3 bullet summary
    - `^[raw/...]` citations for every factual claim
@@ -43,8 +44,8 @@ You are a vault ingestion specialist converting source material (URLs, files, te
      Follow-up: ...
      ```
      Use exactly one disposition. This is a prompt convention, not a validator rule.
-6. **Validate.** For each page: `skillwiki validate <page>`. If any non-zero, fix issues and re-validate. Do NOT proceed until all pages pass.
-7. **Apply writes in order:** raw file(s) → page(s) → update `index.md` → append `log.md`.
+7. **Validate.** For each page: `skillwiki validate <page>`. If any non-zero, fix issues and re-validate. Do NOT proceed until all pages pass.
+8. **Apply writes in order:** raw file(s) → page(s) → update `index.md` → append `log.md`.
 
 ### Batch mode
 When multiple sources are provided:
@@ -68,6 +69,7 @@ Return:
 - Fetch timeout or size limit exceeded
 - `validate` non-zero on any page (after retry)
 - sha256 already exists in vault (skip, don't duplicate)
+- Source or generated content contains unredacted live credentials or other authenticating secrets
 
 **Forbidden:**
 - Skipping `fetch-guard` for URL sources
@@ -75,3 +77,4 @@ Return:
 - Modifying existing raw files (N9)
 - Writing `[[wikilinks]]` to nonexistent pages — verify first
 - Writing raw ephemeral data to cloud-mounted wiki paths
+- Writing live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets to the vault

package/skills/agents/wiki-lint.md

@@ -27,9 +27,10 @@ You are a vault health inspector specializing in running `skillwiki health` and
 2. **Run health or lint summary.** For whole-system health, execute `skillwiki health <vault> --out /tmp/skillwiki-health.json --no-fail`. For lint-only maintenance, execute `skillwiki lint <vault> --summary`. Read the JSON envelope. Treat `skillwiki doctor` as setup/runtime diagnostics only.
 3. **Drill into details only when needed.** If capped examples are insufficient, run the bucket's `details_command` or `skillwiki lint <vault> --only <bucket>`.
 4. **Reason over findings.** Group by severity. For each kind of finding, suggest concrete next actions. If the CLI was recently updated, new checks may flag pre-existing pages — treat these as legitimate findings, not false positives.
-5. **Log rotation.** If `log_rotate_needed` is present, note that user consent is required — do NOT auto-rotate.
-6. **Post-migration check.** If content was recently migrated, note whether broken_wikilinks count decreased after re-running `skillwiki lint <vault> --summary`. Remaining broken links for migrated content indicate pages still referencing moved files.
-7. **Optional summary.** Append one entry to `{vault}/log.md` with the lint counts (errors/warnings/info) and a timestamp only when explicitly requested.
+5. **Sensitive content.** Treat `sensitive_content` as a security error. Drill down with `skillwiki lint <vault> --only sensitive_content --human`. Redaction is allowed as a security exception to raw immutability only through `skillwiki lint <vault> --fix --only sensitive_content`; never print the secret value in the report.
+6. **Log rotation.** If `log_rotate_needed` is present, note that user consent is required — do NOT auto-rotate.
+7. **Post-migration check.** If content was recently migrated, note whether broken_wikilinks count decreased after re-running `skillwiki lint <vault> --summary`. Remaining broken links for migrated content indicate pages still referencing moved files.
+8. **Optional summary.** Append one entry to `{vault}/log.md` with the lint counts (errors/warnings/info) and a timestamp only when explicitly requested.
 
 **Output Format:**
 Return a structured summary:
@@ -49,3 +50,4 @@ Return a structured summary:
 - Auto-rotating logs without user consent
 - Auto-updating sha256 fields
 - Modifying any page beyond an explicitly requested lint summary entry in `log.md`
+- Printing live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets in findings or summaries

package/skills/agents/wiki-query.md

@@ -34,7 +34,8 @@ You are a vault search and synthesis specialist using E2 4-signal ranking to fin
    - Type affinity: 1.0×
 6. **Read top candidates.** Read frontmatter + body of highest-scored pages.
 7. **Synthesize answer.** Compose with explicit citations to candidate pages using `^[page-path]` markers.
-8. **Optional file.** If the task asks to persist: write to `queries/<slug>.md` or `comparisons/<slug>.md` with full frontmatter, validate, then update `index.md` → `log.md`. If the filed page is a research/evaluation answer, recommendation, or comparison, end it with:
+8. **Sensitive content guard.** Before filing a query or comparison page, scan the generated body for live credentials, access keys, tokens, passwords, cookies, bearer headers, or private keys. Redact before writing. If the answer depends on preserving a live secret, STOP and ask for a redacted source or explicit rotation/remediation direction.
+9. **Optional file.** If the task asks to persist: write to `queries/<slug>.md` or `comparisons/<slug>.md` with full frontmatter, validate, then update `index.md` → `log.md`. If the filed page is a research/evaluation answer, recommendation, or comparison, end it with:
    ```markdown
    ## Decision Closeout
 
@@ -58,8 +59,10 @@ Return:
 **Stop Conditions:**
 - Zero matching pages found
 - `skillwiki path` returns NO_VAULT_CONFIGURED
+- Generated filed content contains unredacted live credentials or other authenticating secrets
 
 **Forbidden:**
 - Filing without `validate` passing
 - Skipping graph refresh when graph.json is missing
 - Accepting wiki claims without filesystem verification
+- Writing live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets to the vault

package/skills/agents/wiki-reingest.md

@@ -30,9 +30,10 @@ You are a drift detection specialist running `skillwiki drift` and processing re
    - **unchanged:** No action needed.
 4. **Process each drifted source:**
    a. Archive old raw: `skillwiki archive <raw-path>`
-   b. Re-fetch content and write as new raw file with updated sha256
-   c. Update all concept/entity pages citing the old source: change `^[raw/...]` markers and `sources:` to reference the new path
-   d. Verify with `skillwiki audit` that no broken markers remain
+   b. Re-fetch content. If it contains live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets, STOP and ask for a redacted source or explicit rotation/remediation direction.
+   c. Write as new raw file with updated sha256
+   d. Update all concept/entity pages citing the old source: change `^[raw/...]` markers and `sources:` to reference the new path
+   e. Verify with `skillwiki audit` that no broken markers remain
 5. **Log.** Append to `{vault}/log.md`: scanned count, drifted count, re-ingested count, skipped count.
 
 **N9 Compliance:**
@@ -53,8 +54,10 @@ Return:
 - `skillwiki drift` returns non-zero (other than DRIFT_DETECTED)
 - No raw sources have `source_url` (nothing to check)
 - All sources unchanged
+- Replacement source content contains unredacted live credentials or other authenticating secrets
 
 **Forbidden:**
 - Modifying files in `raw/` directly (N9)
 - Re-ingesting without archiving old raw first
 - Updating citations without running `skillwiki audit` to verify
+- Writing live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets to the vault

package/skills/agents/wiki-sync.md

@@ -68,3 +68,4 @@ Return:
 - Auto-resolving body conflicts
 - Force-pushing (`git push --force`)
 - Modifying files in `raw/` to resolve conflicts (N9)
+- Printing, committing, or preserving live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets during conflict handling

package/skills/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skillwiki/skills",
-  "version": "0.9.1",
+  "version": "0.9.4",
   "private": true,
   "files": [
     "wiki-*",

package/skills/skills/using-skillwiki/SKILL.md

@@ -55,6 +55,10 @@ sha256:          # computed by skillwiki hash over body bytes after closing ---
 **Layer 2 — Typed Knowledge:** `entities/`, `concepts/`, `comparisons/`, `queries/`, `meta/`. Agent-owned pages with `^[raw/...]` citation markers at paragraph-end. Global scope — project association via `provenance_projects:` frontmatter, not directory nesting.
 **Layer 3 — Project Workspaces (`projects/{slug}/`):** Per-project lifecycle directories with `work/` (spec + plan + retro), `compound/` (distilled lessons/patterns), `architecture/` (ADRs), and `history/` (archived specs/plans).
 **No `inbox/` directory.** Ad-hoc captures go to `raw/transcripts/` or directly into a project work item via `proj-work`. Do not invent new top-level directories — extend Layer 2 via SCHEMA.md tag taxonomy if needed.
+
+## Sensitive Content Policy
+Vault content must not contain live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets. This includes development-only and local-only credentials. Redact values before filing using `[REDACTED:<kind>]` or `[REDACTED:<kind>:<fingerprint>]`. If a source contains live secrets, stop and ask for a redacted source or explicit rotation/remediation direction; do not preserve the secret in `raw/`.
+
 ### Ad-hoc capture: three entry points
 | Entry | When | What happens |
 |-------|------|-------------|
@@ -107,9 +111,30 @@ Use `prd_layer` + `prd_pipeline` from `.claude/dev-loop.config.md` as source of
 
 ## CLI Backbone
 All skills are backed by the `skillwiki` CLI — a deterministic tool with no LLM calls. It handles path resolution, config management, validation, health reporting, and linting. Skills invoke it via Bash for the mechanical parts and use Claude for the creative parts.
-Key CLI subcommands: `init`, `health`, `lint`, `config`, `doctor`, `path`, `lang`, `install`, `graph build`, `archive`, `drift`, `compound`, `tag-sync`, `sync status`, `seed`, `stale`, `observe`, `canvas generate`.
+Key CLI subcommands: `init`, `health`, `lint`, `config`, `doctor`, `path`, `lang`, `install`, `fleet context`, `fleet validate`, `graph build`, `archive`, `drift`, `compound`, `tag-sync`, `sync status`, `seed`, `stale`, `observe`, `canvas generate`.
 Run `skillwiki health <vault> --out /tmp/skillwiki-health.json --no-fail` for a bounded whole-system report that includes doctor, lint, vault-sync, query-readiness, source-freshness, risk flags, and self-check coverage. Run `skillwiki lint <vault> --summary` for lint-only bucket counts with capped examples and details commands. Run `skillwiki doctor` to diagnose setup/runtime issues only. Run `skillwiki config list` to see current configuration.
 
+## Runtime Host Context and Fleet Freshness
+The live output of `skillwiki --human fleet context <vault>` is authoritative for host identity. It overrides stale injected SessionStart context, remembered workspace context, and prior conversation summaries. `fleet context` is local and network-free; it reports `identity_status`, resolver trace, warnings, and the fact that remote freshness was not checked.
+
+Use the local identity check for ordinary runtime context:
+```bash
+VAULT="$(skillwiki --human path | sed 's/ (via.*//')"
+skillwiki --human fleet validate "$VAULT/projects/llm-wiki/architecture/fleet.yaml"
+skillwiki --human fleet context "$VAULT"
+```
+
+Use the remote freshness flow before SSH, sync, deploy, install/uninstall, snapshot, protected-host work, editing `fleet.yaml`, or claiming "fleet is up to date":
+```bash
+VAULT="$(skillwiki --human path | sed 's/ (via.*//')"
+git -C "$VAULT" fetch origin main --prune
+skillwiki --human sync status "$VAULT"
+skillwiki --human fleet validate "$VAULT/projects/llm-wiki/architecture/fleet.yaml"
+skillwiki --human fleet context "$VAULT"
+```
+
+If `identity_status` is `unknown` or `invalid`, treat the runtime as ephemeral: do not infer SSH/self aliases, sync authority, deploy authority, or protected-host permissions. Rerun with `--host-id <id>` only after the user confirms the current machine is that named fleet host.
+
 ## Typical Workflow
 1. **Init** (`wiki-init`) — create vault, set domain and taxonomy
 2. **Ingest** (`wiki-ingest`) — add sources, build pages

package/skills/skills/wiki-adapter-prd/SKILL.md

@@ -62,9 +62,10 @@ Map source sections to typed-knowledge pages:
 0. Resolve vault and language: `skillwiki path` and `skillwiki lang`.
 1. Classify the input format using the structural cues above.
 2. If URL source: run `skillwiki fetch-guard <url>`, then fetch.
-3. Write raw capture: frontmatter + full body → `raw/articles/<slug>.md`.
-4. Run `skillwiki hash <raw-file>`, embed sha256.
-5. Generate typed-knowledge pages following the mapping strategy.
+3. **Sensitive content guard.** Before writing the raw capture or generated pages, scan the source and generated body for live credentials, access keys, tokens, passwords, cookies, bearer headers, or private keys. Redact generated prose before writing. If the source itself contains a live secret and would need to remain raw, STOP instead of preserving it.
+4. Write raw capture: frontmatter + full body → `raw/articles/<slug>.md`.
+5. Run `skillwiki hash <raw-file>`, embed sha256.
+6. Generate typed-knowledge pages following the mapping strategy.
    For generated comparison or evaluation pages, end the body with:
    ```markdown
    ## Decision Closeout
@@ -74,8 +75,8 @@ Map source sections to typed-knowledge pages:
    Follow-up: ...
    ```
    Use exactly one disposition. Preserve action items as skipped project-management content unless the closeout explicitly says `work-item`.
-6. For each page: run `skillwiki validate <page>`. If any fails, STOP.
-7. Write pages, then update `index.md` and `log.md`.
+7. For each page: run `skillwiki validate <page>`. If any fails, STOP.
+8. Write pages, then update `index.md` and `log.md`.
 
 ## Provenance defaults
 
@@ -87,6 +88,7 @@ Map source sections to typed-knowledge pages:
 - `fetch-guard` non-zero.
 - `validate` non-zero on any page.
 - sha256 already exists for the same source (skip — already ingested).
+- Source or generated content contains unredacted live credentials or other authenticating secrets.
 
 ## Forbidden
 
@@ -94,3 +96,4 @@ Map source sections to typed-knowledge pages:
 - Writing index/log before all pages validate.
 - Modifying existing raw files (N9).
 - Auto-generating pages for action items, timelines, or process steps — those are project management, not knowledge.
+- Writing live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets to the vault.

package/skills/skills/wiki-add-task/SKILL.md

@@ -32,8 +32,9 @@ Run `skillwiki lang` at the start. Entry prose and `--human` summaries use the r
 - `text` — the idea/bug/task/note content (required)
 - `type` — one of: `idea`, `bug`, `task`, `note` (default: `idea`)
 - `project` — optional project slug to cross-reference (e.g., `llm-wiki`)
-2. **Build filename.** Derive a slug from the first ~6 words of the text (lowercased, hyphens for spaces, non-alphanumeric stripped). The capture file is `raw/transcripts/YYYY-MM-DD-{type}-{slug}.md`. Each capture gets its own file — never append to an existing file.
-3. **Write frontmatter.** Create the file with ad-hoc capture frontmatter:
+2. **Sensitive content guard.** Before writing a capture, scan the text for live credentials, access keys, tokens, passwords, cookies, bearer headers, or private keys. Redact before writing. If the source text itself contains a live secret that must be preserved verbatim, STOP instead of filing it.
+3. **Build filename.** Derive a slug from the first ~6 words of the text (lowercased, hyphens for spaces, non-alphanumeric stripped). The capture file is `raw/transcripts/YYYY-MM-DD-{type}-{slug}.md`. Each capture gets its own file — never append to an existing file.
+4. **Write frontmatter.** Create the file with ad-hoc capture frontmatter:
 ```yaml
 ---
 source_url:
@@ -47,19 +48,19 @@ project: "[[{slug}]]"
 - If no project, omit the `project` field entirely.
 - `source_url` is null (these are locally originated captures).
 - No `sha256` — ad-hoc captures are mutable working notes, not immutable sources.
-4. **Write body.** Below the frontmatter, write:
+5. **Write body.** Below the frontmatter, write:
 ```markdown
 # {type}: {text}
 {text}
 ```
 Use the resolved output language for any prose. The type label and frontmatter stay English.
-5. **Cross-reference (optional).** If a `project` slug was provided:
+6. **Cross-reference (optional).** If a `project` slug was provided:
 - Check that `projects/{slug}/` exists in the vault.
 - Append a one-line reference to the project's compound notes:
 `- [YYYY-MM-DD] capture: [text (first 60 chars)] → raw/transcripts/YYYY-MM-DD-{type}-{slug}.md`
 - Do NOT create a full work item (that's `proj-work`'s job).
-6. **Update log.md.** Append: `## [YYYY-MM-DD] capture | [type]: [text (first 60 chars)]`
-7. **Confirm to user.** Report what was captured and where. Suggest next steps:
+7. **Update log.md.** Append: `## [YYYY-MM-DD] capture | [type]: [text (first 60 chars)]`
+8. **Confirm to user.** Report what was captured and where. Suggest next steps:
 - If `type: idea` → "Consider ingesting related sources to develop this idea."
 - If `type: bug` → "Use proj-work to create a bug-fix work item."
 - If `type: task` → "Use proj-work to track this task through the dev loop."
@@ -83,11 +84,13 @@ Ad-hoc captures omit `sha256` — they are mutable working notes, not immutable
 - `skillwiki path` returns NO_VAULT_CONFIGURED.
 - No `text` provided (prompt user once, then stop).
 - Target file already exists (use a different slug or add a suffix).
+- Capture text contains unredacted live credentials or other authenticating secrets.
 ## Forbidden
 - Creating an `inbox/` directory. All captures go to `raw/transcripts/`.
 - Appending to existing capture files — each capture gets its own file.
 - Creating a work item — this is capture-only. Use `proj-work` for full work items.
 - Writing to any Layer 2 or Layer 3 location. Captures are Layer 1 (raw).
+- Writing live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets to the vault.
 ## Filesystem drop (offline capture)
 When you're not in a Claude session, drop files directly into `raw/transcripts/`:
 1. Create a `.md` file in `raw/transcripts/` — name it descriptively (e.g., `2026-05-08-idea-fix-template.md`)

package/skills/skills/wiki-crystallize/SKILL.md

@@ -26,12 +26,15 @@ Reason: ...
 Follow-up: ...
 ```
 Use exactly one disposition. Keep this as a prompt/template convention; do not add validation or lint enforcement.
-4. `skillwiki validate <page>`. If non-zero, STOP.
-5. Apply writes: page → `index.md` → `log.md`.
+4. **Sensitive content guard.** Before writing, scan the source and generated body for live credentials, access keys, tokens, passwords, cookies, bearer headers, or private keys. Redact generated prose before writing. If the source itself contains a live secret and would need to remain raw, STOP instead of preserving it.
+5. `skillwiki validate <page>`. If non-zero, STOP.
+6. Apply writes: page → `index.md` → `log.md`.
 ## Stop conditions
 - `validate` non-zero.
 - Missing `provenance:` for project-context runs.
+- Source or generated content contains unredacted live credentials or other authenticating secrets.
 ## Forbidden
 - Filing without explicit `provenance:`.
 - Updating `index.md` before `validate` passes.
 - Writing `[[wikilinks]]` to pages that don't exist in the vault. Before linking, verify the target exists: check `index.md` or `ls` the target directory. If the target doesn't exist yet, use plain text instead of a wikilink.
+- Writing live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets to the vault.

package/skills/skills/wiki-ingest/SKILL.md

@@ -19,8 +19,9 @@ Run `skillwiki lang` at the start. Generate page-body prose, narrative sections,
 1. **Guard.** For each URL: run `skillwiki fetch-guard <url>`. If exit ≠ 0, STOP and surface the error. Do not retry.
 2. **Fetch.** Use `web_fetch` (or read local file) under Layer 2 controls (the CLI Layer 2 fetcher applies in tests; in skill runtime use `web_fetch` directly and treat any error as STOP).
 3. **Identity guard.** Before writing raw files, ensure the target raw filename/title, `source_url`, fetched H1/title, and early body subject agree. If `skillwiki ingest` reports `INGEST_VALIDATION_FAILED` with `source identity conflict`, STOP. Do not fix by renaming after the fact; choose the correct title/source pair or ask the user.
-4. **Hash.** Write the raw file (frontmatter + body). Run `skillwiki hash <raw-file>` and embed the result in raw frontmatter `sha256:`.
-5. **Generate page(s).** Compose typed-knowledge page(s) with citations pre-attached (`^[raw/...]` markers). Every page MUST include:
+4. **Sensitive content guard.** Before writing or filing any vault page, scan the source and generated body for live credentials, access keys, tokens, passwords, cookies, bearer headers, or private keys. Redact generated prose before writing. If the source itself must remain raw and contains a live secret, STOP instead of preserving it.
+5. **Hash.** Write the raw file (frontmatter + body). Run `skillwiki hash <raw-file>` and embed the result in raw frontmatter `sha256:`.
+6. **Generate page(s).** Compose typed-knowledge page(s) with citations pre-attached (`^[raw/...]` markers). Every page MUST include:
 - `> **TL;DR:**` blockquote as the first content after the title heading — a one-sentence summary of the page's key takeaway (under 200 chars). See SCHEMA.md `## TL;DR Convention`.
 - For pages tagged `architecture` or explaining workflows/systems: include a Mermaid diagram (`graph TB` or `sequenceDiagram`) in the body. Follow Obsidian-compatible Mermaid rules (see SCHEMA.md `## Mermaid Diagrams`).
 For generated `comparisons/` pages or evaluation-style `queries/` pages, end the body with:
@@ -32,9 +33,9 @@ Reason: ...
 Follow-up: ...
 ```
 Use exactly one disposition. Keep this as a prompt convention, not a validator rule.
-6. **Validate.** For each generated page: run `skillwiki validate <page>`. If exit ≠ 0, STOP — do not write index/log.
-7. **Apply writes in order.** raw → page(s) → `index.md` → `log.md`.
-8. **Confidence flag.** If only one source is cited, set `confidence: low`.
+7. **Validate.** For each generated page: run `skillwiki validate <page>`. If exit ≠ 0, STOP — do not write index/log.
+8. **Apply writes in order.** raw → page(s) → `index.md` → `log.md`.
+9. **Confidence flag.** If only one source is cited, set `confidence: low`.
 ## Provenance defaults
 - Default `provenance: research`.
 - If cwd is inside `projects/{slug}/`, set `provenance: project` and add `provenance_projects: ["[[slug]]"]`.
@@ -47,6 +48,7 @@ Raw ephemeral data (market feeds, logs, transient JSON) must be written to the *
 - `fetch-guard` non-zero.
 - Fetch timeout / size limit exceeded.
 - `INGEST_VALIDATION_FAILED` with `source identity conflict`.
+- Source or generated content contains unredacted live credentials or other authenticating secrets.
 - `validate` non-zero on any page.
 - sha256 already exists in vault for the same source.
 ## Forbidden
@@ -57,7 +59,7 @@ Raw ephemeral data (market feeds, logs, transient JSON) must be written to the *
 - Writing `[[wikilinks]]` to pages that don't exist in the vault. Before linking, verify the target exists: check `index.md` or `ls` the target directory. If the target doesn't exist yet, use plain text instead of a wikilink.
 ## Batch Mode
 When the user provides multiple sources (a directory of files, a list of URLs, or a multi-document input):
-1. **Loop per source.** Execute steps 1–6 for each source individually (guard → fetch → identity guard → hash → generate → validate).
+1. **Loop per source.** Execute steps 1–7 for each source individually (guard → fetch → identity guard → sensitive content guard → hash → generate → validate).
 2. **Accumulate, don't write yet.** Collect all raw files and pages in memory. Do not write `index.md` or `log.md` until every source has validated.
 3. **Fail fast.** If any page fails validation, STOP. Report all failures. Do not write index/log for any source.
 4. **Deduplication.** Before writing each raw file, check `sha256` against existing vault raw sources. Skip sources whose content is already present.

package/skills/skills/wiki-lint/SKILL.md

@@ -15,12 +15,14 @@ Standard four reads.
 2. For lint-only maintenance, run `skillwiki lint <vault> --summary`. This returns bounded bucket counts, capped examples, and `details_command` hints without full item arrays.
 3. Drill into important buckets with `skillwiki lint <vault> --only <bucket>` when examples are insufficient for remediation.
 4. Reason over findings; present grouped by severity with concrete suggested actions per kind. If the CLI was recently updated with new lint checks, re-running lint on the full vault may flag pre-existing pages that predate the new rule — treat these as legitimate findings, not false positives.
-5. If `log_rotate_needed` is present and the user consents, run `skillwiki log-rotate <vault> --apply`. Otherwise leave alone.
-6. **Post-migration verification**: If the user recently migrated content (e.g., moved entity/concept pages to another vault), re-run `skillwiki lint <vault> --summary` and verify that broken_wikilinks count decreased. Remaining broken links for migrated content indicate pages still referencing the moved files — these should be cleaned up (remove citations or migrate the referencing pages too).
-7. Append a `log.md` entry summarizing lint counts only when the user asked to record the maintenance result. Do not log routine `health` reports by default.
+5. Treat `sensitive_content` as a security error. Drill down with `skillwiki lint <vault> --only sensitive_content --human`. Redaction is allowed as a security exception to raw immutability only through `skillwiki lint <vault> --fix --only sensitive_content`; never print the secret value in the report.
+6. If `log_rotate_needed` is present and the user consents, run `skillwiki log-rotate <vault> --apply`. Otherwise leave alone.
+7. **Post-migration verification**: If the user recently migrated content (e.g., moved entity/concept pages to another vault), re-run `skillwiki lint <vault> --summary` and verify that broken_wikilinks count decreased. Remaining broken links for migrated content indicate pages still referencing the moved files — these should be cleaned up (remove citations or migrate the referencing pages too).
+8. Append a `log.md` entry summarizing lint counts only when the user asked to record the maintenance result. Do not log routine `health` reports by default.
 ## Stop conditions
 None — lint reports all findings even on per-page errors.
 ## Forbidden
 - Auto-rotating logs.
 - Auto-updating sha256 fields.
 - Modifying any page beyond a user-approved lint summary entry in `log.md`.
+- Printing live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets in findings or summaries.

package/skills/skills/wiki-query/SKILL.md

@@ -22,7 +22,8 @@ Standard four reads (SCHEMA, index, log, project context if applicable).
 - Type affinity: 1.0×
 5. **Read top candidates** in full (frontmatter + body).
 6. **Synthesize answer** with explicit citations to the candidate pages.
-7. **Optional file.** If user accepts: write to `queries/<slug>.md` or `comparisons/<slug>.md` with full frontmatter, validate, then update `index.md` then `log.md`. If the filed page is a research/evaluation answer, recommendation, or comparison, end it with:
+7. **Sensitive content guard.** Before filing any query or comparison page, scan the generated body for live credentials, access keys, tokens, passwords, cookies, bearer headers, or private keys. Redact before writing. If the answer depends on preserving a live secret, STOP and ask for a redacted source or explicit rotation/remediation direction.
+8. **Optional file.** If user accepts: write to `queries/<slug>.md` or `comparisons/<slug>.md` with full frontmatter, validate, then update `index.md` then `log.md`. If the filed page is a research/evaluation answer, recommendation, or comparison, end it with:
 ```markdown
 ## Decision Closeout
 
@@ -34,6 +35,7 @@ Use exactly one disposition. This is a prompt convention only; do not add CLI en
 ## Stop conditions
 - Zero matching pages.
 - User declines to file.
+- Generated filed content contains unredacted live credentials or other authenticating secrets.
 ## Pitfalls
 ### Claimed-status vs actual-state gap
 When a wiki page (especially a work item `tasks.md`) claims that fixes were applied, features were completed, or files were removed — **verify on disk before accepting the claim**. In one incident, a `tasks.md` marked 6 items DONE but 5 were not actually applied: a script claimed "removed" was still 2020 bytes on disk, a crontab claimed "updated to 30min" was still `*/10`, and a build target claimed "verified has consumers" had no web server serving it.
@@ -41,3 +43,4 @@ When a wiki page (especially a work item `tasks.md`) claims that fixes were appl
 ## Forbidden
 - Filing without `validate` passing.
 - Skipping the orientation reads even for "quick" queries.
+- Writing live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets to the vault.

package/skills/using-skillwiki/SKILL.md

@@ -55,6 +55,10 @@ sha256:          # computed by skillwiki hash over body bytes after closing ---
 **Layer 2 — Typed Knowledge:** `entities/`, `concepts/`, `comparisons/`, `queries/`, `meta/`. Agent-owned pages with `^[raw/...]` citation markers at paragraph-end. Global scope — project association via `provenance_projects:` frontmatter, not directory nesting.
 **Layer 3 — Project Workspaces (`projects/{slug}/`):** Per-project lifecycle directories with `work/` (spec + plan + retro), `compound/` (distilled lessons/patterns), `architecture/` (ADRs), and `history/` (archived specs/plans).
 **No `inbox/` directory.** Ad-hoc captures go to `raw/transcripts/` or directly into a project work item via `proj-work`. Do not invent new top-level directories — extend Layer 2 via SCHEMA.md tag taxonomy if needed.
+
+## Sensitive Content Policy
+Vault content must not contain live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets. This includes development-only and local-only credentials. Redact values before filing using `[REDACTED:<kind>]` or `[REDACTED:<kind>:<fingerprint>]`. If a source contains live secrets, stop and ask for a redacted source or explicit rotation/remediation direction; do not preserve the secret in `raw/`.
+
 ### Ad-hoc capture: three entry points
 | Entry | When | What happens |
 |-------|------|-------------|
@@ -107,9 +111,30 @@ Use `prd_layer` + `prd_pipeline` from `.claude/dev-loop.config.md` as source of
 
 ## CLI Backbone
 All skills are backed by the `skillwiki` CLI — a deterministic tool with no LLM calls. It handles path resolution, config management, validation, health reporting, and linting. Skills invoke it via Bash for the mechanical parts and use Claude for the creative parts.
-Key CLI subcommands: `init`, `health`, `lint`, `config`, `doctor`, `path`, `lang`, `install`, `graph build`, `archive`, `drift`, `compound`, `tag-sync`, `sync status`, `seed`, `stale`, `observe`, `canvas generate`.
+Key CLI subcommands: `init`, `health`, `lint`, `config`, `doctor`, `path`, `lang`, `install`, `fleet context`, `fleet validate`, `graph build`, `archive`, `drift`, `compound`, `tag-sync`, `sync status`, `seed`, `stale`, `observe`, `canvas generate`.
 Run `skillwiki health <vault> --out /tmp/skillwiki-health.json --no-fail` for a bounded whole-system report that includes doctor, lint, vault-sync, query-readiness, source-freshness, risk flags, and self-check coverage. Run `skillwiki lint <vault> --summary` for lint-only bucket counts with capped examples and details commands. Run `skillwiki doctor` to diagnose setup/runtime issues only. Run `skillwiki config list` to see current configuration.
 
+## Runtime Host Context and Fleet Freshness
+The live output of `skillwiki --human fleet context <vault>` is authoritative for host identity. It overrides stale injected SessionStart context, remembered workspace context, and prior conversation summaries. `fleet context` is local and network-free; it reports `identity_status`, resolver trace, warnings, and the fact that remote freshness was not checked.
+
+Use the local identity check for ordinary runtime context:
+```bash
+VAULT="$(skillwiki --human path | sed 's/ (via.*//')"
+skillwiki --human fleet validate "$VAULT/projects/llm-wiki/architecture/fleet.yaml"
+skillwiki --human fleet context "$VAULT"
+```
+
+Use the remote freshness flow before SSH, sync, deploy, install/uninstall, snapshot, protected-host work, editing `fleet.yaml`, or claiming "fleet is up to date":
+```bash
+VAULT="$(skillwiki --human path | sed 's/ (via.*//')"
+git -C "$VAULT" fetch origin main --prune
+skillwiki --human sync status "$VAULT"
+skillwiki --human fleet validate "$VAULT/projects/llm-wiki/architecture/fleet.yaml"
+skillwiki --human fleet context "$VAULT"
+```
+
+If `identity_status` is `unknown` or `invalid`, treat the runtime as ephemeral: do not infer SSH/self aliases, sync authority, deploy authority, or protected-host permissions. Rerun with `--host-id <id>` only after the user confirms the current machine is that named fleet host.
+
 ## Typical Workflow
 1. **Init** (`wiki-init`) — create vault, set domain and taxonomy
 2. **Ingest** (`wiki-ingest`) — add sources, build pages