[GH-ISSUE #162] Process comparison unknown input omits interaction and shim disagreements #110

New issue

Closed

opened 2026-10-15 18:21:14 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 18:21:14 +00:00

Owner

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

Problem

comparisonUnknownInput in process comparison tool generation reports which scopes disagree, but omits interaction and shim even when those dimensions are the only differences.

registerProcessComparisonTool currently builds differingScopes from:

terminal
exit
filesystem
protocol
process

If only interaction or shim differs, the generated unknown input does not list those dimensions.

Confirmed behavior

processCaptureComparisonSchema includes both interaction and shim dimensions and they can drive non-unchanged status.
comparisonUnknownInput (in src/server/registerProcessComparisonTool.ts, lines ~151-159) filters only five dimensions.
As a result, unknown records from process comparison can have a generic question that omits the true source dimension.

Impact

Unknown registry questions are less precise, making triage harder.
Investigation guidance can miss the exact behavior surface that diverged.
This also obscures traceability for analysts relying on unknown metadata.

Expected behavior

Include interaction and shim in the differing-scope list used to build unknown question text.
Keep existing behavior for all existing scopes and preserve approved/required fields.

Suggested fix

Extend the differingScopes dimensions list in comparisonUnknownInput to include:
- interaction
- shim
Add tests for unknown generation with only interaction/shim divergence.

Files

src/server/registerProcessComparisonTool.ts

Originally created by @morluto on GitHub (Jul 14, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/162 ## Problem `comparisonUnknownInput` in process comparison tool generation reports which scopes disagree, but omits `interaction` and `shim` even when those dimensions are the only differences. `registerProcessComparisonTool` currently builds `differingScopes` from: - `terminal` - `exit` - `filesystem` - `protocol` - `process` If only `interaction` or `shim` differs, the generated unknown input does not list those dimensions. ## Confirmed behavior - `processCaptureComparisonSchema` includes both `interaction` and `shim` dimensions and they can drive non-`unchanged` status. - `comparisonUnknownInput` (in `src/server/registerProcessComparisonTool.ts`, lines ~151-159) filters only five dimensions. - As a result, unknown records from process comparison can have a generic question that omits the true source dimension. ## Impact - Unknown registry questions are less precise, making triage harder. - Investigation guidance can miss the exact behavior surface that diverged. - This also obscures traceability for analysts relying on unknown metadata. ## Expected behavior - Include `interaction` and `shim` in the differing-scope list used to build unknown `question` text. - Keep existing behavior for all existing scopes and preserve approved/required fields. ## Suggested fix - Extend the `differingScopes` dimensions list in `comparisonUnknownInput` to include: - `interaction` - `shim` - Add tests for unknown generation with only interaction/shim divergence. ## Files - `src/server/registerProcessComparisonTool.ts`

bsakaguchi

2026-10-15 18:21:14 +00:00