@lorekit/cli 1.67.0 → 1.69.0

package/skill/lorekit-setup/rules/self-improvement-loops.md

@@ -21,6 +21,8 @@ The design has two tiers connected by a recurrence gate. Both run on LoreKit.
 - [Read step (start of every run)](#read-step-start-of-every-run)
 - [Write step (on failure / at the end of a run)](#write-step-on-failure--at-the-end-of-a-run)
 - [The reconcile-on-re-run flow (resolve + record)](#the-reconcile-on-re-run-flow-resolve--record)
+- [Cross-bucket reads (targeted, read-only)](#cross-bucket-reads-targeted-read-only)
+- [Shared codebase-knowledge (the standard cross-loop layer)](#shared-codebase-knowledge-the-standard-cross-loop-layer)
 - [Promotion (fast → slow)](#promotion-fast--slow)
 - [Entrenchment guards (do not skip these)](#entrenchment-guards-do-not-skip-these)
 - [Wiring checklist](#wiring-checklist)
@@ -69,6 +71,11 @@ across runs** — recurrence is the cheap external signal that the lesson is rea
 not a one-off. This is the episodic → procedural promotion path, with a human
 gate on the slow tier so a single bad run can never rewrite the host.
 
+Both tiers are **read by people as well as agents** — a teammate browsing the
+dashboard, a reviewer asking why a rule exists. That is why a lesson body is
+plain markdown with no hidden payload; see
+[the lesson record](#the-lesson-record).
+
 The fast tier is optional: if LoreKit's `memory.*` tools are not connected, the
 loop is a silent no-op (log one line, continue). The slow tier is just editing
 the host and is unaffected.
@@ -99,24 +106,115 @@ Reserve `branch::` for throwaway notes; a loop normally writes `global` or
 ### The lesson record
 
 A loop lesson is **procedural** ("how to do better next time"), not a fact about
-the user. Keep the machine-read metadata in a `meta:` comment at the top of the
-`value` so the prose stays readable:
+the user. The `value` is **markdown a human reads** — in the dashboard, in a
+SessionStart injection, in another agent's context — and nothing else. Write it
+to this shape:
 
 ```markdown
-<!-- meta: seen_count=1 status=active expires=<ISO 8601, ~90 days out> trigger-context="<concrete signal — file glob, task type, tool, error shape>" -->
+# <one-line takeaway — what to do, not what the lesson is about>
 
-# <one-line lesson title>
+**Applies when:** <concrete signal — file glob, task type, tool name, error shape>
 
-**What failed:** <concrete observable from the run>
+**What happened:** <the concrete observable from the run>
 **Why:** <root cause, if known; "unknown" is allowed>
-**What to do next time:** <prescriptive, actionable, testable instruction>
+**Do this instead:** <prescriptive, actionable, testable instruction>
 **Promotion target:** <the host rule/step this would harden if promoted, or "none">
 ```
 
-`trigger-context` must be **concrete** (globs, task types, tool names, error
-shapes) — never "when it feels relevant" — so the read step can match it
-mechanically. `seen_count`, `status`, and `expires` drive recurrence, promotion,
-and decay.
+`Applies when` must be **concrete** (globs, task types, tool names, error
+shapes) — never "when it feels relevant" — so the read step can match it against
+the current run. It is a visible line, not hidden metadata: the reader deciding
+whether a lesson is theirs needs it first, which is why it sits directly under
+the title.
+
+#### Never put machine metadata in the body
+
+**A lesson body carries no hidden or machine-only payload — no HTML comment, no
+front-matter block, no JSON blob, no `key=value` header.** Every byte of `value`
+must render as prose a person can read. This is not a style preference; a body
+field is the wrong home for each of these on the merits:
+
+| Fact | Where it belongs | Why not the body |
+| ---- | ---------------- | ---------------- |
+| **Recurrence count** | `seen_count`, a store column | `memory_write` sets `seen_count = memories.seen_count + 1` on every overwrite. A count written into prose is a snapshot the writer guessed at and nothing ever updates — stale the first time the lesson recurs, and readers of the real counter never see it |
+| **Expiry** | `ttl_days` on the write (`clear_ttl` to make permanent) | Expiry is enforced against the column by `memory.purge_expired` and the read filters. A date in prose expires nothing |
+| **Status** (`structural`, `promoted`) | a `status::<value>` tag | Tags are first-class and filterable — `memory.list { tags: ["status::structural"] }` finds them. Prose is not queryable |
+| **Owning host / bucket kind** | the `host` and `kind` write fields | Both are first-class, inferred from the `loop::<host>-lessons` tag when omitted, and drive the Explorer's own facets |
+| **Provenance** (repo, branch, commit, PR) | `origin_repo` / `origin_branch` / `origin_commit` / `origin_pr` | First-class, and the dashboard renders them as links |
+| **Trigger** (`stuck-loop`, `command-failure`, …) | the `trigger` write field | Already a facet; restating it in prose adds a line and no information |
+
+An HTML comment is the worst of both worlds: markdown renders it to *nothing*, so
+a human sees a lesson that starts mid-thought, while the fields inside it silently
+disagree with the store's own columns. If a fact has a first-class home, put it
+there and leave it out of the prose entirely.
+
+This rule governs **lesson** bodies. A CI **state record** is a different shape
+on purpose — its whole `value` is a JSON object, authoritative and parsed rather
+than read, with no prose wrapped around it. See
+[ci-state-records.md](./ci-state-records.md).
+
+#### Writing rules
+
+Enforce these on every write, autonomous or not:
+
+- **One lesson per record.** Two takeaways are two keys.
+- **Lead with the takeaway.** The `#` title is the instruction, not the topic —
+  "Pass `--node-modules-dir=none` to `deno check`", not "Notes on deno check".
+- **Bold label, then one short paragraph.** No nesting past one list level, no
+  sub-headings; the whole record is read at a glance or not at all.
+- **Fence every command or snippet**, with a language tag.
+- **Budget ~1,500 characters.** A lesson longer than a screen is a document, and
+  a loop that injects documents crowds out the run it was meant to help. Cut the
+  narrative, keep the instruction.
+- **No run residue** — no transcript excerpts, reasoning traces, session or
+  correlation IDs, timestamps, or "in this run I…" framing. A lesson is written
+  for the *next* run, which has none of that context.
+- **No secrets or PII**, per the privacy pre-flight in the write step.
+
+#### Worked example
+
+❌ **Don't** — a hidden header, a title that names a topic, and a run narrative:
+
+```markdown
+<!-- meta: seen_count=1 status=active expires=2026-12-11 trigger-context="bash: line 5: dash0link: command not found" -->
+# Notes on the Slack tool
+**What failed:** In this run I called `slackSendMessage --args='{ … `dash0link` … }'`
+and got `bash: line 5: dash0link: command not found`, then retried twice with
+different escaping before it worked. Session 4b1c2efe, 2026-09-11.
+```
+
+Everything before the title renders to nothing for a human; `seen_count` and
+`expires` contradict the store the moment the lesson recurs; the title says what
+the lesson is *about* rather than what to do; and the run residue is dead weight
+in every future context window.
+
+✅ **Do** — the same lesson, all metadata in its own field:
+
+````markdown
+# Send Slack messages via a heredoc, not inline `--args='…'`
+
+**Applies when:** shelling out to `slackSendMessage` with text interpolated from
+an external source (ticket titles, PR titles) that may contain backticks or apostrophes.
+
+**What happened:** Inline `--args='{ … }'` failed with `bash: dash0link: command not found` —
+the shell expanded backticks in the JSON, and an apostrophe closed the quoted argument early.
+**Why:** Single quotes do not protect the string once the outer shell re-processes it.
+**Do this instead:** Pass the JSON through a quoted heredoc, which needs no escaping:
+
+```bash
+tools invoke slack.slackSendMessage --args="$(cat <<'ENDJSON'
+{ "text": "…" }
+ENDJSON
+)"
+```
+
+**Promotion target:** the automation prompt's message-building step.
+````
+
+Written with `tags: ["loop::<host>-lessons", "source::command-failure"]`,
+`trigger: "command-failure"`, and `ttl_days: 90` — so the recurrence count, the
+expiry, the owning host and the trigger are all queryable, and the body is
+readable start to finish.
 
 ---
 
@@ -133,10 +231,10 @@ memory.search { q: "<keywords>", scopes: ["repo::{owner}/*", "global"], limit: 1
 
 Then:
 
-1. Match each lesson's `trigger-context` against the current run. Consider only
-   matches. **Skip any lesson whose `expires` is in the past** — treat it as
-   stale.
-2. Apply each matching *"What to do next time"* as a **consideration**, not a
+1. Match each lesson's **Applies when** line against the current run. Consider
+   only matches. Expired lessons do not come back — the store's own TTL drops
+   them, so the read never has to filter on a date in the prose.
+2. Apply each matching **Do this instead** line as a **consideration**, not a
    command — it biases the run unless it conflicts with the user's stated intent
    or a task-specific constraint. On conflict, the user's intent wins; surface it.
 3. On a `repo::` vs `global` collision, the `repo::` lesson wins (closer scope).
@@ -159,23 +257,31 @@ caught something, a near-miss, a guess that paid off. Not on smooth successes.
    memory.search { q: "<key words of the lesson>", scopes: ["repo::{owner}/{repo}", "global"], limit: 10 }
    ```
 
-3. **Write** to the classified scope:
+3. **Write** to the classified scope, putting every fact in its own field and
+   nothing but prose in `value`:
 
    ```text
    memory.write {
-     scope: "<global | repo::{owner}/{repo}>",
-     key:   "<host>-lessons::<slug>",
-     value: "<the lesson body above>",
-     tags:  ["loop::<host>-lessons", "source::<trigger>"],
-     trigger: "<stuck-loop | command-failure | gotcha | near-miss | assumption-wrong | paid-off | manual>"
+     scope:     "<global | repo::{owner}/{repo}>",
+     key:       "<host>-lessons::<slug>",
+     value:     "<the markdown lesson body above — no hidden blocks>",
+     tags:      ["loop::<host>-lessons", "source::<trigger>"],   # + "status::structural" when it is
+     trigger:   "<stuck-loop | command-failure | gotcha | near-miss | assumption-wrong | paid-off | manual>",
+     ttl_days:  90
    }
    ```
 
-Same `scope` + `key` overwrites in place. **A recurrence resolves to an UPDATE
-that increments `seen_count` by 1 and refreshes `expires`** — that is what makes
-recurrence countable and drives promotion. If a lesson you applied at the start
-of the run worked (the failure did not recur), still write the UPDATE:
-successful application is recurrence evidence.
+   `host` and `kind` are inferred from the `loop::<host>-lessons` tag; pass them
+   explicitly only when the tag does not carry them. Add the `origin_*` fields
+   when the run knows them.
+
+Same `scope` + `key` overwrites in place. **A recurrence resolves to an UPDATE:
+the store increments `seen_count` by 1 for you, and re-passing `ttl_days`
+refreshes the expiry** — that is what makes recurrence countable and drives
+promotion. Never hand-write a count into the body to track this; the column is
+the only copy that stays true. If a lesson you applied at the start of the run
+worked (the failure did not recur), still write the UPDATE: successful
+application is recurrence evidence.
 
 The privacy pre-flight is never skipped, autonomous or not: a candidate lesson
 containing a secret, token, credential, or PII is **dropped, not written**. The
@@ -247,12 +353,141 @@ record shape are specified in `agents/shared/rules/comment-relevance-memory.md`.
 
 ---
 
+## Cross-bucket reads (targeted, read-only)
+
+The default is strict: a loop reads **only its own bucket**, filtered by
+`loop::<host>-lessons`. That isolation is deliberate — it keeps one loop's
+lessons from drowning another's, and lets each read fire at its own cadence
+against its own decision point. Wholesale "read every lesson this repo knows"
+is an **anti-pattern**: it reintroduces exactly the noise the tag split exists
+to prevent, and buries the matches that would have fired.
+
+There is **one** shape of cross-bucket read that is safe and worth wiring: a host
+reading **another host's Signal or Knowledge bucket, matched by a structural key,
+strictly read-only**. Wire it only when all four hold:
+
+1. **The other bucket is keyed by something structural** — a `symbol@path`, a
+   file path, a stable fingerprint — never by prose. A structural key is what
+   makes a cross-host read meaningful: it matches the reader's own concrete work
+   (the files or symbols it is about to touch), not a vague topic.
+2. **The read is bounded to the reader's current work.** Match the other bucket's
+   keys against the paths / symbols this run will actually touch and ignore the
+   rest — never load the whole bucket as advice.
+3. **The reader treats it as advisory and re-verifies.** A cross-host fact can be
+   stale — it carries the *writer's* `verified_at_sha`, not the reader's. It
+   **raises care** (more coverage on a hotspot, design around a known invariant)
+   but never lowers a bar, skips a step, or suppresses a finding. An absent
+   record is never evidence of safety.
+4. **The reader never writes the other bucket.** Write ownership stays with the
+   one owning host; a second writer corrupts its provenance. Cross-host is a
+   **read** relationship only.
+
+Do **not** cross-read another host's `loop::<host>-lessons`. Lessons are prose
+"how to do better" advice tuned to that host's own decisions; they re-key on
+rephrasing and carry no structural anchor to match against, so a cross-read of
+them is the wholesale anti-pattern above. Only Signal / Knowledge buckets with
+structural keys qualify.
+
+LoreKit ships **one** standard instance of this pattern — the shared
+`codebase-knowledge` bucket that every code-touching loop reads and writes. It is
+the mechanism behind the automatic synergy below, and it is what makes a
+structural key worth insisting on: a fixed name plus a `symbol@path` key is what
+lets a loop wired by one person be consumed by a loop wired by another. It is
+specified in full next.
+
+---
+
+## Shared codebase-knowledge (the standard cross-loop layer)
+
+The cross-bucket read above becomes **automatic** through one bucket every LoreKit
+loop shares by name: `codebase-knowledge`. This is the reason two skills wired
+independently — by different people, in different sessions, in the same repo —
+still compound: they read and write the *same* repo-scoped, structurally-keyed
+record of what the codebase has taught every loop that touched it. A code-changing
+loop plans and edits with that history in hand instead of blind; and because the
+loops that consume it also feed it, the synergy appears for a user who wired a
+single skill and nothing else.
+
+### The bucket
+
+| Field | Value |
+| --- | --- |
+| **Tag** | `codebase-knowledge` |
+| **Kind** | `signal` (a durable per-repo filter, read on every run that touches code) |
+| **Scope** | `repo::{owner}/{repo}` — a codebase fact is repo-bound |
+| **TTL** | ~90 days, refreshed on re-verification |
+| **Keys** | `knowledge::<symbol>@<path>` — verified facts about one symbol (an invariant it holds, its consumer/dependent count, a defect it produced before); `hotspot::<path>` — per-file counters (`confirmed`, `regressed`, `missed`) |
+
+The keys are **structural** (`symbol@path`, `path`) on purpose: a key survives a
+rename of the *finding* but not a rename of the *code*, which is exactly the
+sensitivity that lets a different loop match it against the files it is about to
+touch. Set `kind: signal` and `host` explicitly on every write — LoreKit infers
+them only from a `loop::` tag, and this bucket is not tagged that way.
+
+### Read side — automatic for any code-touching host
+
+Wire it at the host's **plan/apply seam** — the moment it has the concrete
+file/symbol list it will change (a plan's File Changes list, an apply pack, a
+fix's target file):
+
+```text
+memory.list { scope: "repo::{owner}/{repo}", tags: ["codebase-knowledge"], limit: 100 }
+# keep only hotspot::<path> / knowledge::<symbol>@<path> whose <path> (and <symbol>)
+# this run will actually touch. Apply as PLANNING INPUTS: raise coverage on a
+# hotspot, design around a known invariant / consumer count. Advisory and
+# re-verified against the code — never a reason to skip a step or suppress a finding.
+```
+
+This is the read-side contract from [Cross-bucket reads](#cross-bucket-reads-targeted-read-only)
+made concrete: structural match, bounded to this run, advisory, an absent record
+never evidence of safety.
+
+### Write side — how the layer fills, and why many writers stay safe
+
+A host that **verifies** a structural fact contributes it back, so the next loop
+reads it. This is what makes the synergy automatic even for a user with one skill
+and no dedicated reviewer: the loops that consume the layer also feed it.
+Multi-writer is safe **only** behind this write contract — bake in every bullet,
+or do not wire the write:
+
+- **Structural key from a real symbol/path list**, never composed from prose. A
+  prose key accumulates nothing and no reader can match it.
+- **`verified_at_sha` on every fact** — the HEAD this run verified it at. It is the
+  whole mechanism the next reader uses to decide "fact stands" vs "re-verify"; an
+  absent or stale SHA makes the fact permanently unverifiable, and it is dropped.
+- **`source_agent` stamped** — which host verified it. Together with
+  `verified_at_sha` this is what makes many writers safe: a reader sees who
+  verified what, and when, so no writer silently overwrites another's provenance.
+- **Only what THIS run actually verified**, grounded in the code — never a guess,
+  and never a value about a person or a telemetry reading. A fact about code,
+  keyed to code.
+- **Merge, never clobber.** Read the existing record first; append to `history[]`
+  or increment counters (each capped) and carry the rest through unchanged. A
+  clobbered counter is indistinguishable from a first write.
+- **Raise care, never suppress.** These records only raise priority/coverage on a
+  file or symbol. They never lower a bar or silence a finding, and an absent record
+  is never evidence of safety. Suppression, if a host needs it, is a different
+  bucket behind verification (the Signal in the reconcile flow above).
+- **Explicit `kind: signal` + `host`, a TTL, and the privacy pre-flight** — as
+  every write in this skill.
+
+Because the name is fixed, the read is the same call in every host, and the write
+follows one contract, **any two LoreKit-wired loops in the same repo compound
+automatically** — which is the whole reason to standardize the name instead of
+letting each host invent its own. The reference ecosystem is `agent-skills`: the
+`pr-reviewer` agent is the primary writer (it verifies symbol facts and file
+hotspots during review), and every code-changing host — `aw`, `implement-suggestion`,
+`fix-bug`, `ci-auto-fix` — reads the layer at its plan/apply seam.
+
+---
+
 ## Promotion (fast → slow)
 
 After a read or write, a lesson is **promotion-eligible** when either:
 
-- `seen_count >= 3` — the same failure recurred across at least three runs, or
-- it is tagged `status=structural` because it reflects a design gap, not a
+- `seen_count >= 3` — the same failure recurred across at least three runs (read
+  the store's column, never a number written into the body), or
+- it carries the `status::structural` tag because it reflects a design gap, not a
   one-off.
 
 For an eligible lesson, **surface a one-line suggestion — never act silently**:
@@ -264,8 +499,8 @@ The promotion target follows the lesson's scope: a `global` lesson hardens the
 **host's own source** (every user of the host benefits); a `repo::` lesson
 hardens the **repo's own rules / docs** (every teammate in that repo benefits).
 Promotion is a normal, human-reviewed edit — LoreKit does not apply it. After a
-successful promotion, write an UPDATE setting `status=promoted` so the lesson
-stops re-suggesting and stands as an audit trail of why the rule exists.
+successful promotion, write an UPDATE adding the `status::promoted` tag so the
+lesson stops re-suggesting and stands as an audit trail of why the rule exists.
 
 A recurring lesson can be promoted a second time, past the prose rule above,
 into a **compiled invariant** — a declarative, mechanically-checked assertion
@@ -290,9 +525,10 @@ guards are what make the loop safe:
    run; it can never silently disable a gate, skip a step, or change a limit. The
    only path from a lesson to changed behavior is the human-reviewed slow tier.
 2. **Recurrence gates promotion, not a single run** (`seen_count >= 3`, or an
-   explicit `status=structural` marker in the lesson's `meta:` comment).
-3. **Every lesson expires** (default ~90 days from last sighting; the read step
-   ignores expired lessons, so stale beliefs decay instead of entrenching).
+   explicit `status::structural` tag on the lesson).
+3. **Every lesson expires** — `ttl_days: 90` on the write, refreshed on each
+   recurrence, so stale beliefs decay instead of entrenching. The store enforces
+   this; an expiry stated only in prose is decoration.
 4. **Contradiction is surfaced, not silently overwritten** — the dedup search
    finds the prior lesson; a genuine reversal is a reviewed decision.
 5. **The privacy pre-flight is never bypassed** — secrets / PII are dropped, not
@@ -306,16 +542,21 @@ To add a loop to a host called `<host>`:
 
 - [ ] Pick the bucket: tag `loop::<host>-lessons`, key `<host>-lessons::<slug>`.
 - [ ] Add the **read step** at the start of the host's run (narrow-to-broad
-      `memory.list` filtered by the tag; apply matches as considerations; skip
-      expired).
+      `memory.list` filtered by the tag; apply matches as considerations).
 - [ ] Add the **write step** at the host's existing failure / end-of-run points
-      (classify scope, `memory.search` to dedup, `memory.write`). No new
-      reflection stage — hook the points the host already detects.
+      (classify scope, `memory.search` to dedup, `memory.write` with `ttl_days`).
+      No new reflection stage — hook the points the host already detects.
+- [ ] State the **body contract** in the host's own write step: markdown to the
+      shape above, no hidden blocks, every store-backed fact in its own field.
 - [ ] Add the **promotion suggestion** when a read/written lesson hits
-      `seen_count >= 3` or `status=structural`.
+      `seen_count >= 3` or carries `status::structural`.
 - [ ] State the **entrenchment guards** so a future maintainer does not "optimize
       them away".
 - [ ] Confirm the loop **degrades silently** when `memory.*` is not connected.
+- [ ] If the host **touches code**, wire the **[codebase-knowledge](#shared-codebase-knowledge-the-standard-cross-loop-layer)
+      read** at its plan/apply seam (match `hotspot::<path>` /
+      `knowledge::<symbol>@<path>` to the files it will change). If it **verifies**
+      a structural fact, wire the **write** behind that section's contract.
 
 ---
 

package/src/commands/invariants.mjs

@@ -14,15 +14,16 @@
 //
 // Criteria (pure scoring in `../shared/candidates-pure.mjs`):
 //   - summed seen_count across a cluster's members >= --min-seen-count
-//     (default 3), OR any member's `<!-- meta: ... status=... -->` comment
-//     already declares a non-"active" status
+//     (default 3), OR any member already declares a non-"active" status —
+//     a `status::<value>` tag, or a legacy `<!-- meta: ... status=... -->`
+//     comment for lessons written before tags were the convention
 //   - ranked by (summed seen_count × distinct scopes), descending
 //
 // What this deliberately does NOT do:
-//   - classify a trigger-context into a glob/command/error-shape. The raw
-//     `trigger-context` string (when a lesson's meta comment carries one) is
-//     printed verbatim, never interpreted — "parses into a detectable
-//     trigger" is the human step the compile pipeline protects.
+//   - classify an applicability signal into a glob/command/error-shape. The raw
+//     string (a lesson's `**Applies when:**` line, or a legacy meta comment's
+//     `trigger-context`) is printed verbatim, never interpreted — "parses into
+//     a detectable trigger" is the human step the compile pipeline protects.
 //   - check `compiled_to`. No such field exists yet (no schema, no server
 //     support — see the kickoff's Open Questions), so a candidate already
 //     compiled into an obligations-map.mjs entry can still surface here. A
@@ -150,7 +151,13 @@ function buildCandidates(entries, { threshold, minSeenCount }) {
     ...cl,
     members: cl.members.map((m) => {
       const raw = byAddress.get(`${m.scope}::${m.key}`);
-      return { scope: m.scope, key: m.key, seenCount: seenCountOf(raw), value: raw?.value ?? '' };
+      return {
+        scope: m.scope,
+        key: m.key,
+        seenCount: seenCountOf(raw),
+        value: raw?.value ?? '',
+        tags: Array.isArray(raw?.tags) ? raw.tags : [],
+      };
     }),
   }));
   return rankCandidates(clusters, { minSeenCount, resolveClass: resolveRecurrenceClass });
@@ -221,7 +228,7 @@ async function candidates(args) {
     heading('LoreKit invariants candidates');
     log(`  project: ${c.dim(root)}`);
     log(`  scopes:  ${scopes.join('  →  ')}`);
-    log(`  ${c.dim(`criteria: summed seen_count >= ${minSeenCount}, or a member's meta status is non-"active"`)}`);
+    log(`  ${c.dim(`criteria: summed seen_count >= ${minSeenCount}, or a member's status is non-"active"`)}`);
 
     if (offlineSection.available && offlineSection.popCapped) {
       log(`  ${c.yellow('!')} population cap (${POP_CAP}) reached for Offline — results are partial. Narrow with --key-prefix, --since, or --max.`);
@@ -281,8 +288,8 @@ function renderSection(header, section) {
     }
     for (const m of cand.members) {
       const fields = [`seen_count=${m.seenCount}`];
-      if (m.meta.status) fields.push(`status=${m.meta.status}`);
-      if (m.meta['trigger-context']) fields.push(`trigger-context=${JSON.stringify(m.meta['trigger-context'])}`);
+      if (m.status) fields.push(`status=${m.status}`);
+      if (m.appliesWhen) fields.push(`applies-when=${JSON.stringify(m.appliesWhen)}`);
       log(`    ${c.cyan('-')} ${m.scope}::${m.key}  ${c.dim(`(${fields.join(', ')})`)}`);
     }
   }