Uh oh!
There was an error while loading. Please reload this page.
chore(uts): fix legacy uts/test/ paths in spec cross-references - #502
Merged
Conversation
The uts specs were authored against a planned uts/test/<module>/ layout that never shipped - the tree landed as uts/<module>/. 91 cross-references across 75 files still pointed at the old layout (mostly the boilerplate "See uts/test/realtime/unit/helpers/mock_websocket.md ..." / mock_http.md header lines, plus scattered "corresponding test" pointers), all of them dead paths. Mechanical rewrite of uts/test/<path> -> uts/<path>, applied only where the corrected target file exists (validated per unique path before rewriting). Deliberately excluded: - the proxy infrastructure references in the realtime proxy specs (uts/test/realtime/integration/helpers/proxy.md and uts/test/proxy/) - those lines are rewritten by the proxy.md relocation on fix/uts-proxy-liveobjects-spec; changing them here would conflict - four references to uts/test/realtime/unit/client/client_options.md in realtime_client.md - that file never existed under any layout (completion-status.md records RSC1/RSC1a-c coverage as realtime_client.md itself), so these need a spec decision (write the planned file or reword the sections), not a path fix Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Found by validating every backticked uts/*.md path in the tree: - rest_fallback.md pointed RSL1k at uts/rest/unit/publish.md, which does not exist; the RSL1k (idempotent publish) unit coverage lives in uts/rest/unit/channel/idempotency.md - realtime_client.md's RSC1b pointer targeted the never-written client_options.md; RSC1b (error when no auth method available) is covered by uts/rest/unit/auth/auth_scheme.md (rest/unit/RSC1b/no-auth-method-error-0) The remaining three client_options.md references (RSC1/RSC1a/RSC1c) are left as-is deliberately: no REST-side spec covers key-vs-token constructor detection, so they mark a genuine coverage gap for a spec owner to resolve rather than a path to rewrite. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
ttypic
approved these changes
Jul 8, 2026
Uh oh!
There was an error while loading. Please reload this page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Intent
The UTS specs were authored against a planned
uts/test/<module>/directory layout that never shipped — the tree landed asuts/<module>/. As a result, 91 cross-references across 75 spec files still point at paths that have never existed in this repository, so anyone (or any tooling) following them finds a dead path. This PR is the mechanical cleanup, discovered while fixing the objects proxy specs (#501).What changed
Commit 1 — a pure
uts/test/<path>→uts/<path>rewrite, applied only where the corrected target file was verified to exist (each of the 26 unique referenced paths was checked before rewriting). No content changes — 90 insertions / 90 deletions, one-for-one. The bulk is repeated boilerplate header lines:realtime/unit/helpers/mock_websocket.mdrest/unit/helpers/mock_http.mdrest/unit/rest_client.mdCommit 2 — two additional broken cross-references found by validating every backticked
uts/*.mdpath in the tree (not just theuts/test/class), each retargeted to verified coverage:rest_fallback.md: RSL1k pointed at nonexistentuts/rest/unit/publish.md→ nowuts/rest/unit/channel/idempotency.md(where the idempotent-publish unit coverage actually lives)realtime_client.md: the RSC1b pointer targeted the never-writtenclient_options.md→ nowuts/rest/unit/auth/auth_scheme.md(rest/unit/RSC1b/no-auth-method-error-0)Deliberately excluded (and why)
uts/test/realtime/integration/helpers/proxy.mdin the 7 realtime proxy specs, and twouts/test/proxy/directory mentions) — those exact lines are rewritten by the proxy.md relocation commit onfix/uts-proxy-liveobjects-spec([AIT-1106] fix(uts): correct objects proxy specs and harden proxy rule/timeout guidance #501 chain). Fixing them here as well would only manufacture merge conflicts; they are covered there.client_options.mdinrealtime/unit/client/realtime_client.md(the RSC1/RSC1a/RSC1c "See:" line and the two constructor-table rows) — this file has never existed under any layout, and no REST-side spec covers key-vs-token constructor detection (RSC1aappears only incompletion-status.mdandrealtime_client.mditself). These are left in place deliberately: they mark a genuine coverage gap for a spec owner to resolve — either write the planned REST constructor spec or amend the sections andcompletion-status.md— rather than a path to rewrite. A rewrite would merely hide the gap.Verification
uts/*.mdpath leaves exactly two unresolved classes — the proxy references owned by [AIT-1106] fix(uts): correct objects proxy specs and harden proxy rule/timeout guidance #501 and the three flaggedclient_options.mdreferences.git diff --checkclean; no spec content touched beyond the path strings.🤖 Generated with Claude Code