@event4u/agent-config 14.16.0 → 14.17.0

package/dist/agent-src/skills/conventional-commits-writing/SKILL.md

@@ -1,7 +1,7 @@
 ---
 model_tier: medium
 name: conventional-commits-writing
-description: "When writing commit messages or squash-merge titles — `feat:`, `fix:`, `chore:`, scopes, breaking changes — even when the user just says 'commit this' without naming Conventional Commits."
+description: "When writing a commit message, branch name or squash title — measure the repo's own convention first, Conventional Commits as fallback — even on a bare 'commit this'."
 domain: process
 scope:
   write: []
@@ -22,6 +22,8 @@ packs:
 
 Use this skill when:
 
+- Committing in a repository whose conventions you have not established this
+  session — run `## Procedure: Establish the house convention` first
 - Generating a commit message from staged changes
 - Generating a squash merge title from a PR
 - Deciding the correct Conventional Commit type for a change
@@ -34,6 +36,217 @@ Do NOT use when:
 - The message is already correct and does not need review
 - Following the Git workflow (use `git-workflow` skill)
 
+## Procedure: Establish the house convention (run FIRST, before any message)
+
+Conventional Commits is this suite's **fallback**, not a universal truth. A
+repository that has demonstrably converged on another grammar gets that grammar;
+imposing the shipped default there produces commits that read as foreign in
+`git log` and in review. The precedence, highest first:
+
+| Tier | Source | Binding? |
+|---|---|---|
+| **1 — configured** | `commitlint.config.*` · `.gitmessage` · a `commit-msg` hook (husky / lefthook / `.git/hooks`) · `CONTRIBUTING.md` § Commits · a CI job that validates subjects · release automation that PARSES subjects (semantic-release, changesets, git-cliff, conventional-changelog) | yes — Class A, no approval needed |
+| **2 — measured + approved** | the consensus pass below, after the user says yes | yes, for this repository |
+| **3 — measured, unapproved** | the same pass before the user answers | **no — advisory**; report the mismatch, write Conventional |
+| **4 — default** | Conventional Commits | yes |
+
+Release automation is the trap that makes tier 1 outrank tier 2 even when the
+history disagrees: a repo whose `git log` is 85 % `[JIRA-123] Fix thing` but
+whose manifest (`package.json`, `composer.json`, `pyproject.toml`, `Cargo.toml`)
+runs `semantic-release` or its ecosystem equivalent is a repo **migrating toward**
+Conventional Commits, and the measurement is reading its past, not its intent.
+Check for the parser before you trust the prevalence.
+
+### 1. Look for tier 1 before measuring anything
+
+```bash
+ls commitlint.config.* .commitlintrc* .gitmessage .czrc 2>/dev/null
+git config --get commit.template
+ls .husky/commit-msg .git/hooks/commit-msg 2>/dev/null
+grep -rniE 'semantic-release|git-cliff|conventional-changelog|release-please|commitlint' \
+  package.json composer.json pyproject.toml Cargo.toml .github/workflows/ .gitlab-ci.yml \
+  2>/dev/null | head
+```
+
+**Every one of these produces candidates, not verdicts — open the file before
+you act on the hit.** A `commit.template` proves a template exists, not that it
+constrains the subject: a `.gitmessage` carrying only a body checklist ends
+nothing. `CONTRIBUTING.md` is prose and cannot be grepped for a convention —
+`grep -i commit` matches "please commit early and often" — so read its commits
+section if it has one and take the grammar from the sentences, not from the
+match. Only a **confirmed** source ends the procedure, and when it does, say
+which file answered.
+
+`changesets` is deliberately not in the parser list: it reads `.changeset/*.md`
+files and never parses a commit subject, so its presence says nothing about the
+convention. The four that do parse subjects — semantic-release, git-cliff,
+conventional-changelog, release-please — count only when the hit is a real
+dependency or a wired job, not a mention in a comment.
+
+The tier table above calls a confirmed hit Class A. That is exact for a machine
+-readable config and loose for `CONTRIBUTING.md`, which carries no digest and is
+read by a human judgement — treat a prose source as tier 1 in **precedence** and
+as a quoted sentence in the report, so the next reader can check it.
+
+### 2. Sample the history — native source per dimension
+
+Only **commit subjects** are reliably measurable from a clone. Branch names,
+PR titles and commit granularity have different native sources, and `unknown`
+is a valid, honest result for each:
+
+| Dimension | Native source | Measurable from a clone? |
+|---|---|---|
+| Subject grammar | `git log` | yes |
+| Branch naming | forge refs / `git branch -r` | partially — merged branches are often deleted |
+| PR title shape | forge API (`gh pr list`) | only with forge access |
+| Granularity (atomic vs batched) | per-commit diff stat | **no** where the repo squash-merges — the evidence was destroyed at merge |
+
+Resolve the trunk explicitly. `origin/HEAD` is set by `git clone` and is absent
+in a `git init` + `git remote add` checkout, in many CI checkouts and in
+worktrees, where the sample command would die rather than return nothing:
+
+```bash
+TRUNK=$(git symbolic-ref -q --short refs/remotes/origin/HEAD)
+[ -n "$TRUNK" ] || TRUNK=$(git rev-parse -q --verify origin/main >/dev/null && echo origin/main)
+[ -n "$TRUNK" ] || TRUNK=$(git rev-parse -q --verify origin/master >/dev/null && echo origin/master)
+[ -n "$TRUNK" ] || TRUNK=HEAD          # no remote at all: this checkout is the trunk
+git log "$TRUNK" --no-merges -n 200 --since='24 months ago' \
+  --pretty=format:'%H%x09%aN%x09%aE%x09%s'
+```
+
+**`--first-parent` is deliberately absent.** On a merge-commit workflow the
+trunk's first-parent chain is merge commits, which `--no-merges` then drops —
+the two together leave only what was committed straight to the trunk, which on
+a PR-based repo is nearly nothing. The convention lives in the feature commits,
+so walk the whole reachable history and exclude merges alone.
+
+The terminal `HEAD` matters as much as the first line: a chain that ends with an
+unset `TRUNK` hands `git log` an empty argument, which walks `HEAD` anyway —
+silently doing the right thing on a local repo while hiding that the resolution
+failed on one where it should not have.
+
+`%H` leads the format because two of the exclusions below need the commit, not
+just its subject. Drop, from the sample:
+
+- **bot authors** — `[bot]`, `dependabot`, `renovate`, `github-actions`,
+  `semantic-release`, `release-please`;
+- **automation subjects** — `^Revert `, `^Merge `, `chore(release)`,
+  `^Bump `, a bare `v?\d+\.\d+\.\d+`;
+- **bulk imports** — resolve with the hash the format carries:
+  `git show --stat --oneline <sha> | tail -1` and drop anything over 500 files.
+  Check this only for the handful of subjects that read like an import; running
+  it per commit costs 200 subprocesses to remove two rows.
+
+### 3. Classify each surviving subject
+
+Match in order, first hit wins. These are POSIX extended regular expressions,
+given outside a table because a markdown cell would need the alternation pipes
+escaped and `\|` in ERE is a literal pipe, not an alternation:
+
+```
+conventional      ^(build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test)(\([^)]+\))?!?: 
+ticket-prefix     ^\[[A-Z][A-Z0-9]+-[0-9]+\][: ]|^[A-Z][A-Z0-9]+-[0-9]+[: ]
+gitmoji           ^:[a-z0-9_+-]+:[[:space:]]|^[^[:ascii:][:space:]]
+imperative-plain  ^[A-Z][a-z]+[[:space:]].*[^.]$
+other             everything else
+```
+
+`imperative-plain` is deliberately mechanical — capitalised first word, no
+trailing period — and does **not** test for the imperative mood. Mood needs a
+verb lexicon this procedure does not ship, and `Update` versus `Updated` is
+exactly the pair a lexicon-free test cannot separate. That is a stated limit of
+the classifier, not a gap to fill by guessing: a repo whose only distinction
+from Conventional is mood will read as `imperative-plain` either way, and the
+mood question belongs in the ask at step 6.
+
+`classifier_version` in step 7 names the revision of THIS section — the five
+patterns above plus the exclusions in step 2. It is a provenance stamp so a
+later measurement can be compared against a like one; it does not claim an
+executable classifier ships anywhere in the tree.
+
+Record the runner-up family too — a near-tie is itself the finding.
+
+### 4. Aggregate, capped per author, per half
+
+Raw commit counts let one prolific author or an unfiltered bot define the house
+style; one-vote-per-author lets a drive-by contributor with two commits veto it.
+Cap instead: split the sample into a newer and an older half by position first,
+then let **each author contribute at most 20 commits to each half**. Capping the
+sample as a whole would let one author's newest 20 fill their entire quota and
+empty the older half, which is precisely where step 5's coherence check has to
+look.
+
+Compute the dominant family's share over the **capped** total, and report that
+total — a percentage quoted against the raw eligible count describes a statistic
+nobody computed.
+
+With fewer than three authors the cap is **off**: there is no dominance to guard
+against, and a cap of 20 would put the single-maintainer bar's own `n ≥ 30`
+out of reach of its denominator.
+
+### 5. The evidence bar
+
+A measured convention is eligible to be proposed only when **all** hold:
+
+- **n ≥ 30** eligible commits after exclusions;
+- **≥ 80 %** capped-weighted share for the dominant family, over **≥ 3 human
+  authors** — or, with **one or two** authors, an uncapped **≥ 90 %** share over
+  n ≥ 30. Two authors take the stricter branch rather than falling between the
+  two: a two-person repo is a small-team repo, and leaving it unreachable by
+  both branches would make the measurement permanently advisory there;
+- **temporal coherence** — the same family is dominant in the newer half of
+  the sample *and* in the older half. If the halves disagree materially the
+  repository is **migrating**: abstain, name the change point, and use the
+  newer half's family only if it independently clears the bar.
+
+> The 80 % figure is the stricter of two council positions (2026-09-04,
+> anthropic + openai, 2/2 quorum: 70 % vs 80 % + a two-thirds-of-authors
+> clause). The per-author cap is why the separate author-share clause was not
+> also adopted — it already answers the dominance concern the clause existed
+> for. These are policy heuristics, not statistically derived thresholds.
+> **Revisit-if:** a labelled corpus of repositories shows a false-positive or
+> false-negative rate that a different bar would fix.
+
+### 6. Ask — never adopt silently
+
+Below the bar, or on a migrating repo: use Conventional Commits and say so
+**once**, in one line, when a commit is actually requested. Do not ask.
+
+At or above the bar, ask once, as numbered options (per `user-interaction`):
+name the family, the share **and the capped total it was computed over**, the
+author count, and — if a tier-1 parser exists — the tooling that would stop
+parsing.
+
+### 7. Persist the answer where the next session finds it
+
+Write the measurement as a Class-B convention card under
+`agents/memory/curated/conventions/quarantine/commit-subject.md`; the user's
+approval is what moves it to `approved/`. Carry `observed_n`,
+`dominant_share`, `author_count`, `sample_window`, `classifier_version`, and
+`confirm_against` — aggregates only, never per-author identities. Re-measure
+and re-review when the share falls below **70 %**, when a tier-1 source
+appears, or when the newer half's family changes.
+
+## What a measurement may never lower
+
+Prevalence answers *what happened*, never *what the agent is permitted to do* —
+so a house convention can change how a commit reads, and can never change what
+the agent is allowed to commit. Three override policies:
+
+| Policy | Applies to | Examples |
+|---|---|---|
+| `never` | authorization · security · integrity · destructive history · agent provenance | [`commit-policy`](../../rules/commit-policy.md) · [`secret-vcs-guard`](../../rules/secret-vcs-guard.md) · [`git-history-discipline`](../../rules/git-history-discipline.md) · [`non-destructive-by-default`](../../rules/non-destructive-by-default.md) · [`no-attribution-footers`](../../rules/no-attribution-footers.md) |
+| `explicit-only` | governance preferences a maintainer may lift deliberately, that history may not | [`no-decorative-emojis-in-git-surfaces`](../../rules/no-decorative-emojis-in-git-surfaces.md) |
+| `approved-observation` | representation — subject grammar, ticket prefixes, type vocabulary, capitalisation, mood, subject length, body wrapping | this procedure |
+
+So a repository whose history is 70 % emoji subjects does **not** license emoji
+subjects: that rule is `explicit-only`, and the lift is the maintainer's word,
+not the log's. A repository whose history is 60 % attribution trailers licenses
+nothing at all. The council split here (one member argued subject-line emoji is
+a defect and absolute, the other that it is governance taste) resolves to
+`explicit-only` because both positions agree on the operative half — **history
+may not lift it**.
+
 ## Procedure: Generate commit message
 
 ### 1. Identify the actual intent
