[GH-ISSUE #133] Persist residual-unknown CLI registry across CLI invocations #79

New issue

Closed

opened 2026-10-15 18:20:55 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-15 18:20:55 +00:00

Owner

Originally created by @morluto on GitHub (Jul 14, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/133

Problem

CLI residual-unknown commands use a new in-memory UnknownRegistry per process, so recorded unknowns are not visible to later CLI invocations.

In src/cli.ts, createCli() wires registerUnknownCommands() with new UnknownRegistry({ maxRecords: 1_000, maxRelationships: 100 }) each time the CLI starts.

Reproduction

node scripts/rea.mjs unknown-record --question "persist" --severity high --domain d --authority analyst-inference --confidence observed --evidence ev_aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
node scripts/rea.mjs unknowns

Actual: second command returns an empty list (ok: true value: []) because registry is reset between processes.

Expected

When users split work across CLI invocations, unknown IDs and state should be persisted (or the command help should state explicitly that the CLI registry is single-process only).

Files

src/cli.ts
src/cliUnknownCommands.ts
src/application/UnknownRegistry.ts

Originally created by @morluto on GitHub (Jul 14, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/133 ### Problem CLI residual-unknown commands use a new in-memory `UnknownRegistry` per process, so recorded unknowns are not visible to later CLI invocations. In `src/cli.ts`, `createCli()` wires `registerUnknownCommands()` with `new UnknownRegistry({ maxRecords: 1_000, maxRelationships: 100 })` each time the CLI starts. ### Reproduction ```bash node scripts/rea.mjs unknown-record --question "persist" --severity high --domain d --authority analyst-inference --confidence observed --evidence ev_aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa node scripts/rea.mjs unknowns ``` Actual: second command returns an empty list (`ok: true value: []`) because registry is reset between processes. ### Expected When users split work across CLI invocations, unknown IDs and state should be persisted (or the command help should state explicitly that the CLI registry is single-process only). ### Files - src/cli.ts - src/cliUnknownCommands.ts - src/application/UnknownRegistry.ts

bsakaguchi

2026-10-15 18:20:55 +00:00

closed this issue
added the
bug
label

bsakaguchi commented

2026-10-15 18:20:56 +00:00

Author

Owner

@morluto commented on GitHub (Jul 17, 2026):

Superseded by the session Evidence ledger and persistent investigation-workspace model. The per-process UnknownRegistry CLI surface described here no longer exists on main.

@morluto commented on GitHub (Jul 17, 2026): Superseded by the session Evidence ledger and persistent investigation-workspace model. The per-process UnknownRegistry CLI surface described here no longer exists on main.

bsakaguchi referenced this issue

2026-10-16 21:11:20 +00:00

[PR #79] [MERGED] Add evidence-backed investigation workflows #1817

bsakaguchi referenced this issue

2026-10-16 21:11:20 +00:00

[PR #80] [MERGED] Document the expanded analysis surface #1818