@event4u/agent-config 9.7.0 → 9.9.0

package/docs/contracts/file-ownership-matrix.md

@@ -1,135 +0,0 @@
----
-stability: beta
-keep-beta-until: 2026-08-12
----
-
-# File-ownership matrix
-
-> **Audience:** roadmap authors, phase reviewers, and CI gate writers
-> who need to know which artefact reads which, and whether two phases
-> can run concurrently without colliding.
-> **Generator:** `scripts/generate_ownership_matrix.py`
-> (run via `task generate-ownership-matrix`).
-> **Validator:** `task check-ownership-matrix` (fails if the JSON drifts
-> from a fresh regeneration).
-> **Companion contracts:** [`load-context-schema.md`](load-context-schema.md),
-> [`context-paths.md`](context-paths.md).
-
-This contract defines the **schema** of the file-ownership matrix: the
-machine-readable JSON at `docs/contracts/file-ownership-matrix.json` and
-the human-readable mirror at
-`agents/settings/contexts/structural/file-ownership-matrix.md`. Both are
-regenerated from `.agent-src.uncondensed/` by the generator and locked
-by CI.
-
-**Status:** internal-locked (`stability: beta`). Schema bumps require a
-contract version increment plus a roadmap revision (per
-`road-to-structural-optimization.md` § 0.1).
-
-## Why the matrix exists
-
-`road-to-structural-optimization` Phase 0.1 (CRITICAL) is the DAG
-successor of Phase 0.6 (path conventions). Subsequent phases (1, 2A,
-2B, 3, 6) extract material into context files, slim rules, and reorder
-command surface. The matrix is the substrate that lets later phases
-ask three questions deterministically:
-
-1. **Which files does my edit reach transitively?** Answered by the
-   `READ_ONLY` edges plus their depth-2 closure.
-2. **Can Phase X and Phase Y land in either order?** Answered by
-   intersecting per-phase `WRITE` sets — empty intersection = safe.
-3. **Has the matrix drifted since the last green CI run?** Answered by
-   the `check-ownership-matrix` consistency gate.
-
-## Schema (v1)
-
-The JSON document is a single object:
-
-```json
-{
-  "version": 1,
-  "generated_by": "scripts/generate_ownership_matrix.py",
-  "source_of_truth": ".agent-src.uncondensed/",
-  "files": {
-    "<repo-root-relative path>": {
-      "kind": "rule | skill | command | context | persona",
-      "rule_type": "always | auto | manual | null",
-      "load_context": ["<path>", ...],
-      "load_context_eager": ["<path>", ...]
-    }
-  },
-  "edges": [
-    {
-      "source": "<path>",
-      "target": "<path>",
-      "type": "READ_ONLY | WRITE | BLOCKS_IF_CONCURRENT",
-      "via": "load_context | load_context_eager | load_context_transitive | body_link",
-      "depth": 1
-    }
-  ]
-}
-```
-
-**Edge types**
-
-| Type | Meaning | Populated in v1 |
-|---|---|:-:|
-| `READ_ONLY` | Source file reads target (frontmatter declaration or body markdown link). | ✅ |
-| `WRITE` | Source file owns target. Self-edge for every file (`source == target`). | ✅ |
-| `BLOCKS_IF_CONCURRENT` | Two phases would write the same file. Derived later from a phase manifest; reserved in v1. | ⏳ |
-
-**Edge `via` values**
-
-- `load_context` — frontmatter `load_context:` entry (lazy).
-- `load_context_eager` — frontmatter `load_context_eager:` entry.
-- `load_context_transitive` — depth-2 hop reached by following a target's own
-  `load_context*` declarations one level deeper.
-- `body_link` — markdown link in body to a path inside one of the
-  scanned roots.
-
-## Depth invariant (G2 — v3.1)
-
-The generator computes the transitive closure of `load_context` /
-`load_context_eager` edges **up to depth 2**. Any chain
-`R → A → B → C` where every hop is a `load_context*` edge **fails the
-build** with exit code 2. This duplicates the same nesting cap that
-Phase 0.2.4 will enforce in `scripts/check_always_budget.py` — two
-enforcement points, one invariant.
-
-## Regeneration policy
-
-| Trigger | What runs | What fails |
-|---|---|---|
-| `task generate-ownership-matrix` | Regenerates JSON + MD in place. | Depth-3 chain → exit 2. |
-| `task check-ownership-matrix` (CI) | Regenerates to memory, diffs against committed JSON. | Diff non-empty → exit 1. Depth-3 → exit 2. |
-| Pre-commit hook (Phase 2A — A1 fix) | Future: regenerate and diff on commits that touch contexts. | Same as `check-ownership-matrix`. |
-
-Any commit that adds, moves, or modifies a context, rule, skill, or
-command MUST regenerate the matrix in the same commit. CI is the
-backstop; the consistency gate fails if regeneration drifts.
-
-## Scope notes (v1)
-
-- **Greppable surface:** `rules/`, `skills/`, `commands/`, `contexts/`,
-  `personas/` under `.agent-src.uncondensed/`. Generated tool
-  projections (`.augment/`, `.claude/`, `.cursor/`, …) are intentionally
-  ignored — they are downstream of the source of truth.
-- **`skill:` frontmatter in rules** (named in roadmap 0.1.2) is reserved.
-  No rules currently declare it; the generator scans for it but emits
-  zero edges of that kind in v1.
-- **Body link parser** is conservative: it only recognises markdown
-  link targets ending in `.md` whose path resolves under one of the
-  scanned roots. Bare backtick-name references (e.g., `` `skill-quality` ``)
-  are **not** edges in v1; they are too ambiguous to attribute.
-- **Cycles** are not the matrix's concern — the existing
-  `lint_load_context.py` rejects them. The matrix generator follows
-  edges with a visited-set so a cycle, if one slipped through, cannot
-  loop forever; it would surface as a depth-3 abort.
-
-## Versioning
-
-`version: 1` is the initial lock. Schema-breaking changes (renaming a
-field, removing an edge type, changing semantics of an existing
-`via`) require a version bump and a roadmap revision. Additive changes
-(new `via` values, new optional file fields) MAY land at the current
-version with a `CHANGELOG.md` entry under `### Beta`.

