@event4u/agent-config 14.23.0 → 15.0.0

package/dist/agent-src/commands/chat-history/import.md

@@ -1,170 +0,0 @@
----
-model_tier: medium
-name: chat-history-import
-pack: memory
-visibility: internal
-cluster: chat-history
-sub: import
-description: Surface prior chat-history sessions as a numbered table, let the user pick one, read it silently, and emit a short summary plus a resume offer — selective, user-driven cross-session import
-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)."
-workspaces:
-  - agent-config-maintainer
-packs:
-  - memory
----
-<!-- cloud_safe: noop -->
-
-# /chat-history import
-
-Read-only, **user-driven** cross-session import. Surfaces prior
-sessions logged in `agents/runtime/.agent-chat-history` as a numbered table,
-the user picks **one**, the agent reads that session **silently**
-and emits a 2–5 sentence summary, then offers to resume the last
-task from that session. The agent does **not** render entries
-verbatim, auto-import, or rewrite the user's context without an
-explicit instruction.
-
-This is the opt-in counterpart to the read-path filter (Phase 3 of
-`road-to-chat-history-session-isolation`): default reads stay
-session-scoped; `import` is the explicit surface for crossing the
-session boundary. For project-improving learnings derived from a
-prior session, see [`/memory mine-session --mode=proposals`](../memory/mine-session/command.md).
-
-## When NOT to use
-
-- Inspect the current session — use the host's native transcript /
-  session view, or `./scripts-run scripts/chat_history read`.
-- Generate a learning proposal from a prior session — use
-  [`/memory mine-session --mode=proposals`](../memory/mine-session/command.md),
-  which frames the session's signals and runs `learning-to-rule-or-skill`.
-- Bulk-import all sessions — out of scope for v1. One session per
-  invocation; multi-pick is v2.
-- Search prior sessions by content — out of scope for v1; no fuzzy
-  search, no full-text grep. The user picks by `last_ts` and
-  `summary` from the listing.
-
-## Steps
-
-### 1. Check if enabled
-
-Read `chat_history.enabled` from `.agent-settings.yml`. If `false`
-or the section is missing, say so and stop:
-
-```
-> 📒 chat-history is disabled (chat_history.enabled = false).
-> Set it to true in .agent-settings.yml to start logging.
-```
-
-### 2. List sessions
-
-Run `./scripts-run scripts/chat_history sessions --json --limit 20 --summary`.
-The helper returns an array of
-`{id, count, first_ts, last_ts, preview, summary}` sorted by
-`last_ts` desc. The `summary` field is built **inside the helper**
-from at most 10 sampled entries per session (5 oldest + 5 newest) —
-token-cheap, no need to ever read the full body for the picker.
-Default excludes empty buckets — only sessions with at least one
-body entry are surfaced.
-
-If the array is empty, stop:
-
-```
-> 📒 No prior sessions found in agents/runtime/.agent-chat-history.
-```
-
-### 3. Surface as a numbered table
-
-Render the sessions as a markdown table — the row number is the
-option (per `user-interaction` Iron Law: numbered options for any
-picker). The session `id` is noise to humans; keep it **internal**
-for step 5's `read --session <id>` call and never render it.
-Format:
-
-```
-Pick a session to import:
-
-| #  | Date             | Entries | Summary |
-|----|------------------|---------|---------|
-| 1  | YYYY-MM-DD HH:MM | N       | {summary} |
-| 2  | YYYY-MM-DD HH:MM | N       | {summary} |
-| …  |                  |         |           |
-| N  | —                | —       | abort — do not read any session |
-```
-
-Format the timestamp as `YYYY-MM-DD HH:MM` (drop seconds and
-timezone — the listing is for orientation, not forensics). Lead the
-`Summary` cell with the helper's `summary` field — that is the
-rough arc the user picks by (`<first user msg> → <last user msg>`
-for normal sessions, or `(N entries — no user prompts; t-mix: …)`
-for tool-only sessions). Do **not** truncate or rewrite `summary` —
-markdown table wrap handles long values. Always include an explicit
-`abort` row as the last numbered option. Track option-number → `id`
-internally so step 5 can call `./scripts-run scripts/chat_history read
---session <id>` with the right id.
-
-### 4. Wait for the pick
-
-**One question per turn** (per `ask-when-uncertain`). Do not chain
-the listing with anything else; do not auto-pick; do not surface a
-default. Wait for the user's response.
-
-If the user picks the abort option, stop without reading.
-
-### 5. Read the picked session silently
-
-Run `./scripts-run scripts/chat_history read --session <id> --last <count>`,
-where `<count>` is the picked row's `count` from step 2. The
-`--last` flag is **required** — the helper defaults to 5 entries,
-which would silently truncate any longer session. The helper returns
-the entries as JSON.
-
-**Do not render the entries.** The verbose dump was reversed by the
-user — token cost and scroll fatigue outweighed the verbatim
-contract. Read the JSON in-context, then proceed to step 6.
-
-### 6. Summarise and offer to resume
-
-Emit a **2–5 sentence** summary of the picked session: the topic,
-what was decided or built, and where it left off (the last task in
-progress, if any). Plain prose — no bullets, no headings, no
-verbatim quotes.
-
-Then offer the resume choice as numbered options
-(per `user-interaction`), one question per turn:
-
-```
-1. resume — pick up the last task from that session
-2. stop — keep the summary in context, do nothing else
-```
-
-Wait for the pick. Do **not** auto-resume. If the user picks
-`resume`, hand off to the relevant skill or command for that work;
-do not silently start editing files. The agent does not write to
-the current session's log on the user's behalf without an explicit
-instruction.
-
-## Gotchas
-
-- **Summary, not verbatim.** Earlier Council R2-2 favoured verbatim
-  rendering; reversed in practice — too slow, too token-expensive.
-  The agent reads the picked session in-context and emits a 2–5
-  sentence summary. Verbatim rendering is no longer part of the
-  contract.
-- **One pick per invocation.** Multi-pick is v2. If the user wants
-  a second session, run `/chat-history import` again.
-- **Read-only.** This command never writes to `agents/runtime/.agent-chat-history`
-  and never rotates.
-- **`<legacy>` and `<unknown>` buckets** show up like any other
-  session id when they have body entries — the user can pick them
-  too. The helper aggregates body entries with no `s` field into
-  `<legacy>` and entries with `s == "<unknown>"` into `<unknown>`.
-
-## See also
-
-- [`/memory mine-session --mode=proposals`](../memory/mine-session/command.md) — pick a prior session and turn it into a project-improving proposal via `learning-to-rule-or-skill` (the former `/chat-history learn`)
-- [`chat-history-platform-hooks`](../../../agents/settings/contexts/chat-history-platform-hooks.md) — read contract, isolation default, opt-in cross-session path
-- [`scripts/chat_history.ts`](../../../scripts/chat_history.ts) — `sessions` and `read --session` CLI surface
-- [`user-interaction`](../../rules/user-interaction.md) — numbered-options Iron Law
-- [`ask-when-uncertain`](../../rules/ask-when-uncertain.md) — one-question-per-turn Iron Law

