[PR #6180] [CLOSED] docs(errors): correct stale capability-unknown and comparison-rationale rows #7188

Closed
opened 2026-11-01 21:46:00 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6180
Author: @Iyanuoluwa007
Created: 10/21/2026
Status: ❌ Closed

Base: main ← Head: docs/error-catalogue-stale-rows


📝 Commits (2)

  • eff6f9d docs(errors): mark approval-based capability-unknown tracking removed
  • 83f752d docs(errors): record the shipped function-comparison probe rationale

📊 Changes

1 file changed (+2 additions, -2 deletions)

View changed files

📝 docs/user-visible-errors.csv (+2 -2)

📄 Description

Summary

Fixes #5743. Fixes #5742. Two stale rows in docs/user-visible-errors.csv claimed behavior or wording as implemented and verified, but the code and the cited tests now do something else. Docs only; each row is corrected to what the code serves and the cited test asserts. They're kept together per CONTRIBUTING ("keep related corrections together"), as one-line edits to the same catalogue.

Problem and expected behavior

  • Row 24.5 (#5743): "Approved unknown tracking records an unavailable analysis" was marked implemented / "verified by focused MCP integration test". f55c2b926 removed approval-based capability-unknown recording. tests/boundary/mcp/serverUnknownsMcp.test.ts ("does not record capability unavailability without supporting Evidence") now requires list_unknowns to stay empty.
  • Row 24.93 (#5742): proposed_replacement read "…under the same target context and analysis limits." and was marked implemented and verified. src/server/registerFunctionComparisonTool.ts:196 serves "Capture complete dossiers for both functions under the same target context.", and tests/boundary/mcp/functionComparisonMcp.test.ts:217 asserts that shorter sentence.

Change and scope

  • Row 24.5: implementation_status implemented → removed (an existing catalogue status), and verification_result now states what the focused test verifies.
  • Row 24.93: proposed_replacement set to the shipped sentence; status and verification unchanged, since that wording is implemented and verified.

No code, contract or other row changes. Nothing in the repository parses this CSV.

Contract and boundary impact

  • Semantic owner and earliest changed stage: documentation only.

  • Contribution scope fit and linked maintainer decision: not applicable.

  • CLI and MCP/tool-catalog contract: none.

  • Provider, bridge, target-format, or platform compatibility: none.

  • Evidence, artifact, provenance, or reconstruction contract: none.

  • Target selection, authority, upstream behavior, and cleanup details: not applicable.

  • Generated metadata, package, or installation impact: none.

  • Documentation or usability only; no target interaction.

Evidence and regression coverage

  • Source checks: git show f55c2b926 (refactor(mcp): simplify tool inputs and inline results, 2026-09-29); the cited test names and lines exist on main as quoted above.

  • Executed: npx vitest run tests/boundary/mcp/serverUnknownsMcp.test.ts tests/boundary/mcp/functionComparisonMcp.test.ts: 11 passed (Windows 11, Node 24).

  • The CSV still parses with Python's csv.DictReader: 103 rows, no row with extra columns. The diff is two lines.

  • Remaining proof gaps: npm run docs:check could not run on my Windows checkout (it needs the packaged native addon); CI runs it.

  • Observed, derived, and inferred claims remain distinguishable.

  • Artifact identity, source provenance, and failed attempts remain preserved.

  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

  • The two cited test files: 11 passed.
  • CSV re-parsed after each edit: 103 rows, columns intact.
  • Pre-push npm run check:fast (typecheck, lint): passed.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: none.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: none.

Author readiness

Human owner:

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked, or the reason for not linking one is stated above.
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs, contracts, and generated metadata are updated where needed.
  • User-visible CLI/MCP changes include representative output.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/6180 **Author:** [@Iyanuoluwa007](https://github.com/Iyanuoluwa007) **Created:** 10/21/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `docs/error-catalogue-stale-rows` --- ### 📝 Commits (2) - [`eff6f9d`](https://github.com/morluto/rea/commit/eff6f9d484e3e1dfb78edef5c2bf4daf1526a16e) docs(errors): mark approval-based capability-unknown tracking removed - [`83f752d`](https://github.com/morluto/rea/commit/83f752d89b7243153412907faf5b772de9c5da32) docs(errors): record the shipped function-comparison probe rationale ### 📊 Changes **1 file changed** (+2 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `docs/user-visible-errors.csv` (+2 -2) </details> ### 📄 Description ## Summary Fixes #5743. Fixes #5742. Two stale rows in `docs/user-visible-errors.csv` claimed behavior or wording as implemented and verified, but the code and the cited tests now do something else. Docs only; each row is corrected to what the code serves and the cited test asserts. They're kept together per CONTRIBUTING ("keep related corrections together"), as one-line edits to the same catalogue. ## Problem and expected behavior - **Row 24.5 (#5743):** "Approved unknown tracking records an unavailable analysis" was marked `implemented` / "verified by focused MCP integration test". f55c2b926 removed approval-based capability-unknown recording. `tests/boundary/mcp/serverUnknownsMcp.test.ts` ("does not record capability unavailability without supporting Evidence") now requires `list_unknowns` to stay empty. - **Row 24.93 (#5742):** `proposed_replacement` read "…under the same target context and analysis limits." and was marked implemented and verified. `src/server/registerFunctionComparisonTool.ts:196` serves "Capture complete dossiers for both functions under the same target context.", and `tests/boundary/mcp/functionComparisonMcp.test.ts:217` asserts that shorter sentence. ## Change and scope - Row 24.5: `implementation_status` `implemented` → `removed` (an existing catalogue status), and `verification_result` now states what the focused test verifies. - Row 24.93: `proposed_replacement` set to the shipped sentence; status and verification unchanged, since that wording is implemented and verified. No code, contract or other row changes. Nothing in the repository parses this CSV. ## Contract and boundary impact - Semantic owner and earliest changed stage: documentation only. - Contribution scope fit and linked maintainer decision: not applicable. - CLI and MCP/tool-catalog contract: none. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details: not applicable. - Generated metadata, package, or installation impact: none. - [x] Documentation or usability only; no target interaction. ## Evidence and regression coverage - Source checks: `git show f55c2b926` (refactor(mcp): simplify tool inputs and inline results, 2026-09-29); the cited test names and lines exist on main as quoted above. - Executed: `npx vitest run tests/boundary/mcp/serverUnknownsMcp.test.ts tests/boundary/mcp/functionComparisonMcp.test.ts`: 11 passed (Windows 11, Node 24). - The CSV still parses with Python's `csv.DictReader`: 103 rows, no row with extra columns. The diff is two lines. - Remaining proof gaps: `npm run docs:check` could not run on my Windows checkout (it needs the packaged native addon); CI runs it. - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - The two cited test files: 11 passed. - CSV re-parsed after each edit: 103 rows, columns intact. - Pre-push `npm run check:fast` (typecheck, lint): passed. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: none. - Package or release metadata impact: none. - Security, privacy, process, or containment review: none. ## Author readiness Human owner: <!-- @GitHub-handle --> - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:46:00 +00:00
bsakaguchi changed title from [PR #6180] [CLOSED] docs(errors): correct stale capability-unknown and comparison-rationale rows to [PR #6180] docs(errors): correct stale capability-unknown and comparison-rationale rows 2026-11-04 16:32:39 +00:00
bsakaguchi changed title from [PR #6180] docs(errors): correct stale capability-unknown and comparison-rationale rows to [PR #6180] [CLOSED] docs(errors): correct stale capability-unknown and comparison-rationale rows 2026-11-04 17:28:43 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#7188
No description provided.