@@ -110,9 +323,12 @@ Or add `BREAKING CHANGE:` in the commit body/footer.
 
 ## Output format
 
-1. Recommended commit message(s)
-2. Brief rationale for type choice
-3. Split suggestion if the change should be multiple commits
+1. The convention in force and the tier that established it — `configured
+   (commitlint.config.js)`, `approved (ticket-prefix, 84% of 137)`, or
+   `default (Conventional Commits)`
+2. Recommended commit message(s)
+3. Brief rationale for type choice
+4. Split suggestion if the change should be multiple commits
 
 ## Gotcha
 
@@ -120,6 +336,10 @@ Or add `BREAKING CHANGE:` in the commit body/footer.
 - File type alone does not determine commit type (e.g. a `.md` change can be `feat` if it's a new feature doc)
 - Squash merge titles should describe the net effect, not every internal detail
 - `refactor` means NO behavior change — if behavior changes, use `feat` or `fix`
+- A high dominant share over a long window can hide a format change six months
+  ago — the temporal-coherence check, not the share, is what catches it
+- Squash-merging destroys commit-granularity evidence; report granularity as
+  `unknown` there rather than inferring it from the trunk
 
 ## Frugality Standards
 
@@ -146,6 +366,11 @@ to every commit message you author.
 
 ## Do NOT
 
+- Do NOT impose Conventional Commits on a repository that has a configured or
+  approved convention of its own
+- Do NOT adopt a measured convention without asking — below tier 2 it is
+  advisory, and silence is not approval
+- Do NOT let prevalence lift a `never` or `explicit-only` floor
 - Do NOT use vague messages: `update stuff`, `fix bug`, `changes`
 - Do NOT use `refactor` for bug fixes
 - Do NOT use `chore` for meaningful behavior changes
@@ -157,3 +382,8 @@ to every commit message you author.
 - Rule: `commit-conventions` — base format, types, scope, examples
 - Guideline: `docs/guidelines/php/git.md` — type selection rules, anti-patterns, decision checklist
 - Command: `/commit` — uses this skill for message generation
+- Command: `/fix commit-messages` — retro-fits past subjects to the convention
+  this procedure establishes
+- Context: `contexts/execution/project-intelligence.md` — the Class-B
+  consensus-pass, quarantine→approved gate and deviation-staleness mechanism
+  this procedure instantiates for commit subjects

package/dist/agent-src/skills/terraform/SKILL.md

@@ -96,6 +96,35 @@ Check existing modules in the project for which registry modules are used.
 - Security groups follow least-privilege: only allow traffic between known services.
 - IAM policies use specific resource ARNs, not wildcards (except where unavoidable).
 
+### Permissive defaults and missing security blocks
+
+The failure that reaches production is almost never a pinned-version mistake;
+it is a resource that works either way and was left on its permissive default.
+Four constructs carry it. Each backstop grep is over the `.tf` tree you are
+changing, not over this repository.
+
+| Backstop grep | What a hit means | Override condition |
+|---|---|---|
+| `grep -rn '0\.0\.0\.0/0' --include='*.tf' .` | An ingress or egress rule whose CIDR is 0.0.0.0/0, i.e. open to the whole internet. On a management or database port stop and treat it as CRITICAL - the corpus row enumerates which ports those are. | A deliberately public listener - an ALB or CloudFront origin on 80/443. Nothing else. Record the reason next to the rule. |
+| `grep -rn 'publicly_accessible\|block_public_acls\|ignore_public_acls' --include='*.tf' .` | Either `publicly_accessible = true` on a database, or a bucket with no public-access block present at all. Absence is the more common hit and the grep returning nothing is the failing case. | A bucket that genuinely serves public web assets, with the policy written explicitly rather than inherited from a default. |
+| `grep -rnE '"(Action\|Resource)" *: *"\*"\|= *\["\*"\]' --include='*.tf' .` | A wildcard IAM action or resource. One compromised workload credential then reaches everything in the account. | A named, reviewed exception - `iam:PassRole` scoped by condition, or a bootstrap role. Never the default. |
+| `grep -rL 'encrypt' --include='*.tf' .` (lists files with NO encryption mention; `-L` prints names only, so no `-n`) | A storage, volume, snapshot, or database resource with no encryption block. | None for data at rest. A resource holding no data at all. |
+
+Read the surface class before the fix, not after: the mitigation text, the
+abuse case, and the negative test live in the `infrastructure` rows of
+[`threat-modeling`](../threat-modeling/SKILL.md)'s corpus, which is the single
+authority for them. Ask that skill's grounded-corpus step for the
+`infrastructure` surface class - it carries the invocation - and describe the
+change you are making, e.g. *terraform security group ingress open to
+0.0.0.0/0*. Do not copy the command here: one skill owns that interface, for
+the same reason one file owns the control text.
+
+Those rows also carry a `Decided by:` clause stating which check actually
+decides each one. For all four constructs above that clause reads NO CHECK IN
+THIS REPOSITORY - no HCL or IAM-policy parser ships here, so these greps and
+your own IaC policy scanner are the whole enforcement story. Do not write or
+imply otherwise.
+
 ## Common patterns
 
 ### ECS service with CodeDeploy (Blue/Green)

package/dist/agent-src/skills/threat-modeling/data/reasoning.csv

@@ -8,3 +8,4 @@ public-endpoint,Rate limit + cache + minimal payload,"{""if_search_endpoint"": "
 billing,Ledger + idempotency + server-side amounts,"{""if_refunds"": ""one-way-state-machine"", ""if_webhooks_from_psp"": ""verify-signature-and-amount""}",Mutable balance column updates,CRITICAL
 secrets,Manager + redaction + scan,"{""if_third_party_keys"": ""scope-and-rotate-quarterly"", ""if_ci_pipeline"": ""masked-vars-only""}",Secrets in env committed to VCS,HIGH
 data-exposure,Allowlist serializers + contract tests,"{""if_admin_fields"": ""separate-serializer"", ""if_logs_contain_payloads"": ""logger-redaction-keys""}",Spreading model attributes into responses,MEDIUM
+infrastructure,Deny-by-default ingress + encryption on + scoped IAM,"{""if_management_or_db_port"": ""no-internet-cidr-use-bastion-or-private-link"", ""if_object_storage"": ""block-public-access-at-account-and-bucket"", ""if_iam_policy"": ""enumerate-actions-and-resource-arns""}",Permissive defaults left in place because the resource works either way,HIGH

package/dist/agent-src/skills/threat-modeling/data/surfaces.csv

@@ -8,3 +8,4 @@ Public unauthenticated endpoint,public endpoint health status unauthenticated an
 Billing / payment / balance mutation,billing payment charge refund invoice subscription balance credit,billing,money movement,Anything that changes an amount owed/paid
 Secrets / key handling,secret api-key signing key env vault kms rotation,secrets,credentials,"Storage, rotation, and logging paths"
 Data export / serializer / log channel,export serializer api-resource log audit csv download report,data-exposure,"PII, internal fields",Response shaping and log sinks
+Infrastructure / IaC resource definition,terraform iac infrastructure provisioning security group ingress egress cidr bucket storage iam role subnet vpc encryption,infrastructure,"network reachability, data at rest, cloud credentials",Any IaC change to networking storage IAM or encryption defaults

package/dist/agent-src/skills/threat-modeling/data/threats.csv

@@ -14,3 +14,8 @@ billing,Race condition on balance / double-spend,CWE-362,Parallel requests redee
 billing,Price/amount tampering,CWE-602,Client-supplied price or currency trusted at checkout,Recompute amounts server-side from catalog; signed cart or server-held cart only,Test: tampered client amount → server total unchanged,CRITICAL
 secrets,Secret leakage via logs / errors / VCS,"CWE-532, ATT&CK T1552","Key appears in exception payload, debug log, or committed .env",Centralized secret manager; logger redaction list; pre-commit secret scan; scoped short-lived tokens,Test: forced exception on auth path → no credential substring in log sink,HIGH
 data-exposure,Over-broad serializer / API resource,"CWE-213, OWASP API3","Serializer returns internal fields (cost, flags, foreign tenant refs) the UI ignores but attackers read",Explicit field allowlist per resource; separate admin vs public serializers; contract test on response shape,Test: schema-diff response against documented contract → no undocumented fields,MEDIUM
+infrastructure,Unrestricted ingress to a management or database port,"CWE-1327, ATT&CK T1190",Attacker reaches SSH/RDP or a database engine straight from the internet because a security-group or firewall rule allows 0.0.0.0/0,"Deny-by-default ingress; management and database ports reachable only via bastion, VPN, or private link; CIDR scoped to known ranges; never 0.0.0.0/0 on 22/3389/3306/5432/6379/27017","Test: a rule with cidr_blocks 0.0.0.0/0 on a management or database port is rejected. Decided by: NO CHECK IN THIS REPOSITORY - nothing here parses HCL or cloud config; the deciding check is the consumer's own IaC policy scanner",CRITICAL
+infrastructure,Object storage public by default,"CWE-732, OWASP A05",Bucket or container created without a block-public-access setting so any object URL is world-readable,Block public access at account AND bucket level; explicit policy allowlist instead of a public ACL; serve objects via signed URLs or a CDN origin identity,"Test: storage created with no explicit public-access block is rejected; anonymous GET of a stored object returns 403. Decided by: NO CHECK IN THIS REPOSITORY - the deciding check is the consumer's own IaC policy scanner or a cloud posture tool",HIGH
+infrastructure,Missing encryption at rest or in transit,"CWE-311, CWE-319",Volume snapshot bucket or database instance created with no encryption block; endpoint accepts a plaintext connection,Encryption block mandatory on every storage and database resource; customer-managed key where the data class requires it; TLS-only bucket policy and listener; reject plaintext listeners,"Test: a storage or database resource with no encryption block is rejected; a plaintext connection to the endpoint is refused. Decided by: NO CHECK IN THIS REPOSITORY - the deciding check is the consumer's own IaC policy scanner",HIGH
+infrastructure,Wildcard IAM action or resource,"CWE-269, ATT&CK T1078.004",A role policy grants Action * or Resource * so one compromised workload credential reaches every service and object in the account,Enumerate actions and resource ARNs; one role per workload; permission boundary or service control policy on privileged roles; no wildcard outside a named reviewed exception,"Test: a policy document containing Action ""*"" or Resource ""*"" is rejected or carries a named exception. Decided by: NO CHECK IN THIS REPOSITORY - nothing here parses IAM policy documents; the deciding check is the consumer's own IaC policy scanner",CRITICAL
+infrastructure,Credential in an IaC or vars file instead of a secret manager,"CWE-798, ATT&CK T1552.001",Password token or key written as a literal into a .tf .tfvars or .yaml file and committed,Secret-manager reference or runtime-injected env var; never a literal in IaC or vars files; treat the state file as sensitive and store it encrypted with restricted access,"Test: a literal credential in a tracked IaC or vars file fails the build. Decided by: check_secret_leak (src/scripts/check_secret_leak.ts) inside THIS repository - it has no extension allowlist so .tf and .yaml are in scope; for a CONSUMER the deciding check is the gitleaks workflow the package ships as a template that the consumer must copy",HIGH

package/dist/agent-src/templates/agents/agent-project-settings.example.yml

@@ -39,7 +39,7 @@ schema_version: 1
 # CI guard: a release bump of `package.json` must update this value
 # in lockstep — see scripts/check_template_pin_drift.ts (road-to-
 # portable-runtime-and-update-check P3.3).
-agent_config_version: "14.16.0"
+agent_config_version: "14.17.0"
 
 # --- Project identity ---
 project:

package/dist/cli-delegate/cmd_explain.js

@@ -26,8 +26,8 @@ import {
 } from "./chunk-J55WI3RR.js";
 
 // src/scripts/_cli/cmd_explain.ts
-import * as fs7 from "node:fs";
-import * as path6 from "node:path";
+import * as fs6 from "node:fs";
+import * as path5 from "node:path";
 import process2 from "node:process";
 import { fileURLToPath, pathToFileURL } from "node:url";
 
@@ -303,7 +303,7 @@ function _repr(s) {
 }
 
 // src/scripts/_cli/explain_last/index.ts
-import * as fs6 from "node:fs";
+import * as fs5 from "node:fs";
 
 // src/scripts/_cli/explain_last/scrubber.ts
 var LONG_STRING_THRESHOLD = 200;
@@ -817,15 +817,12 @@ function _isOsError(exc) {
 }
 
 // src/scripts/_cli/explain_last/memory.ts
-import * as fs4 from "node:fs";
-import * as path4 from "node:path";
 var PyFloat = class {
   constructor(value) {
     this.value = value;
   }
   value;
 };
-var MEMORY_SIDECAR = path4.join(".agent-memory", "hits.jsonl");
 function _pyTruthy5(value) {
   if (value === null || value === void 0) {
     return false;
@@ -908,93 +905,8 @@ function _from_state(state) {
   }
   return entries;
 }
-function _splitlines(s) {
-  if (s === "") {
-    return [];
-  }
-  const breaks = /* @__PURE__ */ new Set([
-    "\n",
-    "\r",
-    "\v",
-    "\f",
-    "",
-    "",
-    "",
-    "\x85",
-    "\u2028",
-    "\u2029"
-  ]);
-  const out = [];
-  let cur = "";
-  for (let i = 0; i < s.length; i += 1) {
-    const ch = s[i];
-    if (ch === "\r" && s[i + 1] === "\n") {
-      out.push(cur);
-      cur = "";
-      i += 1;
-      continue;
-    }
-    if (breaks.has(ch)) {
-      out.push(cur);
-      cur = "";
-      continue;
-    }
-    cur += ch;
-  }
-  if (cur !== "") {
-    out.push(cur);
-  }
-  return out;
-}
-function _from_sidecar(project_root, run_id) {
-  const p = path4.join(project_root, MEMORY_SIDECAR);
-  if (!fs4.existsSync(p)) {
-    return [];
-  }
-  const entries = [];
-  let content;
-  try {
-    content = fs4.readFileSync(p, "utf-8");
-  } catch {
-    return [];
-  }
-  for (let line of _splitlines(content)) {
-    line = line.trim();
-    if (!line) {
-      continue;
-    }
-    let raw;
-    try {
-      raw = JSON.parse(line);
-    } catch {
-      continue;
-    }
-    if (typeof raw !== "object" || raw === null || Array.isArray(raw)) {
-      continue;
-    }
-    const rawDict = raw;
-    if (run_id) {
-      const got = rawDict.run_id ?? null;
-      if (got !== null && got !== run_id) {
-        continue;
-      }
-    }
-    const entry = _coerce_entry(rawDict);
-    if (entry !== null) {
-      entries.push(entry);
-    }
-  }
-  return entries;
-}
-function build5(project_root, state) {
-  const input = _pyTruthy5(state.input) ? state.input : {};
-  const dataRaw = "data" in input ? input.data : {};
-  const data = typeof dataRaw === "object" && dataRaw !== null && !Array.isArray(dataRaw) ? dataRaw : {};
-  const run_id = data.id;
+function build5(state) {
   const entries = _from_state(state);
-  entries.push(
-    ..._from_sidecar(project_root, typeof run_id === "string" ? run_id : null)
-  );
   return entries.length > 0 ? entries : null;
 }
 
@@ -1062,17 +974,17 @@ function build6(state) {
 }
 
 // src/scripts/_cli/explain_last/route.ts
-import * as fs5 from "node:fs";
-import * as path5 from "node:path";
+import * as fs4 from "node:fs";
+import * as path4 from "node:path";
 var ROUTER_FILENAME = "router.json";
-var ROUTER_RELATIVE = path5.join("dist", ROUTER_FILENAME);
+var ROUTER_RELATIVE = path4.join("dist", ROUTER_FILENAME);
 function _load_router(project_root) {
-  const p = path5.join(project_root, ROUTER_RELATIVE);
-  if (!fs5.existsSync(p)) {
+  const p = path4.join(project_root, ROUTER_RELATIVE);
+  if (!fs4.existsSync(p)) {
     return null;
   }
   try {
-    const parsed = JSON.parse(fs5.readFileSync(p, "utf-8"));
+    const parsed = JSON.parse(fs4.readFileSync(p, "utf-8"));
     return parsed;
   } catch {
     return null;
@@ -1175,7 +1087,7 @@ function _derive_run_id(state, state_file) {
   }
   let mtime = 0;
   try {
-    mtime = fs6.statSync(state_file).mtimeMs / 1e3;
+    mtime = fs5.statSync(state_file).mtimeMs / 1e3;
   } catch {
     mtime = 0;
   }
@@ -1193,7 +1105,7 @@ function build_trace(project_root, state_file, options = {}) {
     inputs: build4(project_root),
     route: build7(project_root, state),
     council: build2(project_root, state_file),
-    memory: build5(project_root, state),
+    memory: build5(state),
     pack: build_pack(project_root),
     assumptions: build(state),
     halt: build3(state),
@@ -1722,7 +1634,7 @@ ${TIP_FOOTER}`;
 
 // src/scripts/_cli/cmd_explain.ts
 var ROUTER_FILENAME2 = "router.json";
-var ROUTER_RELATIVE2 = path6.join("dist", ROUTER_FILENAME2);
+var ROUTER_RELATIVE2 = path5.join("dist", ROUTER_FILENAME2);
 var _HERE = fileURLToPath(import.meta.url);
 var ArgparseExit = class extends Error {
   constructor(code) {
@@ -1834,7 +1746,7 @@ function _dumpJson(payload) {
 }
 function _exists2(p) {
   try {
-    fs7.statSync(p);
+    fs6.statSync(p);
     return true;
   } catch {
     return false;
@@ -1859,19 +1771,19 @@ function _resolve_root(arg) {
   }
 }
 function _load_user_settings(project_root) {
-  const p = path6.join(project_root, DEFAULT_PROJECT_FILE);
+  const p = path5.join(project_root, DEFAULT_PROJECT_FILE);
   if (!_exists2(p)) {
     return {};
   }
   return load_agent_settings({ project_path: p }) || {};
 }
 function _load_router2(project_root) {
-  const p = path6.join(project_root, ROUTER_RELATIVE2);
+  const p = path5.join(project_root, ROUTER_RELATIVE2);
   if (!_exists2(p)) {
     return {};
   }
   try {
-    return JSON.parse(fs7.readFileSync(p, { encoding: "utf-8" }));
+    return JSON.parse(fs6.readFileSync(p, { encoding: "utf-8" }));
   } catch (exc) {
     eprint(`\u274C  explain: cannot read ${p}: ${osErrorStr(exc)}`);
     throw new SystemExitError(2);
@@ -2088,7 +2000,7 @@ function _explain_last(project_root, state_file, as_json, quiet) {
     print("explain last disabled by settings (explain.enable_last)");
     return 0;
   }
-  const target_state = state_file || path6.join(project_root, ".work-state.json");
+  const target_state = state_file || path5.join(project_root, ".work-state.json");
   let trace;
   try {
     trace = build_trace(project_root, target_state);
@@ -2099,7 +2011,7 @@ function _explain_last(project_root, state_file, as_json, quiet) {
       if (relativeTo !== null) {
         rel = relativeTo;
       } else {
-        rel = path6.basename(target_state);
+        rel = path5.basename(target_state);
       }
       const msg = exc.message.split(target_state).join(rel);
       eprint(`\u274C  explain last: ${msg}`);
@@ -2115,9 +2027,9 @@ function _explain_last(project_root, state_file, as_json, quiet) {
   return 0;
 }
 function relativeToOrNull(p, base) {
-  const rel = path6.relative(base, p);
+  const rel = path5.relative(base, p);
   if (rel === "") return rel;
-  if (rel.startsWith("..") || path6.isAbsolute(rel)) {
+  if (rel.startsWith("..") || path5.isAbsolute(rel)) {
     return null;
   }
   return rel;
@@ -2284,13 +2196,13 @@ function _isCliEntry() {
   if (process2.argv[1] === void 0) {
     return false;
   }
-  const argvUrl = pathToFileURL(path6.resolve(process2.argv[1])).href;
+  const argvUrl = pathToFileURL(path5.resolve(process2.argv[1])).href;
   if (import.meta.url === argvUrl) {
     return true;
   }
   try {
-    const here = fs7.realpathSync(fileURLToPath(import.meta.url));
-    const argv = fs7.realpathSync(path6.resolve(process2.argv[1]));
+    const here = fs6.realpathSync(fileURLToPath(import.meta.url));
+    const argv = fs6.realpathSync(path5.resolve(process2.argv[1]));
     return here === argv;
   } catch {
     return false;

package/dist/discovery/deprecation-report.md

@@ -1,6 +1,6 @@
 # Discovery — Deprecation Report
 
-- Generated: `2026-09-04T03:43:39Z`
+- Generated: `2026-09-05T05:33:47Z`
 - Deprecated artefacts: **0**
 
 _None. Tree is clean._