package/dist/agent-src/commands/chat-history.md

@@ -1,63 +0,0 @@
----
-model_tier: medium
-name: chat-history
-disable-model-invocation: true
-argument-hint: "[import]"
-pack: memory
-visibility: internal
-description: Chat-history orchestrator — routes to import (selective cross-session resume). Mining moved to /memory mine-session; raw-log inspection uses the host's native transcript view.
-cluster: chat-history
-routes_to: [chat-history-import]
-type: orchestrator
-suggestion:
-  eligible: true
-  trigger_description: "import a prior session into the current chat, resume a previous session, pull a prior session in verbatim"
-  trigger_context: "user wants to pull a prior session from the agents/runtime/.agent-chat-history log into the current chat verbatim and optionally resume it"
-workspaces:
-  - agent-config-maintainer
-packs:
-  - memory
----
-
-<!-- cloud_safe: noop -->
-
-# /chat-history
-
-Top-level orchestrator for the `/chat-history` family. Writes and overflow
-handling are driven entirely by platform hooks + `scripts/chat_history.ts`
-internals (`road-to-chat-history-hook-only`); the surfaced sub-command is
-read-only on the cross-host log (`agents/runtime/.agent-chat-history`).
-Sessions coexist in one log file — each entry self-tags via the `s` field —
-so there is no ownership layer to recover from.
-
-## Sub-commands
-
-| Sub-command | Routes to | Purpose |
-|---|---|---|
-| `/chat-history import` | `commands/chat-history/import.md` | List prior sessions, pick one, render its entries verbatim — selective cross-session import + resume |
-
-**Consolidated elsewhere** (see `road-to-memory-pipeline-consolidation.md`):
-
-- **Mining a session for learnings** — use
-  [`/memory mine-session --mode=proposals`](../memory/mine-session/command.md)
-  (the former `/chat-history learn`; now the single mining command, reading the
-  same cross-host log).
-- **Inspecting the raw log** (size, entries, header) — use the host's native
-  transcript / session view; the bespoke `/chat-history show` was dropped as
-  redundant.
-
-## Dispatch
-
-1. Parse the user's argument: `/chat-history <sub-command> [args]`.
-2. The only sub-command is `import`. Bare `/chat-history` (or an unknown
-   sub-command) → route to `import`.
-3. Load `commands/chat-history/import.md` and follow its `## Steps` verbatim
-   with the remaining args.
-
-## Rules
-
-- **Do NOT commit, push, or open a PR** — `import` is read-only (it renders a
-  prior session into the current chat; it writes nothing).
-- **Do NOT chain sub-commands.** One `/chat-history import` per turn.
-- **`import` crosses the session boundary** — only run it when the user
-  explicitly asked for cross-session reading.