@event4u/agent-config 9.8.0 → 9.10.0

package/dist/agent-src/commands/agents/user/delete.md

@@ -0,0 +1,147 @@
+---
+model_tier: medium
+name: agents-user-delete
+pack: meta
+tier: 2
+visibility: internal
+cluster: agents
+sub: user
+skills: [agents]
+description: Delete one buffered global observation, purge every observation attributed to a project, or revoke a field from the global profile.md — each writes an append-only tombstone before deleting.
+argument-hint: "[observation <id> | project <path> | profile-field <field>]"
+suggestion:
+  eligible: false
+  rationale: "Mutates the global observation buffer or profile.md — only run from /agents user review, /agents user show --audit, or explicit user invocation."
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+---
+
+# /agents user delete
+
+Delete something the learning channel wrote to the **global** layer —
+road-to-global-user-memory Phase 4, the delete counterpart of
+[`/agents user accept`](accept.md). Every deletion writes an
+append-only tombstone to the revocation ledger BEFORE the underlying
+file is rewritten without it — see
+[`agent-user-schema § Delete, revoke, and audit`](../../../../../docs/contracts/agent-user-schema.md#delete-revoke-and-audit-road-to-global-user-memory-phase-4).
+
+Three targets, one per invocation:
+
+| Target | Removes | Backing function |
+|---|---|---|
+| `observation <id>` | ONE buffered line from `observations.jsonl` | [`deleteGlobalObservation`](../../../../../src/scripts/_lib/user_global_observations.ts) |
+| `project <path>` | EVERY observation attributed (`context.project_path`) to that project | [`purgeProjectContext`](../../../../../src/scripts/_lib/user_global_observations.ts) |
+| `profile-field <field>` | A field's value from the global `profile.md` | [`revokeGlobalProfileField`](../../../../../src/scripts/_lib/agent_user_profile.ts) |
+
+Use when:
+
+- [`/agents user show --audit`](show.md) or
+  [`/agents user review`](review.md) surfaced something the user wants
+  gone.
+- A project was deleted and its buffered facts should not linger
+  forever (`project <path>`).
+- A promoted or accepted profile field turned out to be wrong
+  (`profile-field <field>`).
+
+Never runs autonomously — always asks before writing, exactly like
+`accept`.
+
+## Steps
+
+### 1. Resolve the target
+
+| Invocation | Target |
+|---|---|
+| `/agents user delete observation <id>` | The buffered observation whose `observationId` equals `<id>` (shown by `/agents user show --audit` or `/agents user review`) |
+| `/agents user delete project <path>` | Every observation whose `context.project_path` equals `<path>` |
+| `/agents user delete profile-field <field>` | `<field>` in the global `profile.md` (must match the schema enum) |
+| No argument | Print the target-kind table above and ask which; then ask for the id/path/field |
+
+Invalid `<field>` → print the schema enum and stop. No observation
+matches `<id>` → print "No buffered observation with that id." and
+stop (no tombstone is written for a no-op — see the backing functions'
+`deleted: false` / `purgedCount: 0` contract).
+
+### 2. Confirm
+
+```
+Delete this from the global user-memory layer?
+
+  target : {observation <id> | project <path> | profile-field <field>}
+  current: {for profile-field — the current value; for observation/project — the suggest text(s) that will be removed}
+
+> 1. Delete — write a tombstone, then remove
+> 2. Cancel — leave everything untouched
+```
+
+For `project <path>`, list every matched observation's `suggest` text
+before asking, so the user confirms the actual scope, not just a count.
+
+One question per turn. Wait for the user's number.
+
+### 3. Ask for a reason
+
+```
+Why is this being deleted? (one line, becomes the tombstone's `reason`)
+> {free-text reason}
+```
+
+An empty answer is not accepted — re-ask once, then default to `"no
+reason given"` if the user still declines (mirrors
+[`user_global_revocations.appendTombstone`](../../../../../src/scripts/_lib/user_global_revocations.ts)'s
+own fallback, so a user who truly has nothing to say is never blocked).
+
+### 4. Write
+
+On `1. Delete`, call the matching function with today's date and the
+step-3 reason:
+
+- `observation <id>` →
+  [`deleteGlobalObservation(id, reason, { today })`](../../../../../src/scripts/_lib/user_global_observations.ts).
+- `project <path>` →
+  [`purgeProjectContext(path, reason, { today })`](../../../../../src/scripts/_lib/user_global_observations.ts).
+- `profile-field <field>` →
+  [`revokeGlobalProfileField(field, reason, { today })`](../../../../../src/scripts/_lib/agent_user_profile.ts).
+
+Each function writes its tombstone(s) BEFORE the buffer/profile
+rewrite — never call `fs`/the file directly from this command; always
+go through the function so the tombstone-before-delete order holds.
+
+On `2. Cancel`: stop without any write, without any tombstone.
+
+### 5. Confirm
+
+```
+✅  Deleted ({target}). Tombstone recorded: {entity_id}, {revoked_at}.
+```
+
+For `project <path>`, report the count: `✅  Purged {n} observation(s) from {path}. {n} tombstone(s) recorded.`
+
+Do NOT commit. Do NOT auto-chain to a second deletion.
+
+## Rules
+
+- One target per invocation. Run the command again for the next
+  deletion.
+- Never delete without explicit confirmation in step 2 and a reason
+  from step 3.
+- Never write to a file directly — every deletion goes through
+  `deleteGlobalObservation`, `purgeProjectContext`, or
+  `revokeGlobalProfileField` so the tombstone always precedes the
+  delete.
+- Never touch project-local `.agent-user.md` or its buffer from this
+  command — this leaf covers the global layer only. A project-local
+  fact is deleted by editing `.agent-user.md` directly (it never left
+  the project) or via [`/agents user review`](review.md)'s existing
+  "clear a buffer" option.
+- Mirror the user's language for prompts per
+  [`language-and-tone`](../../../../dist/agent-src/rules/language-and-tone.md).
+
+## See also
+
+- Schema: [`agent-user-schema § Delete, revoke, and audit`](../../../../../docs/contracts/agent-user-schema.md#delete-revoke-and-audit-road-to-global-user-memory-phase-4) — the write→delete mapping and the ADR-121 reuse this command exposes.
+- Audit source: [`/agents user show --audit`](show.md) — the read surface that surfaces what there is to delete.
+- Parent: [`/agents user`](../user.md).
+- Sibling: [`/agents user review`](review.md), [`/agents user accept`](accept.md) — the write side this command undoes.

package/dist/agent-src/commands/agents/user/review.md

@@ -7,7 +7,7 @@ visibility: internal
 cluster: agents
 sub: user
 skills: [agents]
-description: List buffered observations from .agent-user.observations.jsonl with numbered options to inspect or accept individually.
+description: List buffered observations from the project-local and global observation buffers with numbered options to inspect or accept individually.
 suggestion:
   eligible: false
   rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
@@ -19,14 +19,17 @@ packs:
 
 # /agents user review
 
-List the buffered observations in `.agent-user.observations.jsonl`
-and let the user choose which to inspect or accept.
+List the buffered observations across BOTH observation buffers —
+project-local `.agent-user.observations.jsonl` and the global
+`~/.event4u/agent-config/user/observations.jsonl` (ADR-138,
+road-to-global-user-memory Phase 2) — and let the user choose which to
+inspect or accept.
 
 Use when:
 
 - You want to see what the agent has learned about your preferences.
-- You suspect `.agent-user.md` is out of date and want a curated
-  diff before editing.
+- You suspect `.agent-user.md` (or the global `profile.md`) is out of
+  date and want a curated diff before editing.
 - You want to dismiss observations the agent collected.
 
 Read-only by itself — actual changes go through
@@ -35,57 +38,90 @@ Read-only by itself — actual changes go through
 
 ## Steps
 
-### 1. Locate buffer
+### 1. Locate buffers
 
 ```bash
 ls .agent-user.observations.jsonl 2>/dev/null
 ```
 
-| State | Action |
+Resolve the global buffer's path via `user_global_observations.
+resolveGlobalObservationsPath()` — it honours the config-home override
+env var and the legacy fallback root exactly like every other global
+artefact, so never hard-code either path here.
+
+| State (either buffer) | Action |
 |---|---|
-| Missing or empty | Print "No buffered observations. The agent has not learned anything new." and stop |
-| Present | Proceed |
+| Both missing or empty | Print "No buffered observations. The agent has not learned anything new." and stop |
+| At least one present | Proceed with whichever buffer(s) exist |
 
 ### 2. Parse + group
 
-Read every line as JSON. Drop malformed lines silently (one-line
-warning at the end with the count). Group by `field`:
+Read every line as JSON from BOTH buffers via
+[`user_global_observations.readGlobalObservations`](../../../../src/scripts/_lib/user_global_observations.ts)
+for the global one, and the equivalent tolerant parse for the
+project-local file. Drop malformed lines silently (one-line warning at
+the end with the combined count; `readGlobalObservations` already
+reports `droppedMalformed` / `droppedUnknownField`). Group by `field`
+ACROSS both buffers, tagging each observation with its layer:
 
 ```
-.agent-user.observations.jsonl — {n} observations across {k} fields
+Buffered observations — {n} across {k} fields ({p} project-local, {g} global)
 
   1. style.pace          ({n}× since {oldest_ts})
-     latest suggest: "rapid" — evidence: user said 'mach kürzer' 3× this session
+     latest suggest: "rapid" [global] — evidence: user said 'mach kürzer' 3× this session
   2. identity.nickname   ({n}× since {oldest_ts})
-     latest suggest: "Matze" — evidence: user signed last 3 messages "— Matze"
+     latest suggest: "Matze" [project] — evidence: user signed last 3 messages "— Matze"
   3. language            ({n}× since {oldest_ts})
-     latest suggest: "de" — evidence: last 12 messages in German, .agent-user.md says "en"
+     latest suggest: "de" [global] — evidence: last 12 messages in German, profile says "en"
+```
+
+Sort by frequency (most observations first, combined across both
+layers), then by recency. When the SAME field has observations in both
+layers, list the most-recent one first and note both counts.
+
+### 2a. Promotion candidates (road-to-global-user-memory Phase 3)
+
+Separately from the field grouping above, call
+[`findPromotionCandidates`](../../../../../src/scripts/_lib/user_global_observations.ts)
+over the global buffer's entries. Any observation with `seen_count ≥ 3`
+(`PROMOTION_SEEN_COUNT_THRESHOLD`) is project-attributed, human-confirmed
+recurring evidence across that many DIFFERENT projects — surface it as
+its own block, ahead of the field list:
+
+```
+Promotion candidates — seen in 3+ projects:
+
+  1. "always use pnpm instead of npm for installs" — seen in 3 projects (acme-web, acme-api, acme-mobile)
 ```
 
-Sort by frequency (most observations first), then by recency.
+This is candidacy only, never a promotion — crossing the threshold makes
+`/agents user accept` able to offer promoting it, nothing more (see
+[`agent-user-schema.md § Project attribution`](../../../../../docs/contracts/agent-user-schema.md#project-attribution-road-to-global-user-memory-phase-3)).
 
 ### 3. Ask
 
 ```
-> 1. Accept the most-frequent suggestion ({field} → {value})
+> 1. Accept the most-frequent suggestion ({field} [{layer}] → {value})
 > 2. Inspect a specific field
-> 3. Clear the buffer (discard all)
-> 4. Cancel
+> 3. Clear a buffer (project-local, global, or both)
+> 4. Promote a candidate from step 2a (only shown when ≥ 1 exists)
+> 5. Cancel
 ```
 
 | Choice | Action |
 |---|---|
-| 1 | Hand off to [`/agents user accept`](accept.md) with the chosen field |
-| 2 | Print every observation for that field with evidence + ts, then re-ask |
-| 3 | Truncate `.agent-user.observations.jsonl` to zero bytes; print confirmation |
-| 4 | Stop without changes |
+| 1 | Hand off to [`/agents user accept`](accept.md) with the chosen field AND layer |
+| 2 | Print every observation for that field (both layers) with evidence + ts, then re-ask |
+| 3 | Ask which buffer(s) to truncate, then truncate the chosen file(s) to zero bytes; print confirmation |
+| 4 | Hand off to [`/agents user accept`](accept.md) with the chosen promotion candidate — `accept` collects the mandatory `promotion_reason` before writing anything |
+| 5 | Stop without changes |
 
 One question per turn. Wait for the user's number.
 
 ### 4. Privacy-floor verify
 
 Before printing any observation's `evidence` text, scan it for the
-[exclusions list](../../../../../../../../docs/contracts/agent-user-schema.md#explicit-exclusions).
+[exclusions list](../../../../../docs/contracts/agent-user-schema.md#explicit-exclusions).
 Match → replace the offending substring with `[redacted]` in the
 rendered output.
 
@@ -100,14 +136,15 @@ turn.
 
 ## Rules
 
-- Read-only on `.agent-user.md`. Only `accept` writes to the persona
-  file.
-- Buffer is the only mutable artefact (truncate via option 3).
+- Read-only on `.agent-user.md` AND the global `profile.md`. Only
+  `accept` writes to either persona file.
+- Both buffers are the only mutable artefacts (truncate via option 3).
 - Mirror the user's language for prompts per
   [`language-and-tone`](../../../../dist/agent-src/rules/language-and-tone.md).
 
 ## See also
 
-- Schema + buffer contract: [`agent-user-schema § Observation buffer`](../../../../../../../../docs/contracts/agent-user-schema.md#observation-buffer).
+- Schema + buffer contract: [`agent-user-schema § Observation buffer`](../../../../../docs/contracts/agent-user-schema.md#observation-buffer).
+- Global buffer implementation: [`user_global_observations.ts`](../../../../src/scripts/_lib/user_global_observations.ts).
 - Parent: [`/agents user`](../user.md).
 - Sibling: [`/agents user accept`](accept.md), [`/agents user update`](update.md).

package/dist/agent-src/commands/agents/user/show.md

@@ -7,7 +7,8 @@ visibility: internal
 cluster: agents
 sub: user
 skills: [agents]
-description: Read-only render of .agent-user.md — prints the persona summary the host agent loads at session start.
+description: Read-only render of the effective (merged) user profile — global profile.md plus project .agent-user.md. --audit renders the global layer raw for delete/revoke decisions.
+argument-hint: "[--audit]"
 suggestion:
   eligible: false
   rationale: "Cluster sub-command — reached via its cluster head's routing or its explicit /cluster:sub name; not independently suggested (surface-consolidation)."
@@ -19,50 +20,71 @@ packs:
 
 # /agents user show
 
-Read-only render of the project-root `.agent-user.md` per
-[`docs/contracts/agent-user-schema.md`](../../../../../../../../../../../docs/contracts/agent-user-schema.md).
+Read-only render of the **effective, merged** user profile — the
+global `~/.event4u/agent-config/user/profile.md` layer plus the
+project-root `.agent-user.md` layer — per
+[`docs/contracts/agent-user-schema.md`](../../../../../docs/contracts/agent-user-schema.md)
+and its Loader contract / merge rule (ADR-138).
 
 Use when:
 
 - You want to see what persona the host agent currently loads.
-- You want to confirm `last_updated` is fresh (≤90 days).
+- You want to confirm the **effective** `last_updated` is fresh (≤90 days).
 - You want a paste-ready summary for handoff or onboarding.
 
 Does **not** edit, observe, or buffer anything. Pure read.
 
+Called with `--audit` (road-to-global-user-memory Phase 4): renders the
+GLOBAL layer's raw holdings instead of the merged effective profile —
+see [§ Audit mode](#audit-mode---audit) below. Use `--audit` when
+deciding what to delete via [`/agents user delete`](delete.md).
+
 ## Steps
 
-### 1. Locate the file
+### 1. Locate both layers
 
 ```bash
 ls .agent-user.md 2>/dev/null
+ls ~/.event4u/agent-config/user/profile.md 2>/dev/null
+ls ~/.config/agent-config/user/profile.md 2>/dev/null   # legacy fallback
 ```
 
-| State | Action |
-|---|---|
-| Present | Proceed |
-| Missing | Print "No `.agent-user.md` found at project root. Run `/agents user init` to create one." and stop |
+| Project file | Global file | Action |
+|---|---|---|
+| Present | Present or absent | Proceed — project layer wins per field it declares |
+| Missing | Present | Proceed — render sourced entirely from the global layer |
+| Missing | Missing | Print "No `.agent-user.md` and no global profile found. Run `/agents user init` to create one, or set up the global profile." and stop |
 
-### 2. Parse frontmatter
+### 2. Parse frontmatter — per layer
 
-Parse the YAML frontmatter and the body (everything after the second
-`---`). Validate against the locked v1 schema:
+Parse each present layer's YAML frontmatter and body (everything after
+the second `---`) independently. Per layer:
 
 - `version` is `1`.
-- `identity.name`, `language`, `role`, `style.pace`,
-  `voice_sample`, `last_updated` are all present.
-- File is ≤100 lines total.
+- File is ≤100 lines total — the cap applies **per layer**, never as a
+  shared total across both files.
+
+Any violation → print a one-line warning identifying the layer, the
+missing/malformed field, and continue with the render (so the user can
+fix it via `/agents user update`).
+
+### 3. Merge
 
-Any violation → print a one-line warning identifying the missing /
-malformed field and continue with the render (so the user can fix it
-via `/agents user update`).
+Apply the deepest-wins merge rule per
+[`agent-user-schema.md § Global profile layer`](../../../../../docs/contracts/agent-user-schema.md#global-profile-layer-adr-138):
+for each field (`identity.name`, `language`, `role`, `style.pace`,
+`voice_sample`, `last_updated`), the project layer's value wins when
+present, otherwise the global layer's value is used. `# Notes`
+concatenates both layers' text under `[global]` / `[project]` markers
+when both carry content.
 
-### 3. Render
+### 4. Render
 
-Print the persona in this exact shape:
+Print the merged persona in this exact shape:
 
 ```
-.agent-user.md  ({n} lines, last_updated: YYYY-MM-DD{staleness_marker})
+Effective user profile  ({staleness_marker})
+  sources: identity.name={global|project}, style.pace={global|project}, …
 
   Identity   : {nickname or name}  ({name} if nickname is set)
   Language   : {language}
@@ -75,15 +97,20 @@ Print the persona in this exact shape:
 
   Notes
   ─────────────
-  {body, indented 2 spaces; "(empty)" if no notes}
+  {merged notes, indented 2 spaces; "(empty)" if neither layer has notes}
 ```
 
-Where `{staleness_marker}` is:
+Where `{staleness_marker}` reflects the **effective** `last_updated`
+(the merged value, not necessarily the project file's own date):
 
-- empty when `last_updated` is within 90 days.
+- empty when within 90 days.
 - ` ⚠️  >90 days` when older (per the schema staleness rule).
 
-### 4. Loader hint
+The `sources:` line lists only the fields that resolved to a
+non-default value, so a project-only or global-only user sees a
+single-source line and is not confused by an empty cascade.
+
+### 5. Loader hint
 
 If the host-agent loader has NOT yet picked up the file this session
 (detect via session memory if available), print one line:
@@ -94,13 +121,39 @@ If the host-agent loader has NOT yet picked up the file this session
 
 Otherwise omit — agent already knows.
 
-### 5. Stop
+### 6. Stop
 
 Do NOT chain to other `/agents user *` commands. Do NOT commit.
 
+## Audit mode (`--audit`)
+
+Road-to-global-user-memory Phase 4. Renders what the GLOBAL layer
+currently holds — `profile.md`'s fields, the observation buffer's entry
+count and per-field counts, promotion candidates, and the revocation
+ledger's tombstone count — without the user reading raw JSONL. This is
+the global layer only; the project-local `.agent-user.md` never leaves
+the project it lives in, so there is nothing to audit for it here.
+
+1. Call
+   [`renderGlobalMemoryAudit()`](../../../../../src/scripts/_lib/user_global_memory_audit.ts).
+2. Print its `text` verbatim — every value it contains already passed
+   the same
+   [`knowledge_global_redaction.redaction_scan`](../../../../../src/scripts/_lib/knowledge_global_redaction.ts)
+   gate the write path runs; nothing here needs a second scan.
+3. If `revocationCount > 0`, add one line: "Run `/agents user delete
+   --show-revoked` to see what was deleted and why." (a stub for a
+   future `--show-revoked` flag; today the count is sufficient — the
+   full ledger is inspectable via
+   [`user_global_revocations.loadTombstones`](../../../../../src/scripts/_lib/user_global_revocations.ts)
+   for a maintainer who needs it).
+4. Stop. Do NOT chain to `--audit`'s own delete follow-up — hand the
+   user to [`/agents user delete`](delete.md) explicitly if they name
+   something to remove.
+
 ## Rules
 
-- Read-only. Never write `.agent-user.md` from this command.
+- Read-only. Never write `.agent-user.md` or the global `profile.md`
+  from this command — including `--audit` mode.
 - Never print fields the schema does not define — even if they exist
   in the file. (Forward-compat: an unexpected field is a warning, not
   a render target.)
@@ -110,6 +163,6 @@ Do NOT chain to other `/agents user *` commands. Do NOT commit.
 
 ## See also
 
-- Schema: [`agent-user-schema`](../../../../../../../../../../../docs/contracts/agent-user-schema.md).
+- Schema: [`agent-user-schema`](../../../../../docs/contracts/agent-user-schema.md) — see § Global profile layer for the merge rule this command renders, and § Delete, revoke, and audit for `--audit`'s contract.
 - Parent: [`/agents user`](../user.md).
-- Sibling: [`/agents user init`](init.md), [`/agents user update`](update.md).
+- Sibling: [`/agents user init`](init.md), [`/agents user update`](update.md), [`/agents user delete`](delete.md) — the delete/revoke counterpart `--audit` informs.

package/dist/agent-src/commands/agents/user/update.md

@@ -61,7 +61,7 @@ When called with `--validate` (or after the user confirms "done"):
 
 1. Read `.agent-user.md`.
 2. Parse frontmatter; check every required field per
-   [`agent-user-schema § Field reference`](../../../../../../../docs/contracts/agent-user-schema.md#field-reference).
+   [`agent-user-schema § Field reference`](../../../../../docs/contracts/agent-user-schema.md#field-reference).
 3. Check file size ≤100 lines.
 4. Run the privacy-floor scan (same as `init` step 4): credentials,
    third-party PII, financial figures, health/legal status.
@@ -99,6 +99,6 @@ Do NOT commit. Do NOT chain to another `/agents user *` command.
 
 ## See also
 
-- Schema: [`agent-user-schema`](../../../../../../../docs/contracts/agent-user-schema.md).
+- Schema: [`agent-user-schema`](../../../../../docs/contracts/agent-user-schema.md).
 - Parent: [`/agents user`](../user.md).
 - Sibling: [`/agents user init`](init.md), [`/agents user show`](show.md), [`/agents user review`](review.md).

package/dist/agent-src/commands/agents/user.md

@@ -25,6 +25,18 @@ Sub-dispatcher for the user-persona file
 single, project-root, gitignored Markdown file that captures who the
 user is and how they want the agent to address them.
 
+Since ADR-138, a weaker global layer
+(`~/.event4u/agent-config/user/profile.md`) sits beneath the
+project-local file — see
+[`agent-user-schema.md § Global profile layer`](../../../docs/contracts/agent-user-schema.md#global-profile-layer-adr-138)
+for the merge rule. `init` and `update` operate on the **project-local**
+file only; `review` and `accept` cover BOTH layers' observation buffers
+(road-to-global-user-memory Phase 2/3); `show` renders the merged,
+effective profile by default, or the global layer's raw holdings with
+`--audit`; `delete` removes something the global learning channel wrote
+— an observation, a project's worth of observations, or a promoted
+profile field — with a tombstone in every case (Phase 4).
+
 **Why this is its own cluster:** `AGENTS.md` describes the *project*
 to the agent. `.agent-user.md` describes the *user* to the agent.
 Two distinct primitives — same `/agents` family for discoverability,
@@ -35,10 +47,11 @@ separate sub-commands for separation of concerns.
 | Sub-sub-command | Routes to | Purpose |
 |---|---|---|
 | `/agents user init` | `commands/agents/user/init.md` | Short interview → creates `.agent-user.md` |
-| `/agents user show` | `commands/agents/user/show.md` | Read-only render of the persona |
-| `/agents user review` | `commands/agents/user/review.md` | List buffered observations from `.agent-user.observations.jsonl` |
-| `/agents user accept` | `commands/agents/user/accept.md` | Apply a buffered observation with confirmation |
+| `/agents user show` | `commands/agents/user/show.md` | Read-only render of the persona; `--audit` renders the global layer's raw holdings |
+| `/agents user review` | `commands/agents/user/review.md` | List buffered observations from both the project-local and the global buffer |
+| `/agents user accept` | `commands/agents/user/accept.md` | Apply a buffered observation (either layer) with confirmation |
 | `/agents user update` | `commands/agents/user/update.md` | Open in IDE for manual edit; validate on save |
+| `/agents user delete` | `commands/agents/user/delete.md` | Delete an observation, purge a project's observations, or revoke a profile field — with a tombstone |
 
 Schema contract:
 [`docs/contracts/agent-user-schema.md`](../../../docs/contracts/agent-user-schema.md).
@@ -62,7 +75,7 @@ Schema contract:
 - **Do NOT introduce network code** in this package. External
   enrichment is rejected for v1 — see the
   [determinism floor](../../../docs/contracts/agent-user-schema.md#determinism-floor).
-- **Edit `.agent-src.uncondensed/` only.** `dist/agent-src/` and
+- **Edit `src/` only.** `dist/agent-src/` and
   `.augment/` regenerate from source.
 
 ## See also

package/dist/agent-src/commands/agents.md

@@ -64,5 +64,5 @@ Sub-command names match the locked contract in
 - **Do NOT chain sub-commands.** One `/agents <sub>` per turn.
 - If the user invokes `/agents` with no argument, **show the menu** — do
   not guess which sub-command they meant.
-- **Edit `.agent-src.uncondensed/` only.** `dist/agent-src/` and `.augment/`
+- **Edit `src/` only.** `dist/agent-src/` and `.augment/`
   regenerate from source.

package/dist/agent-src/commands/check-current-md.md

@@ -96,9 +96,9 @@ Apply all fixes** for ≤2 findings or when all are pure translations.
 
 Edit only the source-of-truth file:
 
-- Path under `.agent-src.uncondensed/` → edit there directly
+- Path under `src/` → edit there directly
 - Path under `dist/agent-src/` → edit the matching
-  `.agent-src.uncondensed/` file instead, then run
+  `src/` file instead, then run
   `bash scripts/condense.sh --sync`
 - Path under `.augment/` → same as `dist/agent-src/` (it's a projection)
 - Path under `agents/` → edit directly (no condensation layer)
@@ -109,21 +109,11 @@ After all fixes, re-run:
 ./scripts-run src/scripts/check_md_language <path> [<path> …]
 ```
 
-### 6. Mark hashes (only if `.agent-src.uncondensed/` was edited)
-
-For each modified source file:
-
-```bash
-./scripts-run src/scripts/condense --mark-done "{relative_path}"
-```
-
-This keeps `.condensation-hashes.json` consistent with the new content.
-
 ## Rules
 
 - **Never edit `.augment/` directly** — it's a generated projection.
   Per [`source-of-truth`](../rules/source-of-truth.md),
-  the source is `.agent-src.uncondensed/`.
+  the source is `src/`.
 - **Per-line ignore marker is reserved** for meta-documentation that
   must quote German tokens; do NOT use it as a generic mute.
 - **Frontmatter is exempt** — the checker skips YAML frontmatter at