[PR #6181] [MERGED] refactor: remove obsolete forwarding APIs and unify CI contracts #7189

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/6181
Author: @morluto
Created: 10/21/2026
Status: ✅ Merged
Merged: 10/21/2026
Merged by: @morluto

Base: main ← Head: codex/legacy-cleanup-20261022


📝 Commits (2)

  • c50f5c7 refactor: remove obsolete internal forwarding APIs
  • 7735aa5 refactor(ci): centralize failure classification contracts

📊 Changes

11 files changed (+68 additions, -117 deletions)

View changed files

📝 scripts/ci/artifacts.d.mts (+39 -13)
📝 scripts/ci/failure-report.d.mts (+1 -53)
📝 scripts/ci/failure-report.mjs (+0 -2)
📝 src/application/Uninstall.ts (+0 -1)
📝 src/application/Update.ts (+0 -1)
📝 src/cli/options.ts (+14 -25)
📝 src/cliLogging.test.ts (+4 -10)
📝 src/domain/analysisView/analysisView.ts (+1 -1)
📝 src/domain/analysisView/modelArtifactView.ts (+1 -5)
📝 tests/boundary/filesystem/ciFailureReport.test.ts (+3 -3)
📝 tests/boundary/filesystem/ciFailureReportBudget.test.ts (+5 -3)

📄 Description

Summary

Remove internal forwarding APIs whose callers already have canonical owners. Native CLI flags now map directly to analysis options, failure predicates are imported from their own modules, and model-view requests import their schema from the model query contract.

The CI report previously forwarded classifyFailure with a second, different handwritten declaration. CI run/job metadata and parsed static evidence now live with the artifact classifier and producer. The report and tests consume those shared contracts directly; the forwarding export and duplicate signature are removed. Normalized workflow identity remains required. No casts or synthetic index signatures were added.

Maintainer-requested cleanup; no separate issue. The two commits separate the internal forwarding cleanup from CI contract ownership.

Contract and boundary impact

  • Owners: CLI option mapping, model query schema, failure-predicate modules, and CI artifact parsing/classification.
  • Contribution scope: ordinary internal refactoring; no new target execution or mutation authority. A new maintainer scope decision is not applicable.
  • CLI/MCP inputs, generated schemas, persisted Evidence, provider protocols and package dependencies retain their existing behavior. Optional-field omission is preserved.
  • CI classification implementation and proof/unknown handling are unchanged; the declarations now use the same concrete records as the report API and normalized-run producer.

Validation performed

Executed with Node 24.18.0 / npm 11.16.0:

  • Six existing workflow/test files: 105 tests passed, including raw-binary CLI admission and real local CLI/MCP model-evidence paging.
  • Four CI boundary files: 64 tests passed, covering classification, request budgets, workflow normalization and static artifacts. These runs cover 148 distinct tests across nine files (one file overlaps).
  • npm run check:fast — typecheck and lint passed.
  • npm run knip — passed after refreshing this worktree's stale pre-build cache.
  • Formatting checks on all 11 changed files and git diff --check — passed.
  • Independent source review found no remaining consumers of removed exports and no behavior or evidence-contract regression.

No real Hopper/Ghidra, device or Windows execution was performed; this cleanup adds no provider behavior. Hosted CI is separate from these local results.

Author readiness

Human owner: @morluto

  • 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/6181 **Author:** [@morluto](https://github.com/morluto) **Created:** 10/21/2026 **Status:** ✅ Merged **Merged:** 10/21/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `codex/legacy-cleanup-20261022` --- ### 📝 Commits (2) - [`c50f5c7`](https://github.com/morluto/rea/commit/c50f5c7b6a7f33b6d71fc2a6ebe5ede420b1ff6c) refactor: remove obsolete internal forwarding APIs - [`7735aa5`](https://github.com/morluto/rea/commit/7735aa51be53a08ee45ecf0efabd0e9fac28cd7c) refactor(ci): centralize failure classification contracts ### 📊 Changes **11 files changed** (+68 additions, -117 deletions) <details> <summary>View changed files</summary> 📝 `scripts/ci/artifacts.d.mts` (+39 -13) 📝 `scripts/ci/failure-report.d.mts` (+1 -53) 📝 `scripts/ci/failure-report.mjs` (+0 -2) 📝 `src/application/Uninstall.ts` (+0 -1) 📝 `src/application/Update.ts` (+0 -1) 📝 `src/cli/options.ts` (+14 -25) 📝 `src/cliLogging.test.ts` (+4 -10) 📝 `src/domain/analysisView/analysisView.ts` (+1 -1) 📝 `src/domain/analysisView/modelArtifactView.ts` (+1 -5) 📝 `tests/boundary/filesystem/ciFailureReport.test.ts` (+3 -3) 📝 `tests/boundary/filesystem/ciFailureReportBudget.test.ts` (+5 -3) </details> ### 📄 Description ## Summary Remove internal forwarding APIs whose callers already have canonical owners. Native CLI flags now map directly to analysis options, failure predicates are imported from their own modules, and model-view requests import their schema from the model query contract. The CI report previously forwarded `classifyFailure` with a second, different handwritten declaration. CI run/job metadata and parsed static evidence now live with the artifact classifier and producer. The report and tests consume those shared contracts directly; the forwarding export and duplicate signature are removed. Normalized workflow identity remains required. No casts or synthetic index signatures were added. Maintainer-requested cleanup; no separate issue. The two commits separate the internal forwarding cleanup from CI contract ownership. ## Contract and boundary impact - Owners: CLI option mapping, model query schema, failure-predicate modules, and CI artifact parsing/classification. - Contribution scope: ordinary internal refactoring; no new target execution or mutation authority. A new maintainer scope decision is not applicable. - CLI/MCP inputs, generated schemas, persisted Evidence, provider protocols and package dependencies retain their existing behavior. Optional-field omission is preserved. - CI classification implementation and proof/unknown handling are unchanged; the declarations now use the same concrete records as the report API and normalized-run producer. ## Validation performed Executed with Node 24.18.0 / npm 11.16.0: - Six existing workflow/test files: 105 tests passed, including raw-binary CLI admission and real local CLI/MCP model-evidence paging. - Four CI boundary files: 64 tests passed, covering classification, request budgets, workflow normalization and static artifacts. These runs cover 148 distinct tests across nine files (one file overlaps). - `npm run check:fast` — typecheck and lint passed. - `npm run knip` — passed after refreshing this worktree's stale pre-build cache. - Formatting checks on all 11 changed files and `git diff --check` — passed. - Independent source review found no remaining consumers of removed exports and no behavior or evidence-contract regression. No real Hopper/Ghidra, device or Windows execution was performed; this cleanup adds no provider behavior. Hosted CI is separate from these local results. ## Author readiness Human owner: @morluto - [ ] 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. --- <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
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#7189
No description provided.