package/docs/contracts/frontmatter-contract.md

@@ -1,140 +0,0 @@
----
-stability: beta
-keep-beta-until: 2026-08-19
----
-
-# Per-artefact frontmatter contract
-
-> Companion to [`ADR-013`](../decisions/ADR-013-discovery-frontmatter-contract.md)
-> and [`discovery-manifest.schema.json`](discovery-manifest.schema.json). The
-> ADR is the decision; this file is the worked-example reference linters,
-> installer, and contributors cite at runtime.
-
-Every `.md` artefact under `.agent-src.uncondensed/` MUST declare the five
-ADR-013 discovery keys. The release-time manifest builder
-(`scripts/build_discovery_manifest.py`) derives all workspace/pack assignment
-from these alone — **no manual workspace or pack list is ever maintained**.
-
-## Required keys
-
-| Key | Type | Vocabulary | Source |
-|---|---|---|---|
-| `workspaces` | `array<string>`, ≥1 | [`src/config/discovery/workspaces.yml`](../../config/discovery/workspaces.yml) | role-based axis |
-| `packs` | `array<string>`, ≥1 | [`src/config/discovery/packs.yml`](../../config/discovery/packs.yml) | functional axis |
-| `lifecycle` | enum | `active` · `experimental` · `deprecated` · `archived` | review cycle |
-| `trust.level` | enum | `core` · `professional` · `experimental` · `advisory` · `restricted` | safety gate |
-| `trust.confidence` | enum | `high` · `medium` · `low` | curator signal |
-| `trust.human_review_required` | bool | — | reviewer routing |
-| `install.default` | bool | — | ships-by-default toggle |
-| `install.removable` | bool | — | core / removable axis |
-
-Vocabularies are **closed**. New entries require an amendment to
-[`ADR-013`](../decisions/ADR-013-discovery-frontmatter-contract.md) in the
-same PR. The linter
-([`scripts/lint_artefact_frontmatter.py`](../../src/scripts/lint_artefact_frontmatter.py))
-rejects free-text values.
-
-## Worked examples
-
-### Skill — `laravel/SKILL.md`
-
-```yaml
----
-name: laravel
-description: "Writes Laravel PHP — Eloquent, Artisan, FormRequests, jobs, policies."
-source: package
-domain: engineering
-workspaces:
-  - engineering
-packs:
-  - laravel
-lifecycle: active
-trust:
-  level: professional
-  confidence: high
-  human_review_required: false
-install:
-  default: false
-  removable: true
----
-```
-
-### Rule — `rules/commit-policy.md`
-
-```yaml
----
-type: "always"
-tier: "safety-floor"
-description: "Commit policy — never commit unless explicitly authorized this turn."
-alwaysApply: true
-source: package
-workspaces:
-  - engineering
-packs:
-  - engineering-base
-lifecycle: active
-trust:
-  level: core
-  confidence: high
-  human_review_required: false
-install:
-  default: true
-  removable: false
----
-```
-
-### Command — `commands/cost/report.md`
-
-```yaml
----
-name: cost-report
-tier: 2
-description: "Capture token cost from the active session and surface the 50/75/90/100% budget ladder."
-workspaces:
-  - agent-config-maintainer
-packs:
-  - meta
-lifecycle: active
-trust:
-  level: core
-  confidence: high
-  human_review_required: false
-install:
-  default: true
-  removable: false
----
-```
-
-## Quarantine
-
-Artefacts that genuinely cannot yet carry frontmatter (early scaffolds,
-generated stubs) MUST be listed in
-[`src/config/discovery/unassigned-artefacts.yml`](../../config/discovery/unassigned-artefacts.yml)
-with a `reason`. A quarantined entry MUST NOT also carry the five keys —
-the linter rejects that collision.
-
-## Enforcement
-
-| Surface | What runs | When |
-|---|---|---|
-| Local | `task lint-artefact-frontmatter` | manual / pre-commit |
-| Pre-commit | `pre-commit-roadmap-progress` template | when `.agent-src.uncondensed/*.md`, `src/config/discovery/*.yml`, or the linter itself is staged |
-| CI | `task ci` → `lint-artefact-frontmatter` | every push / PR |
-
-Install the pre-commit hook with:
-
-```bash
-./agent-config hooks:install            # combined hook (roadmap + frontmatter)
-./agent-config hooks:install --print    # dump to stdout for manual chaining
-```
-
-The hook is opt-in per concern — it short-circuits when no relevant files
-are staged.
-
-## Roundtrip invariant
-
-Frontmatter survives the `task sync` condensation pipeline. Path-bearing
-keys (`load_context`) may be rewritten relative to the projected location,
-but the five Phase-1 keys above are byte-stable between
-`.agent-src.uncondensed/`, `dist/agent-src/`, and `.augment/`. Enforced by
-`tests/test_frontmatter_roundtrip.py`.

