@event4u/agent-config 1.19.0 → 1.21.0

package/scripts/update_prices.py

@@ -1,5 +1,5 @@
 #!/usr/bin/env python3
-"""Refresh `.agent-prices.md` from the LiteLLM model-prices feed.
+"""Refresh `agents/.agent-prices.md` from the LiteLLM model-prices feed.
 
 Source: https://raw.githubusercontent.com/BerriAI/litellm/main/
         model_prices_and_context_window.json
@@ -9,7 +9,7 @@ Network failure or invalid response → fall back to
 always written. Stdlib only; no extra dependency.
 
 Usage:
-    python3 scripts/update_prices.py            # writes .agent-prices.md
+    python3 scripts/update_prices.py            # writes agents/.agent-prices.md
     python3 scripts/update_prices.py --check    # exit 1 if file is stale
 """
 
@@ -81,7 +81,7 @@ def _to_rows_from_litellm(payload: dict[str, dict[str, object]]) -> list[tuple[s
 
 
 def refresh(path: Path = PRICES_FILE) -> str:
-    """Write a fresh `.agent-prices.md`. Returns the source label used."""
+    """Write a fresh `agents/.agent-prices.md`. Returns the source label used."""
     payload = _fetch_litellm()
     if payload is not None:
         rows = _to_rows_from_litellm(payload)

package/scripts/validate_frontmatter.py

@@ -157,15 +157,55 @@ def _parse_yaml_block(body: str) -> dict[str, Any]:
 def _consume_block_list(lines: list[str], start: int) -> tuple[list[Any], int]:
     items: list[Any] = []
     i = start
+    item_indent: int | None = None
     while i < len(lines):
         line = lines[i]
         if not line.strip():
             i += 1
             continue
         stripped = line.lstrip()
+        leading = len(line) - len(stripped)
         if not stripped.startswith("- "):
+            # Out of the list — caller resumes.
             break
-        items.append(_coerce(stripped[2:]))
+        if item_indent is None:
+            item_indent = leading
+        elif leading != item_indent:
+            break
+        item_body = stripped[2:].strip()
+        # Inline mapping inside the list: `- key: value`
+        m = re.match(r"^([\w-]+):\s*(.*)$", item_body)
+        if m:
+            mapping: dict[str, Any] = {}
+            key = m.group(1)
+            raw = m.group(2).strip()
+            mapping[key] = _coerce(raw) if raw != "" else ""
+            # Consume continuation lines that are indented past the dash —
+            # they belong to the same mapping item (`pattern: …`, `reason: …`).
+            cont_indent = item_indent + 2  # `- ` is two chars
+            i += 1
+            while i < len(lines):
+                cont = lines[i]
+                if not cont.strip():
+                    i += 1
+                    continue
+                cont_stripped = cont.lstrip()
+                cont_leading = len(cont) - len(cont_stripped)
+                if cont_stripped.startswith("- "):
+                    break
+                if cont_leading <= item_indent:
+                    break
+                cm = re.match(r"^([\w-]+):\s*(.*)$", cont_stripped)
+                if cm and cont_leading >= cont_indent:
+                    ckey = cm.group(1)
+                    cval = cm.group(2).strip()
+                    mapping[ckey] = _coerce(cval) if cval != "" else ""
+                    i += 1
+                else:
+                    break
+            items.append(mapping)
+            continue
+        items.append(_coerce(item_body))
         i += 1
     return items, i - start
 

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

@@ -1,126 +0,0 @@
----
-name: chat-history:checkpoint
-cluster: chat-history
-sub: checkpoint
-description: Append a phase-boundary entry to .agent-chat-history — CHECKPOINT fallback for platforms without a native hook (Augment IDE, Cursor pre-1.7, Cline non-Mac/Linux). ~1s.
-disable-model-invocation: true
-suggestion:
-  eligible: true
-  trigger_description: "User wants to flush a chat-history phase boundary on a CHECKPOINT-class platform (Augment IDE, Cursor < 1.7, Cline on Windows) — phrases like 'checkpoint chat history', 'log a phase boundary', 'manual chat-history append'."
-  trigger_context: "chat_history.path == checkpoint AND a phase-shaped boundary just completed (decision recorded, multi-tool sequence finished, task-list item closed)."
----
-<!-- cloud_safe: noop -->
-
-# /chat-history checkpoint
-Force-append a `phase`-typed entry to `.agent-chat-history`. CHECKPOINT
-fallback for platforms without native hooks — see
-[`agents/contexts/chat-history-platform-hooks.md`](../../../agents/contexts/chat-history-platform-hooks.md)
-for the per-platform classification.
-
-Use this at decision points, end of phase, or after a meaningful tool
-sequence on a CHECKPOINT/MANUAL platform. On HOOK platforms (Claude
-Code, Augment CLI, Cursor 1.7+, Cline non-Windows, Windsurf, Gemini
-CLI), the platform fires hooks automatically — manual use is allowed
-but rarely needed.
-
-## When to use
-
-- IDE plugin without hooks (Augment Code IDE plugin as of 2026-04-30).
-- Long-running tool sequence on any platform that did not flush.
-- Explicit phase-boundary marker after a multi-tool refactor.
-- Crash-recovery rehearsal — verifies the append path works before a
-  real outage.
-
-## When NOT to use
-
-- HOOK platform mid-session — the platform already records turn-level
-  cadence; an extra checkpoint just adds noise.
-- After every line of agent output — that's `per_turn` cadence and is
-  configured in `.agent-settings.yml`, not via this command.
-- To inspect the log → [`/chat-history`](chat-history.md).
-- To wipe the log → [`/chat-history-clear`](chat-history-clear.md).
-- To reload the log into context → [`/chat-history-resume`](chat-history-resume.md).
-
-## 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).
-> Nothing to checkpoint. Enable in .agent-settings.yml first.
-```
-
-### 2. Determine the phase label
-
-Pick a short label (2–6 words) that names what just happened:
-
-- "phase-1-done", "refactor-extracted", "tests-green",
-  "review-comments-fixed", "merge-ready".
-
-If the user invoked the command without context, ask once with
-numbered options per [`user-interaction`](../rules/user-interaction.md):
-
-```
-> 1. Use a free-text label — type 2–6 words for the checkpoint
-> 2. Use a generic "manual-checkpoint" label
-> 3. Skip — close without writing
-```
-
-### 3. Append the checkpoint
-
-Invoke the master CLI:
-
-```
-./agent-config chat-history:checkpoint \
-  --first-user-msg "<the conversation's first user message>" \
-  --payload '{"phase": "<label>"}'
-```
-
-The wrapper delegates to `scripts/chat_history.py hook-append --event phase`,
-which performs cadence filtering and ownership checks. Cadence is read
-from `chat_history.frequency` in `.agent-settings.yml` — `per_turn` /
-`per_phase` / `per_tool`. `per_tool` cadence drops the `phase` event;
-say so explicitly if that is the active mode.
-
-### 4. Confirm
-
-Render a one-line confirmation, mirroring the user's language:
-
-```
-> 📒 Checkpoint logged: <label>  (entries: N → N+1)
-```
-
-If the helper returned `skipped_cadence`, surface it:
-
-```
-> 📒 Checkpoint skipped — current cadence is per_tool, phase events are dropped.
-> Switch chat_history.frequency to per_phase or per_turn to capture phase boundaries.
-```
-
-## Gotchas
-
-- The command writes through the same ownership-state machine as
-  hooks — a `foreign` log triggers the
-  [`chat-history`](../rules/chat-history-ownership.md) Foreign-Prompt before any
-  append. This is intentional; the checkpoint must not silently
-  hijack another session's log.
-- The `phase` payload key is required. Other keys are accepted but
-  ignored by the JSONL schema (forward-compat — they may be promoted
-  to first-class fields later).
-- On HOOK platforms, hook entries and checkpoint entries coexist
-  cleanly. The schema does not deduplicate; if you checkpoint
-  immediately after a hook fires, expect two adjacent entries with
-  different `source` values.
-
-## See also
-
-- [`chat-history`](../rules/chat-history-ownership.md) — the rule defining the
-  conditional Iron Law (HOOK platforms vs CHECKPOINT/MANUAL platforms)
-- [`/chat-history`](chat-history.md) — read-only status display
-- [`/chat-history-resume`](chat-history-resume.md) — adopt + load
-- [`/chat-history-clear`](chat-history-clear.md) — wipe
-- [`agents/contexts/chat-history-platform-hooks.md`](../../../agents/contexts/chat-history-platform-hooks.md) — per-platform strategy table
-- [`scripts/chat_history.py`](../../../scripts/chat_history.py) — `hook-append` API

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

@@ -1,103 +0,0 @@
----
-name: chat-history:clear
-cluster: chat-history
-sub: clear
-description: Manually delete the persistent chat-history log — asks for confirmation, optionally archives to a timestamped backup before wiping
-disable-model-invocation: true
-suggestion:
-  eligible: false
-  rationale: "Destructive log wipe — must be deliberate."
----
-<!-- cloud_safe: noop -->
-
-# /chat-history clear
-Wipes `.agent-chat-history`. Use when the log is stale (wrong session),
-bloated beyond usefulness, or contains information you do not want
-persisted on disk.
-
-This command is **destructive** — always asks for confirmation before
-touching the file, unless the file does not exist in the first place.
-
-## When NOT to use
-
-- Inspect before deleting → [`/chat-history`](chat-history.md).
-- Keep the entries but re-point the header → [`/chat-history-resume`](chat-history-resume.md).
-- Disable logging entirely → set `chat_history.enabled: false` in
-  `.agent-settings.yml`; see
-  [`layered-settings`](../../docs/guidelines/agent-infra/layered-settings.md#section-aware-merge-rules).
-  Disabling does not delete the existing file; run this command
-  afterwards if you also want it gone.
-
-## Steps
-
-### 1. Check current state
-
-Run `scripts/chat_history.py status`. If `exists: false`, tell the user
-and stop:
-
-```
-> 📒 No .agent-chat-history to clear.
-```
-
-### 2. Show what is about to be deleted
-
-Render a short preview so the user sees what they are wiping:
-
-```
-> 📒 About to clear .agent-chat-history
->
-> Size:       {size_kb} KB
-> Entries:    {entries}
-> Session:    {short_fp}  (started {created_at_relative})
->
-> 1. Archive — rename to .agent-chat-history.{YYYYMMDD-HHMMSS}.bak, then start fresh
-> 2. Delete — permanent, no backup
-> 3. Cancel — keep the file as-is
-```
-
-### 3. Act on the choice
-
-- `1` (Archive) → `mv .agent-chat-history
-  .agent-chat-history.{timestamp}.bak`. The rule will create a fresh
-  file on the next append.
-- `2` (Delete) → run `scripts/chat_history.py clear`. Permanent.
-- `3` (Cancel) → stop. Make no changes.
-
-Free-text replies ("abbrechen", "keep it", "nevermind") count as `3`.
-An unrecognized reply also counts as `3` — never delete on ambiguous
-input.
-
-### 4. Confirm
-
-After a successful archive or delete, print a one-line confirmation:
-
-```
-> 📒 Archived to .agent-chat-history.{timestamp}.bak
-```
-
-or
-
-```
-> 📒 .agent-chat-history deleted.
-```
-
-Do **not** re-enable logging or change `.agent-settings.yml` as a side
-effect — this command is scoped to the file on disk only.
-
-## Gotchas
-
-- `.agent-chat-history.*.bak` files are also git-ignored by the
-  installer's `.gitignore` block. They accumulate if archived often —
-  users can delete them manually.
-- If `chat_history.enabled: false`, the file will **not** be recreated
-  after clearing. That is usually fine, but mention it so the user
-  knows the log is now silent.
-- Deletion cannot be undone. When in doubt, prefer option `1` (Archive).
-
-## See also
-
-- [`chat-history`](../rules/chat-history-ownership.md) — the rule that writes the file
-- [`/chat-history`](chat-history.md) — status inspection
-- [`/chat-history-resume`](chat-history-resume.md) — load + adopt instead of wipe
-- [`agent-settings` template](../templates/agent-settings.md) — `chat_history.*` reference
-- [`scripts/chat_history.py`](../../../scripts/chat_history.py) — helper API

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

@@ -1,183 +0,0 @@
----
-name: chat-history:resume
-cluster: chat-history
-sub: resume
-description: Load the persistent chat-history log into the current conversation — picks match/returning/foreign flow and supports resume, merge, replace, or continue
-disable-model-invocation: true
-suggestion:
-  eligible: false
-  rationale: "Explicit resume mechanic with foreign/returning state machine."
----
-<!-- cloud_safe: noop -->
-
-# /chat-history resume
-Reconnects the current conversation with an existing `.agent-chat-history`
-file. Depending on the 4-state ownership check, it routes to the right
-flow: silent summarize, adopt, merge, or replace.
-
-Use after a crashed chat, after switching tools (Augment → Claude Code),
-or when the agent showed the foreign- or returning-session prompt from
-the [`chat-history`](../rules/chat-history-ownership.md) rule and the user picked
-"resume".
-
-## When NOT to use
-
-- Just inspect metadata → [`/chat-history`](chat-history.md).
-- Start fresh instead of resuming → [`/chat-history-clear`](chat-history-clear.md)
-  or pick "New start" in the foreign prompt.
-- Logging is disabled (`chat_history.enabled: false`) → enable it in
-  `.agent-settings.yml` first; this command refuses to run otherwise.
-
-## Preconditions
-
-- `.agent-settings.yml` exists and `chat_history.enabled: true`.
-- `.agent-chat-history` exists at the project root.
-
-If either is missing, tell the user and stop — do not create files here.
-
-## Steps
-
-### 1. Load status
-
-Run `scripts/chat_history.py status`. If `exists: false` or
-`entries: 0`, tell the user there is nothing to resume and stop.
-
-### 2. Determine ownership state
-
-Run `scripts/chat_history.py state --first-user-msg "<current first user
-message>"`. Branch on the result:
-
-- `match` → step 3a (already owner)
-- `returning` → step 3b (pick Merge / Replace / Continue)
-- `foreign` → step 3c (pick Resume / New start / Ignore)
-- `missing` → header corrupt; tell the user and suggest
-  `/chat-history-clear` to start fresh. Stop.
-
-### 3a. `match` — already owner
-
-Nothing to adopt. Skip to step 4 (summarize) for the user's benefit.
-
-### 3b. `returning` — this chat once owned the file
-
-Another session took over. Present the Returning-Prompt from the rule
-and wait for a number:
-
-```
-> 📒 Welcome back. This chat once owned the history file; another
-> session has written to it since.
->
-> On-file entries: {N}   Size: {X} KB
->
-> 1. Merge — my in-memory history first, the foreign entries after
-> 2. Replace — wipe the foreign entries, keep only my history
-> 3. Continue — leave the file as-is; only new entries from now on
-```
-
-- **1 (Merge)** — build the in-memory entries list (see below), then:
-  ```bash
-  scripts/chat_history.py prepend --entries-json '<list>'
-  scripts/chat_history.py adopt --first-user-msg "<msg>"
-  ```
-- **2 (Replace)** — build the in-memory entries list, then:
-  ```bash
-  scripts/chat_history.py reset --first-user-msg "<msg>" \
-    --freq <frequency> --entries-json '<list>'
-  ```
-- **3 (Continue)** —
-  ```bash
-  scripts/chat_history.py adopt --first-user-msg "<msg>"
-  ```
-
-### 3c. `foreign` — new chat finds an unknown session's file
-
-Present the Foreign-Prompt from the rule and wait for a number:
-
-```
-> 📒 Found chat history from an unknown session.
->
-> Entries on file: {N}   Size: {X} KB
->
-> 1. Resume — adopt this file, load entries as context, keep appending
-> 2. New start — archive to .agent-chat-history.bak, init fresh
-> 3. Ignore — leave the file untouched, disable logging for this session
-```
-
-- **1 (Resume)** — `adopt --first-user-msg "<msg>"`.
-- **2 (New start)** — rename file to `.agent-chat-history.bak`, run
-  `init --first-user-msg "<msg>" --freq <frequency>`. Skip summary.
-- **3 (Ignore)** — do nothing. Report that logging is off for this
-  conversation. Stop.
-
-### 3d. Building the in-memory entries list (Merge / Replace)
-
-Reconstruct the agent's prior turns as a JSON array:
-
-- one `{"t":"user","text":"<preview>","ts":"<iso>"}` per user message
-- one `{"t":"agent","text":"<preview>","ts":"<iso>"}` per agent reply
-- `text` previews capped at ~200 chars (whitespace flattened)
-- timestamps in ISO-8601 UTC (current time is acceptable if exact times
-  are unknown; order is what matters)
-- no tool-call payloads, no file contents, no secrets
-
-If the list is large (>30 KB), stream it via stdin:
-`prepend --entries-stdin` or `reset --entries-stdin`.
-
-### 4. Overflow check
-
-After any Merge or Replace, run
-`scripts/chat_history.py rotate --max-kb <max_size_kb>
---mode <on_overflow>` so the combined body stays within the user's
-budget.
-
-### 5. Summarize into conversation context
-
-Read the entries via the helper (`read --all` or `read --last N` for
-bounded). Produce a short, structured summary — **not** a verbatim dump:
-
-```
-> 📒 Resumed chat-history ({entries} entries, {age})
->
-> ## What was done
-> - {1–3 bullets from agent/decision entries}
->
-> ## Open threads
-> - {1–3 bullets from the most recent entries and any pending questions}
->
-> ## Key decisions
-> - {decisions captured during the prior session}
->
-> Ready to continue. What would you like to do?
-```
-
-Keep the summary under ~25 lines. Rationale: this is input into the new
-turn, not a display artifact (see
-[`token-efficiency`](../rules/token-efficiency.md)).
-
-### 6. Hand control back to the user
-
-After presenting the summary, stop and wait. Do not auto-resume work —
-the user decides what to do next.
-
-## Gotchas
-
-- **Iron law — one question at a time.** Even if the log contains
-  several open threads, ask about one at a time after the summary
-  (see [`ask-when-uncertain`](../rules/ask-when-uncertain.md)).
-- `adopt` rewrites the header in place and pushes the previous fp into
-  `former_fps` (capped at 10). No backup is created — use
-  `/chat-history-clear` first if you want a clean slate.
-- `reset` discards whatever was on disk. Only use it when the user
-  explicitly picks "Replace".
-- The summary is derived from the agent's reading of the JSONL. Old
-  entries may be incomplete (especially under `per_turn` with
-  previews only). Flag gaps explicitly.
-
-## See also
-
-- [`chat-history`](../rules/chat-history-ownership.md) — the rule that triggers
-  this command via the foreign- and returning-session prompts
-- [`/chat-history`](chat-history.md) — status inspection without adopting
-- [`/chat-history-clear`](chat-history-clear.md) — wipe instead of adopt
-- [`/agent-handoff`](agent-handoff.md) — complementary: generates a
-  paste-into-new-chat prompt (no disk file)
-- [`scripts/chat_history.py`](../../../scripts/chat_history.py) — helper API

package/.agent-src/contexts/communication/rules-auto/artifact-engagement-recording-mechanics.md

@@ -1,72 +0,0 @@
-# Artifact Engagement Recording — mechanics
-
-CLI invocation, privacy contract, failure-mode handling, and "what
-this rule does NOT do" catalog for the
-[`artifact-engagement-recording`](../../../rules/artifact-engagement-recording.md)
-rule. The activation gate, cadence table, and consulted-vs-applied
-definitions live in the rule; this file is the lookup material for
-the actual `telemetry:record` call and the privacy floor.
-
-## What to record — id-only, no payload
-
-```bash
-./agent-config telemetry:record \
-  --task-id "$TASK_ID" \
-  --boundary task \
-  --consulted skills:php-coder \
-  --consulted skills:eloquent \
-  --consulted rules:scope-control \
-  --applied skills:php-coder \
-  --applied rules:scope-control
-```
-
-- `--task-id` — the ticket key (`PROJ-123`) for `/implement-ticket`, or a
-  short opaque slug derived from the prompt for `/work`. **Never** a
-  branch name, a file path, or a free-text title.
-- `--boundary` — `task` or `phase-step`, matching the cadence in the rule.
-- `--consulted <kind>:<id>` — repeat per artefact. `<kind>` is one of
-  `skills`, `rules`, `commands`, `guidelines`, `personas`.
-- `--applied <kind>:<id>` — repeat per artefact actually applied.
-- Exit `0` always when disabled (silent). Exit `1` on schema validation
-  failure (rule must NOT swallow this — surface to the user). Exit `2`
-  on IO failure.
-
-## Privacy contract — what NEVER goes into a record
-
-The CLI rejects most violations on the input boundary, but the agent must
-not even attempt these:
-
-- ❌  File paths (`src/Foo.php`, `tests/...`) — id fields are
-  artefact identifiers only.
-- ❌  Source code, prompt text, ticket body, AC text.
-- ❌  Branch names, commit shas, PR numbers, URLs.
-- ❌  Secrets, env vars, credentials, customer data.
-- ❌  Free-text strings longer than 200 chars (CLI enforces; agent must
-  not generate).
-
-When in doubt → **don't record**. A missing event is cheap; a leaked
-prompt is not.
-
-## Failure modes — DO NOT block the user's task
-
-- Schema rejection (CLI exit `1`) → log the message internally, continue
-  the user's task. Do **not** halt the dispatch loop.
-- IO failure (CLI exit `2`) → same. The telemetry is **observation**, not
-  a delivery requirement.
-- Settings malformed → already handled by the CLI: it falls back to
-  disabled and exits `0`. Agent treats it as "disabled this task".
-
-The only error the agent surfaces is when the user explicitly asked for
-recording (`telemetry:status` confirms enabled) but no event reached the
-log — that is a real bug, not a swallowed error.
-
-## What this rule does NOT do
-
-- Run when `enabled: false` (cost floor is zero — see
-  [`tests/telemetry/test_cost_floor.py`](../../../../tests/telemetry/test_cost_floor.py)).
-- Track the agent's tool calls, file reads, or token spend — that is
-  out of scope, see the roadmap's "out-of-scope" section.
-- Decide retirement. Phase 4's aggregator + report renderer are the only
-  consumers that may interpret the JSONL.
-- Run on cloud surfaces (Claude.ai Web, Skills API). The
-  `cloud_safe: noop` marker keeps it inert there.

package/.agent-src/contexts/communication/rules-auto/augment-portability-mechanics.md

@@ -1,79 +0,0 @@
-# Augment portability — mechanics
-
-`task`-to-script translation table, the `./agent-config` consumer-CLI
-table, and the rationale behind both for the
-[`augment-portability`](../../../rules/augment-portability.md) rule.
-The portability obligation, the agnostic-content rules, and the
-enforcement script reference live in the rule; this file is the
-lookup material when an agent is about to write or edit an artefact
-that mentions a runtime invocation.
-
-## Why no `task` commands inside artefacts
-
-Skills, rules, commands, guidelines, personas, and context docs
-shipped by this package run in **consumer projects**. Consumer
-projects may not have [Task](https://taskfile.dev) installed —
-they might use npm scripts, Composer scripts, Make, or nothing at
-all. A skill that instructs an agent to run `task <something>`
-silently breaks in every project without a `Taskfile.yml`.
-
-Task remains a convenience shortcut for maintainers working on the
-package repo itself — `task ci` is the recommended local gate before
-a PR and lives in `Taskfile.yml`, `AGENTS.md`, and the package README.
-Those maintainer-facing surfaces are outside the scope of this rule.
-Artefact files must assume Task is absent.
-
-The detection pattern *"if the consumer has a `Makefile` / build
-script, prefer its targets over raw commands"* is still allowed when
-the skill adapts to the **consumer's own** tooling (e.g.
-`tests-execute` detecting `php artisan test` vs `vendor/bin/pest`).
-It is not allowed to reference `task <name>` as the detected target —
-every direct invocation must resolve to a real script path.
-
-## Translation table — `task` → script
-
-| ❌ Forbidden | ✅ Portable |
-|---|---|
-| `task sync` | `bash scripts/compress.sh --sync` |
-| `task sync-check` | `bash scripts/compress.sh --check` |
-| `task sync-check-hashes` | `bash scripts/compress.sh --check-hashes` |
-| `task sync-changed` | `bash scripts/compress.sh --changed` |
-| `task sync-mark-done -- X` | `bash scripts/compress.sh --mark-done X` |
-| `task generate-tools` | `python3 scripts/compress.py --generate-tools` |
-| `task lint-skills` | `python3 scripts/skill_linter.py --all` |
-| `task check-refs` | `python3 scripts/check_references.py` |
-| `task check-portability` | `python3 scripts/check_portability.py` |
-| `task check-compression` | `python3 scripts/check_compression.py` |
-| `task validate-schema` | `python3 scripts/validate_frontmatter.py` |
-| `task counts-check` | `python3 scripts/update_counts.py --check` |
-| `task roadmap-progress` | `./agent-config roadmap:progress` |
-| `task ci` | run each underlying script directly (no single portable equivalent) |
-
-## Consumer CLI — `./agent-config`
-
-A subset of package scripts is exposed through a project-local CLI
-wrapper `./agent-config` (written into the project root by the
-installer, gitignored). Artefacts MUST prefer the CLI over raw
-`python3 scripts/…` paths for every command the CLI already covers,
-because the raw paths only resolve inside the package repo — in a
-consumer project the scripts live under `node_modules/` or `vendor/`.
-
-| ❌ Forbidden in artefacts | ✅ Portable |
-|---|---|
-| `python3 scripts/mcp_render.py` | `./agent-config mcp:render` |
-| `python3 scripts/mcp_render.py --check` | `./agent-config mcp:check` |
-| `python3 .augment/scripts/update_roadmap_progress.py` | `./agent-config roadmap:progress` |
-| `python3 .augment/scripts/update_roadmap_progress.py --check` | `./agent-config roadmap:progress-check` |
-| `bash scripts/first-run.sh` | `./agent-config first-run` |
-| `PYTHONPATH=… python3 -m implement_ticket` | `./agent-config implement-ticket` |
-| `python3 scripts/memory_lookup.py` | `./agent-config memory:lookup` |
-| `python3 scripts/memory_signal.py` | `./agent-config memory:signal` |
-| `python3 scripts/memory_hash.py` | `./agent-config memory:hash` |
-| `python3 scripts/check_memory.py` | `./agent-config memory:check` |
-| `python3 scripts/check_memory_proposal.py` | `./agent-config memory:check-proposal` |
-| `python3 scripts/check_proposal.py` | `./agent-config proposal:check` |
-| `python3 scripts/refine_ticket_detect.py` | `./agent-config refine-ticket:detect` |
-
-Commands not covered by the CLI stay as direct script invocations
-(e.g. `bash scripts/compress.sh --sync`) — those are maintainer-only
-and not reachable from a consumer project anyway.