[wefio]

Change summary

What (what changed):

Automatic recall now shares source-bound InformationView preparation across Pi, OpenCode, DSH and WorkBuddy. Session-bound search reorders its existing candidate page using the current request and bounded recent user context, independently of display mode. Automatic display defaults to at most ten candidates with 160-code-point statement previews; full mode retains statement bodies within the shared context budget.

Why (why it changed / what problem it addresses):

Unrelated long engineering memories can crowd out the current conversation. Shared ranking and display profiles reduce that exposure without deleting retrieval candidates or adding provider calls. Automatic adapters also stop recording disclosure before host delivery, and historical DSH UI snapshots cannot become a fresh turn's injected recall.

Changes (key changes, by file or module):

• Shared service/context policy: bounded user-only context, stable contextual ordering, unchanged candidate membership and scores, session/project isolation.
• Shared view preparation: compact/full profiles, retained references and preview labels, whole-row output budgeting and an explicit displayed/retrieved count.
• CLI/RPC: nmg recall display --session-id ID [--mode compact|full]; settings are daemon-local and session-specific.
• Adapters: shared automatic preparation; generation/deadline fencing and disclosure boundaries remain explicit.
• Validation: 16 blocking checks passed through agent:verify; product tests: 2,082 passed, 2 skipped, zero failures. An isolated resident daemon verified CLI reads, mode changes and session isolation.

Documentation owners:

• Decision: docs/decisions/implemented/2026-10-07-shared-information-output.{md,zh-CN.md}.
• Design: docs/design/state-spaces.{md,zh-CN.md}, docs/design/recall-context-and-display.{md,zh-CN.md,terms.yaml}, docs/design/session-memory-lifecycle-hooks-2026-08-10/automatic-recall-budget.{md,zh-CN.md}, and the feature-register/shared-display-options document groups under docs/design/hidden-features-registry/.
• Operating references: recall and harness-adapters pairs under skills/nmg-memory/references/; adapter README updates in dsh/, opencode-plugin/ and workbuddy-plugin/.
• Experiment, postmortem and guide: none; this change adds no measured natural benchmark result, incident record or learning guide.

---

Not verified

Not verified (what was not verified):

No live LLM/embedding benchmark or natural multi-turn relevance/answer-quality evaluation was run. Keeping all retrieved IDs preserves whole-page membership; it does not prove recall at a smaller cutoff or improvement in the first ten results. Production daemon deployment and live host GUI behavior were not exercised. Research/chaos advisory suites were not run. The existing production daemon was not restarted.

---

Completion checklist

Local quality checks

• verify:static component checks passed via the 16-check agent:verify route (build, package, type, tests types, lock, lint, format, docs, context routes, complexity, packages, glossary, policy words, RTM and mutation anchors).
• npm run test:product: 2,082 passed, 2 skipped, zero failures.
• Dependencies and lockfiles unchanged; check:lock passed.
• DSH subpackage frozen-lockfile install/build passed through verify:packages.
• docs:check passed; the existing unrelated embedding-deadline bilingual-link warning remains.
• Every touched documentation owner is named above.
• Not verified scope is filled; non-trivial changes include an updated decision.
• New/changed methods satisfy the complexity gate; unchanged baseline debt is reported separately.
• No reproducible build artifacts committed.
• Full pre-push mutation sweep passed: 116/116 mutants caught; all 23 target files restored byte-identically.

RCP (Repository Control Plane)

• In-flight goals registered before substantive changes and resolved on completion.
• Changed routes reconciled through agent:verify; local evidence in .nmg/verification/latest.json.
• All-green CI confirmed by nmg-rcp forge-status --pr <number>.
• Only owned files committed; working tree checked.

CI completion confirmation

• All checks passed from RCP forge observation.
• CodeFactor passes.
• Static job passes, including dependency audit.