@remits/remits-cli 0.1.156 → 0.1.157

package/index.js

@@ -13,9 +13,9 @@
 - L5223  Component Summaries, Status, And Sync Gates
 - L7547  Branches, Promotion, Commit, And Test Runs
 - L9676  Tokens, Tools, Verification, And Config
-- L11103  Service Dashboard And WebSocket Listener
-- L13602  Agent And Ticket Workflows
-- L17778  Help, Auto Update, And Command Dispatch
+- L11174  Service Dashboard And WebSocket Listener
+- L13673  Agent And Ticket Workflows
+- L17849  Help, Auto Update, And Command Dispatch
 */
 
 /*
@@ -112,7 +112,7 @@ let LOCAL_ACTOR_CONTEXT = null;
 
 // Flags that are legitimately repeatable accumulate into an array instead of last-wins. Every other
 // flag keeps last-wins so existing callers are unaffected.
-const REPEATABLE_FLAGS = new Set(['expected-removed', 'expectedRemoved', 'names', 'tag', 'tags', 'key', 'keys', 'case-key']);
+const REPEATABLE_FLAGS = new Set(['expected-removed', 'expectedRemoved', 'names', 'tag', 'tags', 'key', 'keys', 'case-key', 'score', 'scores', 'lower-is-better']);
 
 // `-m "msg"` is how git spells a commit message, and agents type it from habit. Before this the parser took a
 // single-dash token as the VALUE of whatever flag preceded it: `--json -m "x"` silently turned JSON mode
@@ -10343,6 +10343,19 @@ function corpusAiLabel(row = {}) {
   return 'no AI';
 }
 
+function corpusScoreSummary(scores = {}) {
+  return Object.keys(scores).map((k) => k + ' ' + (scores[k] && scores[k].mean !== undefined ? scores[k].mean : scores[k]) +
+    (scores[k] && scores[k].cases !== undefined ? '/' + scores[k].cases : '')).join(', ');
+}
+
+function corpusScoreDeltas(scores = {}) {
+  return Object.keys(scores).map((k) => {
+    const s = scores[k] || {};
+    const delta = s.delta !== undefined && s.delta !== null ? ' (' + (Number(s.delta) >= 0 ? '+' : '') + s.delta + ')' : '';
+    return k + ' ' + (s.base !== undefined ? s.base : '?') + ' -> ' + (s.head !== undefined ? s.head : '?') + delta + (s.regressed ? ' REGRESSED' : '');
+  }).join(', ');
+}
+
 function corpusLines(sub, data = {}) {
   const lines = ['Corpus: ' + (data.corpus || '?') + ' (owner account ' + (data.ownerAccountId || '?') + ')'];
   if (sub === 'cases') {
@@ -10358,6 +10371,12 @@ function corpusLines(sub, data = {}) {
     (data.runs || []).forEach((r) => lines.push('- ' + r.taskId + '  ' + r.cases + ' case(s)  ' + Object.keys(r.outcomes || {}).map((k) => k + ' ' + r.outcomes[k]).join(', ') +
       '  ' + corpusAiLabel(r) + '  ' + (r.dataMode || '?') + '  ' + (r.branchName || '?') + (r.workspace ? ' [ws:' + r.workspace + ']' : '') +
       (r.laneContentHash ? '  lane ' + String(r.laneContentHash).slice(0, 12) : '') + '  ' + formatTime(r.recordedAt)));
+    (data.runs || []).forEach((r) => {
+      const extra = [];
+      if (r.scores && Object.keys(r.scores).length) extra.push('scores ' + corpusScoreSummary(r.scores));
+      if (r.review) extra.push('graded ' + r.review.graded + ', spot-checked ' + r.review.reviewed + (r.review.agreement !== undefined ? ' (agreement ' + r.review.agreement + ')' : ''));
+      if (extra.length) lines.push('    ' + r.taskId + ': ' + extra.join('  '));
+    });
     if ((data.runs || []).some((r) => r.aiMode === 'mocked')) {
       lines.push('Runs marked AI MOCKED replayed every AI turn from aiMock - they measure the harness, not the model.');
     }
@@ -10366,10 +10385,12 @@ function corpusLines(sub, data = {}) {
     lines.push('Base ' + cmp.baseTaskId + ' -> head ' + cmp.headTaskId + ': ' + Object.keys(cmp.counts || {}).map((k) => k + ' ' + cmp.counts[k]).join(', '));
     lines.push('AI mode: base ' + (cmp.baseAiMode || '?') + ', head ' + (cmp.headAiMode || '?'));
     if (cmp.aiModeChanged) lines.push('WARNING: ' + cmp.aiModeChanged);
-    (cmp.cases || []).filter((c) => c.direction !== 'same').forEach((c) => {
+    if (cmp.scores && Object.keys(cmp.scores).length) lines.push('Scores (cases both runs measured): ' + corpusScoreDeltas(cmp.scores));
+    (cmp.cases || []).filter((c) => c.direction !== 'same' || c.changedScores).forEach((c) => {
       lines.push('- ' + c.caseKey + '  ' + c.direction + (c.base ? '  ' + c.base.outcome : '') + (c.head ? ' -> ' + c.head.outcome : '') +
         (c.expectedChanged ? '  (EXPECTED ANSWER CHANGED between runs)' : ''));
       (c.changedMetrics || []).slice(0, 8).forEach((m) => lines.push('    ' + m.metric + ': ' + JSON.stringify(m.base) + ' -> ' + JSON.stringify(m.head)));
+      Object.keys(c.changedScores || {}).slice(0, 8).forEach((k) => lines.push('    score ' + k + ': ' + c.changedScores[k].base + ' -> ' + c.changedScores[k].head));
       if (c.head && c.head.outcomeReason && c.head.outcome !== 'passed') lines.push('    reason: ' + String(c.head.outcomeReason).slice(0, 300));
     });
   } else if (sub === 'retire') {
@@ -10380,6 +10401,28 @@ function corpusLines(sub, data = {}) {
     if ((data.cases || []).some((c) => c.status === 'retired' || c.status === 'restored')) {
       lines.push('Retired cases stay readable in results and compare; they are just no longer handed to runs. `corpus cases --include-retired` lists them, `corpus retire --restore` puts them back.');
     }
+  } else if (sub === 'gate') {
+    const gate = data.gate || {};
+    lines.push('Gate ' + (gate.baseTaskId || '?') + ' -> ' + (gate.headTaskId || '?') + ': ' + (gate.passed ? 'PASSED' : 'DID NOT PASS') +
+      (gate.tolerance !== undefined ? '  (tolerance ' + gate.tolerance + ')' : ''));
+    if (gate.scores && Object.keys(gate.scores).length) lines.push('Scores: ' + corpusScoreDeltas(gate.scores));
+    (gate.reasons || []).forEach((r) => lines.push('- ' + r));
+    if (gate.expectedChanged && gate.expectedChanged.length) lines.push('Left out (expected answer changed between runs): ' + gate.expectedChanged.join(', '));
+    (gate.changedCases || []).slice(0, 15).forEach((c) => lines.push('  ' + c.caseKey + '  ' + c.direction +
+      Object.keys(c.changedScores || {}).map((k) => '  ' + k + ' ' + c.changedScores[k].base + '->' + c.changedScores[k].head).join('')));
+  } else if (sub === 'review') {
+    if (data.review) {
+      lines.push('Recorded: ' + data.review.caseKey + ' in run ' + data.review.taskId + ': ' + data.review.verdict + (data.review.score !== undefined && data.review.score !== null ? ' (score ' + data.review.score + ')' : ''));
+    } else {
+      const sample = data.sample || [];
+      lines.push('Spot-check sample: ' + sample.length + ' graded case(s), unreviewed first');
+      sample.forEach((c) => {
+        const g = c.grade || {};
+        lines.push('- ' + c.caseKey + '  grade ' + (g.verdict || '?') + ' ' + (g.score !== undefined ? g.score : '') + (c.review ? '  reviewed: ' + c.review.verdict : '  NOT REVIEWED'));
+        if (g.reasons) lines.push('    ' + String(g.reasons).slice(0, 300));
+      });
+      if (sample.length) lines.push('Record a check: remits-cli corpus review --corpus ' + (data.corpus || '<name>') + ' --task-id <taskId> --case <caseKey> --verdict agree|disagree [--score n] [--note "..."]');
+    }
   } else if (sub === 'consistency') {
     const con = data.consistency || {};
     lines.push('Case ' + con.caseKey + ': ' + con.runs + ' run(s), ' + (con.stable ? 'STABLE (identical metrics every run)' : (con.variants || []).length + ' distinct metric results') +
@@ -10390,7 +10433,7 @@ function corpusLines(sub, data = {}) {
   return lines;
 }
 
-// `corpus import|cases|results|runs|compare|consistency`: test corpora through the platform's own corpus(name).
+// `corpus import|cases|results|runs|compare|consistency|retire|gate|review`: test corpora through the platform's own corpus(name).
 async function corpusCommand(flags, subcommand) {
   const cwd = process.cwd();
   ensureLocalState(cwd);
@@ -10510,8 +10553,36 @@ async function corpusCommand(flags, subcommand) {
     if (!retireKeys.length) throw new Error('corpus retire requires --case <caseKey> (repeatable) or --keys a,b,c');
     data = await post({ command: 'retire', corpus: corpusName, keys: retireKeys, restore: flagEnabled(flags.restore) });
     if (data && data.success === false) process.exitCode = 1;
+  } else if (sub === 'gate') {
+    const scores = parseCorpusFilterValues(flags, ['score', 'scores']);
+    const lowerIsBetter = parseCorpusFilterValues(flags, ['lower-is-better']);
+    data = await post({ command: 'gate', corpus: corpusName, base: flags.base, head: flags.head, tolerance: flags.tolerance,
+      scores: scores.length ? scores : undefined,
+      lowerIsBetter: lowerIsBetter.length ? lowerIsBetter : undefined,
+      allowModeChange: flagEnabled(flags['allow-mode-change']) });
+    const gate = (data && data.gate) || {};
+    if (!gate.passed) process.exitCode = 1;
+    await appendVerificationPacket(api, cwd, session, accountId, flags, {
+      type: 'corpus_gate',
+      success: !!gate.passed,
+      claim: 'Corpus ' + corpusName + ' gate ' + (gate.baseTaskId || '?') + ' -> ' + (gate.headTaskId || '?') + ': ' + (gate.passed ? 'passed' : 'did not pass'),
+      world: Object.assign({}, (data && data.world) || {}, { host: normalizeBaseUrl(baseUrl), branchName, workspace, dataMode }),
+      revision: collectVerificationSource(cwd, flags),
+      evidenceCategories: ['corpus_gate'],
+      corpusGate: { corpus: corpusName, baseTaskId: gate.baseTaskId, headTaskId: gate.headTaskId, passed: !!gate.passed, scores: gate.scores, reasons: gate.reasons }
+    }, { quiet: jsonOutput });
+  } else if (sub === 'review') {
+    const taskId = flags['task-id'];
+    if (!taskId) throw new Error('corpus review requires --task-id <taskId> (and --case <caseKey> --verdict agree|disagree to record a check)');
+    if (flags.verdict) {
+      const caseKey = flags.case || flags['case-key'];
+      if (!caseKey) throw new Error('corpus review --verdict requires --case <caseKey>');
+      data = await post({ command: 'review', corpus: corpusName, taskId, caseKey, verdict: flags.verdict, score: flags.score, note: flags.note });
+    } else {
+      data = await post({ command: 'review', corpus: corpusName, taskId, size: flags.sample || flags.size });
+    }
   } else {
-    throw new Error('Unknown corpus subcommand: ' + sub + ' (use import, cases, results, runs, compare, consistency or retire)');
+    throw new Error('Unknown corpus subcommand: ' + sub + ' (use import, cases, results, runs, compare, consistency, retire, gate or review)');
   }
   if (jsonOutput) {
     console.log(JSON.stringify(data, null, 2));
@@ -18144,6 +18215,8 @@ function printCorpusHelp() {
   console.log('       remits-cli corpus compare --corpus <name> --base <taskId> --head <taskId> [--json]');
   console.log('       remits-cli corpus consistency --corpus <name> --case <caseKey> [--limit 20] [--json]');
   console.log('       remits-cli corpus retire --corpus <name> --case <caseKey> [--case ...] [--restore] [--json]');
+  console.log('       remits-cli corpus gate --corpus <name> [--base <taskId>] [--head <taskId>] [--tolerance 0.02] [--score answer] [--lower-is-better <name>] [--allow-mode-change] [--json]');
+  console.log('       remits-cli corpus review --corpus <name> --task-id <taskId> [--sample 5] | --case <caseKey> --verdict agree|disagree [--score n] [--note "..."]');
   console.log('');
   console.log('A corpus is a named, durable set of cases an evaluation-style Test runs again and again (front stage:');
   console.log('corpus(name)). Cases live in a platform table owned by one account and visible to the accounts beneath');

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remits/remits-cli",
-  "version": "0.1.156",
+  "version": "0.1.157",
   "description": "Local CLI for auth, component sync, and live test execution against Remits",
   "license": "MIT",
   "private": false,

package/skills/remits-cli/SKILL.md

@@ -46,6 +46,7 @@ reference below, load it before you act, not after something surprises you.
 | work from a non-trunk checkout, or promote a branch | `branch-variants.md` | what a variant is, which world your checkout resolves, `--as-account` vs `--variant-branch`, tombstones, the promotion loop and its phases, subscribe/retire |
 | touch a support ticket | `support-tickets.md` | the ticket record and its verbs, routed vs claimed vs owned, autonomous workers, the repository edit lease, ask/answer/resume, delivery |
 | register this session as an agent, or ask why a routed ticket never started | `agent-sessions.md` | `serve` vs `register`, what registration does, worker spawning per agent kind, routing order, the control center, multi-session auth |
+| build or evaluate cited Q&A, review learnings, or investigate answer quality | `ai-quality.md` | front-stage guide routing, interaction/session pivots, baseline vs proposal measurements, human checks and explicit corpus gates |
 | investigate live behavior | `investigation.md` | which tool reads which record, correlation keys, reading a record's `content`, HTTP audits, AI activity, node/`localMode`, the production support flows |
 | call any `mcp_*` tool | `tool-reference.md` | every tool's parameters, semantics, and traps — read the tool's entry before building its input |
 | run, describe, poll, or interrupt an Action from the CLI | `tool-reference.md` → `mcp_run_action` | Action execution through `remits-cli tool --name mcp_run_action`; there is no separate top-level `remits-cli action` / `run action` wrapper |
@@ -158,12 +159,11 @@ reference named after it.
   (`component-resolution.md`, `command-reference.md`)
 - **Host and data mode are two independent decisions.** `--base-url` picks the Remits host,
   `--data-mode` picks the data segment on it. Neither implies the other. (`command-reference.md`)
-- **Localhost being down is not a verification blocker.** `remits-cli` can talk to any reachable Remits
-  host, including the deployed production host, by passing `--base-url`. If `http://localhost:8080`
-  refuses a connection, retry the same stage/test/tool/status command against the intended deployed host
-  with the same account, branch, workspace and data-mode facts; do not stop unless no reachable host or
-  valid session exists. A deployed host can still run test-lane verification: `--base-url` selects the
-  server, while `test run` still defaults to `--data-mode test`. (`command-reference.md`)
+- **Use a reachable host that has the implementation you are verifying.** For component work against
+  existing capabilities, localhost being down need not block verification: pass the intended deployed
+  host with `--base-url`, preserving account, branch, workspace and data-mode facts. For unreleased
+  platform capabilities, a deployed old binary is not a substitute; use the updated local/test runtime
+  and follow that repository's startup/restart instructions. (`command-reference.md`, `ai-quality.md`)
 - **`test run` ignores the stored session data lane.** It defaults to `test` even when `whoami` shows
   the session parked on prod; production Test runs require explicit prod provenance (`--data-mode prod`)
   or Test source declaring `dataMode 'prod'` / `[dataMode:'prod']`. Check returned `dataModeSource`

package/skills/remits-cli/references/ai-quality.md

@@ -0,0 +1,118 @@
+# Answer Quality And Reviewed Learning
+
+Load this when building cited Q&A, investigating a wrong answer, changing retrieval or prompts,
+or measuring a proposed learning before review. Component APIs belong in the account's front-stage
+guides; this reference owns the CLI investigation and measurement workflow.
+
+## Table of Contents
+
+- [Find the right guide](#find-the-right-guide)
+- [Investigate one answer](#investigate-one-answer)
+- [Measure a change](#measure-a-change)
+- [Review and gate](#review-and-gate)
+- [Keep the regression](#keep-the-regression)
+
+## Find the right guide
+
+| Building or changing | Read in the account repository |
+|---|---|
+| Search Tool → citations → feedback/review page | `guides/features/ai-interactions.md` → *Wiring a question-to-review workflow* |
+| Learning proposals, review, retirement, Agent memory | `guides/features/agent-memory.md` → *Reviewing learnings* |
+| Rewrite, learned wording, rerank, answer spans, retrieval misses | `guides/features/schema-vertex-ai-extension.md` → *Retrieval quality* |
+| Named retrieval/answer scores, rubric grader, baseline/candidate design | `guides/test-components.md` → *Measuring a proposed learning* and *Human Review And Release Gates* |
+| Per-question guidance and timeout recovery | `guides/agent-components.md` → *ai.turnContext* and *Wiring tools to an agent* |
+
+Use the built-in interaction and learning stores. `interactions()` and `memories()` are component DSL
+builders, not top-level CLI commands. Call them from an application's Action/review UI or a Test;
+do not bypass their scope and review behavior with SQL. The CLI has `corpus review` and `corpus gate`.
+
+## Investigate one answer
+
+Start from the answer's `interactionId`, its sources and feedback. `interactions().trace(id)` gives
+its provider rounds and tool calls; `sessionId` and `traceId` pivot into `mcp_ai_session_search`
+(`investigation.md`, then that tool's entry in `tool-reference.md`). Inspect what the model actually
+received before changing a prompt. For normalization, `unstructured()` also returns `aiSessionId`
+when a model was called, plus `traceId`.
+
+Decide what failed before choosing a remedy:
+
+- Expected source missing: inspect the actual retrieval and `index_explain` diagnostics in the
+  authorized data lane. Test documents are not indexed. Diagnose eligibility/indexing before tuning
+  wording; `not_reached` describes a bounded search window, not proof that a document is irrelevant.
+- Source retrieved but answer wrong: inspect the offered passages, per-turn instructions and answer
+  trace. A citation is not proof that the source supports the claim.
+- Coverage absent: include a should-decline corpus case; a grounded decline can be the correct result.
+- Terminology mismatch: propose `kind: 'phrasing'` with indexed wording in `details` and a source
+  document id in `subjectRef`, then measure it. Feedback alone does not alter retrieval.
+
+`quality.rerank.applied: false` is fallback, not successful reranking. `indexSearchMock` bypasses
+rewriting, learned retrieval and ranking; it proves how the caller uses supplied search results.
+Use live-provider evidence for claims about those steps. Ranking charges are outside chat-token budgets.
+
+## Measure a change
+
+Use the existing account Test/corpus workflow. Keep durable regression components in the account
+repository, and stage the workset in a dedicated workspace. Establish host, execution account, source
+layer and data lane before running (`components status`). Compare the same cases, expected answers,
+source inputs and model settings. Retrieve and score through the actual application path; a parallel
+search written just for the evaluator may measure something the answering Agent never saw.
+
+1. Capture a baseline with approved memories only. Keep each question in a fresh Agent session.
+2. Make the source/prompt change, or enable `includeProposed` in the Test's Agent/retrieval path.
+   Preview includes all relevant proposals in scope, not one selected id. Keep the proposal set
+   stable. Learning records are shared across data lanes; a workspace does not isolate them.
+3. Re-stage and run the candidate under an explicit `withAiBudget` in the Test. Retain both task ids,
+   per-case `scores: [retrieval: ..., answer: ...]`, grader results and retrieval diagnostics.
+
+```bash
+remits-cli components stage --workset --account-id 1 --base-url http://localhost:8080 --data-mode test
+remits-cli test run --test "Support Answer Evaluation" --account-id 1 --base-url http://localhost:8080 --data-mode test --json
+```
+
+The suite name and account above are examples: create/use your application's suite and resolved account.
+Repeat after the candidate edit and stage. `--test` selects a suite; `--names` selects exact case names
+(or a `|`-separated list), not substrings or a regex. Check `total` and outcomes; a zero-case run proves
+nothing. `--wait false` only launches; finish with `test status --task-id <id>`.
+
+Use deterministic search/AI mocks for protocol regressions and live models against pinned corpus
+artifacts for answer quality. Real index measurements need an explicitly authorized production data
+lane and a read-only application path; changing the lane of a workflow with writes is not a shortcut.
+The intended host must also have the implementation being verified: a deployed old binary cannot
+verify unreleased platform changes, even with the same account and test lane.
+
+## Review and gate
+
+With the same explicit host/account/data-mode options as the runs:
+
+```bash
+remits-cli corpus compare --corpus support-golden --base BASE_TASK_ID --head CANDIDATE_TASK_ID
+remits-cli corpus review --corpus support-golden --task-id CANDIDATE_TASK_ID --sample 5
+remits-cli corpus review --corpus support-golden --task-id CANDIDATE_TASK_ID --case CASE_KEY --verdict agree --note "Checked against the source"
+remits-cli corpus gate --corpus support-golden --base BASE_TASK_ID --head CANDIDATE_TASK_ID --score retrieval --score answer
+remits-cli evidence
+```
+
+Replace uppercase ids with the returned task/case ids. Each repeated `--score` is a required metric;
+`--scores retrieval,answer` is equivalent. Pin baseline and candidate instead of relying on latest runs.
+The gate exits nonzero for regressions, lost/absent measurements or an unaccepted mocked/live mode
+change. It records `corpus_gate` evidence. Inspect measured case counts and excluded changed expected
+answers; also assess the application's minimum accuracy and the human spot checks. A non-regression
+gate alone does not establish an absolute quality target or statistical significance.
+
+Stop a release workflow on a failing gate. Approval and component sync do not automatically invoke it.
+Human review preserves the model grade; it does not replace it. Approve/reject through the application's
+`memories()` review path after the decision, and keep the relevant task ids in the review note. Editing
+an approved memory affects later answers immediately; use a proposal when a replacement needs measurement.
+
+## Keep the regression
+
+Use `auxiliary: false` for durable Tests and their helper components. Set `regression: true` for suites
+the account expects in its normal regression, including explicitly budgeted provider suites when
+their cost/dependency is intentional. Otherwise leave costly/exploratory measurements opt-in.
+Describe the proof boundary in the sidecar and README: mocked protocol, live provider smoke,
+measured corpus quality, or UI journey. Retire/reject synthetic memories in cleanup.
+
+Read `component-integrity.md` before landing. Source files alone do not update the platform's durable
+regression selection: use normal account commit/push/sync when authorized, or stage for local runs.
+Read `evidence` before reporting results; distinguish checked-in/staged source, measured behavior,
+human approval and deployment.

package/skills/remits-cli/references/command-reference.md

@@ -65,8 +65,10 @@ Do not assume `--data-mode prod` implies the deployed prod host, or that `--data
 localhost. Likewise, do not assume localhost is required because the current checkout is a back-stage
 repo or because a previous command used localhost. If host matters, read `~/.remits-cli/sessions.json`,
 `remits-cli whoami`, or the recent `remits-cli evidence` world blocks, then pass `--base-url` explicitly.
-Only call verification blocked after trying the intended reachable host and finding that no authenticated
-session or usable network path exists.
+For existing capabilities, try the intended reachable host before declaring a connection blocker.
+For unreleased platform capabilities, also verify that the host has the required implementation.
+Staged component source cannot add missing platform APIs to an older deployed binary; use the updated
+local/test runtime and follow that platform repository's startup/restart instructions.
 
 ### Tool Execution Lifecycle
 
@@ -266,6 +268,9 @@ remits-cli corpus cases --corpus <name> [--split S] [--tag T|--tags T,U] [--key
 remits-cli corpus runs --corpus <name> [--limit 20] [--json]                                   # runs that measured the corpus: outcomes, AI mode (live|MOCKED|none), cost, world
 remits-cli corpus results --corpus <name> [--case <caseKey>] [--task-id <taskId>] [--json]
 remits-cli corpus compare --corpus <name> --base <taskId> --head <taskId> [--json]              # per-case direction, metric deltas, expectedChanged
+remits-cli corpus gate --corpus <name> --base <taskId> --head <taskId> [--score retrieval --score answer] [--lower-is-better <name>] [--tolerance 0.02] [--allow-mode-change] [--json]
+remits-cli corpus review --corpus <name> --task-id <taskId> [--sample 5] [--json]
+remits-cli corpus review --corpus <name> --task-id <taskId> --case <key> --verdict agree|disagree [--score n] [--note "..."]
 remits-cli corpus consistency --corpus <name> --case <caseKey> [--json]                        # did the case produce the same metrics every run?
 remits-cli corpus retire --corpus <name> --case <caseKey> [--case ...] [--restore] [--json]    # drop a case from future runs; past measurements stay readable
 ```
@@ -318,6 +323,16 @@ of the same **shape** - same data lane, branch, workspace and case count - and s
 skipped; it refuses rather than comparing across worlds. `test status --data-mode prod` on a run recorded in
 the test lane returns the run's real lane and now says that is what happened.
 
+For the baseline → proposed learning → human review workflow, see `ai-quality.md` and
+`guides/test-components.md` → *Measuring a proposed learning*. `--score` is repeatable;
+`--score retrieval --score answer` requires both metrics (`--scores retrieval,answer` is equivalent).
+`interactions()` and `memories()` are component DSL APIs, not top-level CLI subcommands.
+
+`corpus gate` exits nonzero for a score regression, missing measurements, or an unaccepted AI-mode
+change, and records `corpus_gate` evidence. Run it explicitly before sync or approving a learning;
+neither operation invokes it automatically. Prefer explicit run ids and check their world.
+`corpus review` samples graded cases or records a human spot check; it preserves the model grade.
+
 A run labelled **`AI MOCKED`** replayed every AI turn from `aiMock`: it produces the same outcomes, scores and
 metrics a measured run would, so read that label before treating green as evidence. `compare` warns when base and
 head used different AI modes; `consistency` warns before calling a case unstable when its runs mixed modes.

package/skills/remits-cli/references/development-loop.md

@@ -68,6 +68,10 @@ The right model is:
 
 Never treat "it looks right in prod data inspection" as sufficient proof that a code change is verified.
 
+For cited answers, retrieval changes or reviewed learnings, load `ai-quality.md`. It connects the
+component workflow to measured baseline/candidate runs, human checks and `corpus gate`; a passing
+mocked Test alone cannot establish improved answer quality.
+
 ## Verification Envelopes
 
 For a concrete user workflow, browser-facing change, branch-variant release, support ticket, or any loop

package/skills/remits-cli/references/investigation.md

@@ -57,6 +57,8 @@ different lanes (see `platform-overview.md` → *Test and Production Data Lanes*
 - **`sessionKey`** — salted user-activity session key. Pivot `mcp_user_activity` `sessions` → `story`;
   each beat then carries a `traceId` / `threadGroupingId` for trace and log investigation.
 - **`sessionId`** — pivots into persisted AI activity via `mcp_ai_session_search`.
+- **`interactionId`** — one Agent answer, including feedback and citations. In component code,
+  `interactions().get(id)` / `.trace(id)` open it; use its `sessionId` / `traceId` for deeper forensics.
 
 ### Reading a record's `content` — persisted context, not a memory dump
 
@@ -109,7 +111,13 @@ embeddable patterns: `features/http-audits.md` (`mcp_get_guide`).
 
 ### AI activity
 
-Every `ai()` call and Agent turn is persisted. Two ways in:
+For a rated or corrected Agent answer, start with `interactions().trace(interactionId)` from an
+Action or Test using the component DSL. `correlation: request_ids` identifies its recorded rounds;
+legacy `time_window` matches may overlap adjacent answers. Empty rounds can mean logging was off or
+telemetry expired. There is no top-level CLI `interactions` command: use your review Action, or pivot
+its session/trace into the tools below. `ai-quality.md` routes the full correction/evaluation workflow.
+
+AI request logging provides two deeper ways in:
 
 - **`mcp_ai_session_search`** — search groupings and open their detail. A grouping spans every session
   sharing one grouping id: the agent turns plus its guardrail and internal `ai()` calls. Use the