spec 010 D0 cleanup: probe key removed, both mechanisms measured - #79
Merged
Conversation
D0 is complete and both halves are answered. GitBook automatically redirects a Git-synced SUMMARY.md rename. The old path returned 307 to the new one within 25 seconds of #77 merging, with no redirects block anywhere in the repo. .gitbook.yaml section-level redirects are also read and honoured, and the site plan permits them. The probe key — a path that had never existed and returned 404 — began redirecting after #78 published, while a control key absent from the block kept 404ing. That control is what makes it a measurement rather than a hope. An extra finding worth more than either: the redirect VALUE is a repository path, and GitBook resolves it to wherever that page currently publishes. The probe pointed at contents/CommandsCommandDispatcherandProcessor.md and landed on commands-processors-and-dispatchers/..., the post-rename URL. So a redirect entry does not go stale when its page moves again — which matters for a spec that will move some pages more than once. The probe key has done its job and is removed. The real redirect for #77's rename stays as a safety net, since nothing yet establishes that automatic redirects persist over time. Verified again after the edit: zero bytes outside printable ASCII, parses as YAML, structure block intact, target exists, no leading slashes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012tcdwxVb8NmKaX2S6fvyFg
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes out D0. The probe key promised for removal in #78 comes out here.
Both halves answered
SUMMARY.mdrename?.gitbook.yamlredirects read on this site, and does the plan permit them?The control is what makes the second a measurement rather than a hope.
Fingerprint
Cached responses all report
200, so status alone proves nothing. The discriminators:location:headerThe finding worth more than either
The redirect value is a repository path, and GitBook resolves it to wherever that page currently publishes. The probe pointed at
contents/CommandsCommandDispatcherandProcessor.mdand landed oncommands-processors-and-dispatchers/…— the post-rename URL. So a redirect entry does not go stale when its page moves again, which matters for a spec that will move some pages more than once.What stays
The real redirect for #77's rename, as a safety net. Nothing yet establishes that automatic redirects persist over time — they may be tied to revision history, and one session cannot test that.
Re-verified after the edit: zero bytes outside printable ASCII, parses as YAML,
structure:intact, target exists, no leading slashes.🤖 Generated with Claude Code
https://claude.ai/code/session_012tcdwxVb8NmKaX2S6fvyFg