package/docs/contracts/ghostwriter-schema.md

@@ -1,337 +0,0 @@
----
-stability: beta
-keep-beta-until: 2026-08-13
----
-
-# `ghostwriter/<slug>.md` schema (v1)
-
-> **Status:** beta — locked for the `/ghostwriter` cluster roadmap.
-> Re-evaluate fields after the cluster has shipped + been in use
-> for ≥ 1 week.
-
-A **ghostwriter profile** is a single Markdown file that captures the
-public writing voice of a documented public figure so the `/ghostwriter:write`
-and `/post-as:ghostwriter` commands can emit copyable drafts in that
-voice. Ghostwriter is the third voice primitive in the package, peer
-to `personas/*.md` (review-lens, internal) and `.agent-user.md` (the
-maintainer themselves).
-
-The file is owned by the user. The agent never edits it without an
-explicit `accept` step on `/ghostwriter:fetch` re-runs.
-
-## Storage model (dual)
-
-- **Consumer projects** — `agents/reference/ghostwriter/<slug>.md`. Real-person
-  profiles live here. **Gitignored by default** via the package-managed
-  `.gitignore` block. A `--shared` opt-in to commit profiles is
-  deferred to v2; only the doc note lands in v1.
-- **Package source** — `.agent-src.uncondensed/ghostwriter/` ships
-  the README, this schema doc, and `fictional: true` fixtures only.
-  **Zero real-person profiles ever ship with the OSS package.** A CI
-  lint (`task lint-ghostwriter-source`) enforces this rule by failing
-  on any non-allowlisted file or any file lacking the `fictional: true`
-  frontmatter key.
-
-Slug = full-name kebab-case (`alice-walker`). Optional `-<discriminator>`
-suffix for disambiguation (`alice-walker-novelist` vs `alice-walker-cyclist`).
-Namespace conflict resolution is consumer-owned — the package does not
-deduplicate across consumers.
-
-## Locked frontmatter (v1)
-
-```yaml
----
-version: 1
-fictional: false             # required — true for package-side fixtures, false for real-person consumer profiles
-identity:
-  name: "Alice Walker"       # required — public name
-  role_or_title: "novelist"  # required — short role label
-  era: "1944–"               # optional — birth–death range; "1944–" if living
-  public_figure_category: "public_artist"  # required — enum below
-  source_urls:               # required — public sources only, ≥ 3 distinct items
-    - "https://example.org/walker/interview-1"
-    - "https://example.org/walker/essay-collection"
-    - "https://example.org/walker/lecture-2018"
-  fetched_at: "2026-05-15"   # required — ISO date of last fetch
-  confidence: "med"          # required — low | med | high (see § Confidence)
-  attestation_recorded_at: "2026-05-15T10:00:00Z"  # required — when the user attested (NOT consent, see § Ethics floor)
-aliases:                     # optional, consumer-only — alternative names that resolve to this slug
-  - "Hawking"                # case-insensitive match, case-preserving storage
-  - "Prof. Hawking"          # min 2 chars, no homoglyphs (see § Aliases)
-style:
-  fingerprint:
-    sentence_length_avg: 18  # avg words per sentence across samples
-    vocab_register: "literary"  # casual | conversational | professional | literary | academic
-    opener_patterns: ["personal anecdote", "rhetorical question"]
-    closer_patterns: ["call to reflection", "quoted aphorism"]
-    hashtag_rules: "never"   # always | sometimes | never
-    emoji_rules: "never"     # always | sometimes | never
-    paragraph_cadence: "long-form, 4–6 sentence paragraphs"
-  free_form_notes: |
-    Tends to weave personal narrative with broader social observation.
-    Rarely uses imperatives; prefers invitations.
-voice_samples:               # required — max 3 items, each ≤ 200 words, source-attributed
-  - source_url: "https://example.org/walker/interview-1"
-    length_words: 142
-    text: |
-      [actual public excerpt, max 200 words]
-taboos:                      # required — what the target never does in public writing
-  - "political endorsements"
-  - "profanity"
-  - "hashtag-driven posts"
-source_provenance:           # required
-  count: 3                   # number of distinct source URLs
-  last_fetched_at: "2026-05-15"
-  types: ["interview", "essay", "lecture"]  # platforms/formats represented
-  verification: "fetched"    # required — fetched | user-asserted (see § Verification)
-last_updated: "2026-05-15"   # YYYY-MM-DD — bumped on every accepted change
----
-```
-
-After the frontmatter, the body is a single freeform **`# Notes`**
-section for the user's own observations on the profile. Hard cap:
-**200 lines** total file size (frontmatter + body + Notes).
-
-## Field reference
-
-| Field | Required | Purpose |
-|---|---|---|
-| `version` | yes | Schema version. v1 is the only valid value today. |
-| `fictional` | yes | `true` for package fixtures, `false` for real-person consumer profiles. Drives `task lint-ghostwriter-source`. |
-| `identity.name` | yes | Public name of the figure. |
-| `identity.role_or_title` | yes | Short role label (novelist, executive, …). |
-| `identity.era` | no | Birth–death range. Trailing `–` for living figures. |
-| `identity.public_figure_category` | yes | Enum: `author` \| `executive` \| `academic` \| `politician` \| `journalist` \| `public_speaker` \| `public_artist` \| `deceased_historical`. |
-| `identity.source_urls` | yes | ≥ 3 public source URLs. Drives `confidence`. |
-| `identity.fetched_at` | yes | ISO date of the most recent fetch. |
-| `identity.confidence` | yes | `low` \| `med` \| `high` — derived from source count/diversity. |
-| `identity.attestation_recorded_at` | yes | ISO timestamp the user attested the public-figure gate. |
-| `aliases` | no | Consumer-only list of alternative names that resolve to this profile's slug. See [§ Aliases](#aliases). Banned on `fictional: true` fixtures. |
-| `style.fingerprint.*` | yes | Structured shape of the voice. All sub-fields required. |
-| `style.free_form_notes` | yes | Free-form supplement to the structured fingerprint. |
-| `voice_samples` | yes | Max 3 items; each `≤ 200 words`; each source-attributed. |
-| `taboos` | yes | What the target never does — feeds the write engine's negative-constraint pass. |
-| `source_provenance.count` | yes | Distinct source URLs. |
-| `source_provenance.last_fetched_at` | yes | ISO date — drives the 90-day stale warning. |
-| `source_provenance.types` | yes | Platforms/formats (interview, essay, post, book, …). |
-| `source_provenance.verification` | yes | `fetched` (host agent retrieved) \| `user-asserted` (user pasted; not verifiable). |
-| `last_updated` | yes | ISO date, bumped on every accept. |
-
-## Confidence
-
-Derived deterministically from `source_provenance.count` and `types`:
-
-| Sources × types | Confidence |
-|---|---|
-| 3 sources, same platform | `low` |
-| 3+ sources, 2+ platforms | `med` |
-| 5+ sources, 3+ platforms, ≥ 1 canonical (Wikipedia / official site / published book) | `high` |
-
-`/ghostwriter:fetch` refuses to write a profile with fewer than 3 distinct
-authoritative sources.
-
-
-## Aliases
-
-`aliases` is an **optional, consumer-only** field listing alternative
-names that resolve to this profile's slug. It is a portability win
-over per-user shell aliases — team-shared profiles become immediately
-usable without per-developer config.
-
-The list is read by `/ghostwriter:write --as=<value>` (and the
-`/post-as:ghostwriter` thin alias) when resolving the style source:
-
-1. Exact slug match (case-insensitive on filename stem).
-2. **If no slug match**, scan every consumer profile's `aliases` list
-   for a case-insensitive equality match against `<value>`.
-3. If neither matches, fall through to the interactive numbered menu.
-
-### Storage rules
-
-- **Case-insensitive match, case-preserving storage** — the resolver
-  treats `--as=hawking` and `--as=Hawking` as identical, but the YAML
-  preserves the author's chosen casing.
-- **Minimum length: 2 characters** — single-character aliases are
-  collision magnets and are rejected by the consumer-side lint.
-- **No homoglyphs** — aliases must use Latin script (ASCII letters,
-  digits, common punctuation, common Latin diacritics). Cyrillic,
-  Greek, or other confusable scripts are rejected. Prevents spoofing
-  like `Stephеn` (Cyrillic `е`) shadowing `Stephen`.
-- **Case-insensitive uniqueness within a profile** — a single profile
-  cannot list both `"Hawking"` and `"hawking"`.
-- **Case-insensitive uniqueness across consumer profiles** — two
-  different profiles in the same consumer tree cannot share an alias
-  (including alias-vs-slug collisions). Conflicts fail the consumer-side
-  lint (Option B — lint-time rejection, never a runtime disambiguation
-  menu). Determinism contract trumps UX convenience.
-
-### Footer integrity (canonical name only)
-
-The mandatory [disclosure footer](#mandatory-disclosure-footer-deterministic)
-**always** uses `identity.name`, never the alias that triggered the
-command. A user invoking `/ghostwriter:write --as=Hawking` against a
-profile with `identity.name: "Stephen Hawking"` produces a footer
-reading *"Written in the style of Stephen Hawking, not by them."* —
-not *"…of Hawking, not by them."* This makes aliases UX-only; identity
-attribution stays deterministic.
-
-### Package-source ban
-
-`aliases:` is **forbidden** on any file with `fictional: true`. Package
-fixtures are schema examples for a single canonical name; aliases are a
-consumer-only deployment feature. The package-source lint
-(`task lint-ghostwriter-source`) fails on `aliases:` in
-`.agent-src.uncondensed/ghostwriter/`.
-
-### Settings toggle (consumer-only)
-
-The consumer enables alias resolution via `.agent-project-settings.yml`:
-
-```yaml
-ghostwriter:
-  aliases: true   # default: true — set to false to disable resolver
-```
-
-Toggling `aliases: false` makes `/ghostwriter:write --as=<value>` resolve
-against slug names only; any `aliases:` entries in profiles are ignored
-at resolve time (but the lint still validates them on commit).
-
-## Verification
-
-`source_provenance.verification` distinguishes two acquisition paths:
-
-- `fetched` — the host agent retrieved the source URLs via its built-in
-  web-fetch / web-search capability. Default for `/ghostwriter:fetch`.
-- `user-asserted` — the host agent could not fetch and the user pasted
-  the material manually. The package cannot independently verify these
-  sources. `/ghostwriter:show` surfaces user-asserted profiles with a
-  visible `⚠️ user-asserted sources — not independently verified` line.
-
-This split exists because the package contains zero network code (see
-[§ Determinism floor](#determinism-floor)); the agent cannot otherwise
-distinguish first-party fetch from paste-and-trust.
-
-## Ethics floor
-
-### Public-figure-only gate (advisory)
-
-Before `/ghostwriter:fetch` writes any file, the user must explicitly
-attest that:
-
-1. The target is a documented public figure with a public-facing role
-   matching `public_figure_category`.
-2. The source URLs are public, not paywalled, not login-walled, not
-   leaked, not retracted.
-3. The user accepts the right-of-publicity and defamation surface — the
-   user owns the legal call, not the package.
-4. The user understands the disclosure footer on every `/ghostwriter:write`
-   output is non-removable.
-
-The attestation timestamp is recorded in `identity.attestation_recorded_at`.
-
-**The gate is advisory by design.** The package has no network code and
-cannot verify the target's public-figure status against Wikidata or any
-external source. The user's attestation is a documented user-asserted
-checkpoint, not legal consent on the figure's behalf — for living
-figures, no consent path exists short of direct opt-in (deferred to v2).
-
-### Mandatory disclosure footer (deterministic)
-
-Every `/ghostwriter:write` and `/post-as:ghostwriter` output ends with
-this literal footer:
-
-```
-Written in the style of <identity.name>, not by them.
-```
-
-The footer is appended by the command's procedural output template as
-a literal string — **not** generated by the model. There is no
-`--no-disclosure` flag. The acceptance criteria grep-verify the absence
-of any opt-out flag in the command source.
-
-### Banned content (always)
-
-Even for documented public figures, `/ghostwriter:fetch` refuses:
-
-- Leaked drafts or material marked private / draft / internal.
-- Paywalled or login-walled content.
-- Private DMs, private email leaks, retracted posts.
-- Medical, financial, or legal data attributed to the figure.
-- Opinions the figure has not publicly stated.
-
-### Excluded targets
-
-Private individuals (a random LinkedIn user who is not a public figure)
-remain out of scope. This carve-out only widens the persona-roadmap's
-"no third-party PII" floor for documented public figures, never for
-anyone else.
-
-## Determinism floor (inherited)
-
-The `agent-config` package contains **zero network code**. `/ghostwriter:fetch`
-is a procedural document that delegates the fetch or search to the host
-agent's built-in capability. The package only reads the returned data
-and proposes a diff for user acceptance.
-
-## Staleness
-
-When `source_provenance.last_fetched_at` is older than 90 days, any
-`/ghostwriter:*` command surfaces a one-line warning (non-blocking):
-
-```
-⚠️  ghostwriter/<slug>.md was last fetched YYYY-MM-DD (>90 days ago). Run /ghostwriter:fetch <slug> --force-refresh.
-```
-
-## Re-fetch flow
-
-`/ghostwriter:fetch` on an existing slug routes through a diff-and-accept
-flow mirroring `/agents user accept` — the user reviews the proposed
-diff before any write. `--force-refresh` rebuilds the profile from scratch
-instead of merging.
-
-## Lint enforcement (`task lint-ghostwriter-source`)
-
-The lint runs in `task ci` and fails on:
-
-1. Any file under `.agent-src.uncondensed/ghostwriter/` whose stem is
-   **not** on the fixture allowlist (`scripts/ghostwriter_fixture_allowlist.txt`).
-2. Any allowlisted file missing `fictional: true` in frontmatter.
-3. Any package-source file (`fictional: true`) carrying an `aliases:`
-   field (aliases are a consumer-only feature; see [§ Aliases](#aliases)).
-4. Any consumer-side file under `agents/reference/ghostwriter/` with `fictional: true`
-   (fictional profiles belong in the package source, not consumer trees).
-5. Any consumer-side `aliases:` entry that violates the storage rules:
-   shorter than 2 characters, non-Latin scripts (homoglyph protection),
-   duplicate within a profile (case-insensitive), or colliding across
-   profiles (case-insensitive — alias-vs-alias or alias-vs-slug).
-
-New package-side fixtures require updating the allowlist + reviewer
-sign-off.
-
-## Commands
-
-| Command | Role |
-|---|---|
-| `/ghostwriter:fetch` | Creates or refreshes a profile from URL or name input. Runs the public-figure gate. |
-| `/ghostwriter:write` | Generates a draft in the chosen voice. Appends the mandatory disclosure footer. |
-| `/ghostwriter:list` | Numbered listing of available profiles. |
-| `/ghostwriter:show` | Read-only render of one profile. |
-| `/ghostwriter:delete` | Two-step confirmation, hard-deletes the file. |
-| `/post-as:me` | Separate top-level command. Reads `.agent-user.md`; shares the write engine. |
-| `/post-as:ghostwriter` | Thin alias to `/ghostwriter:write`. |
-
-See [`command-clusters.md`](command-clusters.md) for the locked
-cluster registration.
-
-## Gitignore
-
-`agents/reference/ghostwriter/*.md` (except `README.md`) is added to the
-package-managed `.gitignore` block ([`src/config/gitignore-block.txt`](../../config/gitignore-block.txt))
-and ignored by default. A `--shared` opt-in to commit profiles is
-deferred to v2.
-
-## See also
-
-- [`agent-user-schema`](agent-user-schema.md) — the maintainer-self primitive that `/post-as:me` consumes.
-- [`persona-schema`](persona-schema.md) — the review-lens primitive, distinct from ghostwriter.
-- [`command-clusters`](command-clusters.md) — the canonical cluster registry.