refactor(harness): remove retired server graph composition (SAP-3091) - #910
Conversation
|
Warning Review limit reachedNext included review available in 59 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (10)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
gwitwer
left a comment
There was a problem hiding this comment.
Approving. Watcher lifecycle checked: the per-session and per-created-agent leases are unchanged and onLastLeaseReleased still fires the same discovery invalidation. Two notes: the #892 changeset says the retired routes return 410 and this one says 404, both harness minors in the same release, so one should be edited before the version PR; and the new generic /api JSON 404 applies to every unknown API path, which is an improvement but wider than the changeset describes.
Preserve the reviewed history while updating the stack for review fixes.
Describe the final authenticated 404 contract consistently across the combined release and document JSON responses for every unknown API path. Refs: SAP-3091
Preserve the reviewed history while updating the stack for review fixes.
Primary change type
Problem and motivation
The server still instantiated the retired project graph builder, store, providers and watcher lifecycle after supported browser callers had been removed.
Summary and scope
Remove legacy route registration, graph instances/events, active-scope ownership, prerequisites, refresh bookkeeping and teardown. Keep accepted discovery evidence, synchronous pre-connect invalidation, publication freshness fences, shared watcher leases and per-agent Canvas. Add a generic authenticated JSON API 404 before the SPA fallback for all unknown /api paths, including the removed graph endpoints. Reconcile both retirement changesets to this final response contract. This layer disconnects the implementation; the final layer deletes it.
Related work
Related issue or discussion: SAP-3091. Part of the authorized cleanup stack above #892 and #893, targeting
main. The seven layers are intended to merge and ship together. Updated layers require maintainer approval before merge.Validation
Review-fix verification on cumulative source
5bfed981, including currentmain(8679d745). Server and browser typechecks also passed on each of the seven isolated PR heads.The browser override selects the installed Google Chrome, temporary output paths and
pnpm exec vite; it preserves the checked-in tests and assertions. All 16 focused map/style/project-tab cases passed, including light/dark computed styles, project/agent viewport restoration, offscreen recovery, automatic fitting, auth isolation and layout recovery. The viewport and metadata regressions failed before their fixes. The new viewport and project-altitude tests also passed on #907's own intermediate tree (10 cases).An initial three-worker Harness run failed one archive-wiring case; the affected file passed unchanged 8/8, followed by the complete passing two-worker run above. The
mainintegration passed 263 focused cases, and #892's resolved auth mock passed 4/4 on its own tree. No tests or admission guards were weakened.All PR heads include
main's deliberate removal of the duplicate Claude workflow in #886. The reviewed commits remain in history; the stack update uses ordinary fast-forward pushes. Fresh build hashes and the earlier package/smoke evidence are recorded in the retirement record. Signed macOS installer/upgrade validation remains SAP-3086.Tests and documentation
Retained discovery freshness, rescan, shared watch leases and Studio wiring tests. Both retirement changesets now describe the final authenticated JSON 404; the release note also explains that every unknown /api path uses this fallback.
Compatibility and release impact
Security
AI assistance
Codex implemented the cleanup and test/doc migrations, traced retained callers, and checked the resulting diffs. Automated checks above and independent read-only review provide implementation evidence; maintainer review is still required.
Checklist
CONTRIBUTING.md, and this contribution follows the direct-PR or issue-first policy.