Repository navigation
fix(refs): stale postplan.tapetide.com defaults left from the rename - #31
Merged
Merged
Conversation
…name The docs base URLs, the openapi `servers` url, the CLI config example, two fetch.go comment examples and the brutal.sh env defaults all still named the pre-rename `postplan.tapetide.com`. The CLI's compiled-in default was already `agentdraft` (config.go DefaultAPIURL), so shipped behaviour was correct — but anyone copy-pasting the docs, running the openapi spec, or invoking brutal.sh with no env override was pointed at the old host. brutal.sh was the worst of these: its defaults sent the adversarial suite at the wrong deployment entirely.
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
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.
Found while reading
tests/brutal.shbefore running it: the adversarial suite's defaultAPI/CONTENTenv values still pointed at the pre-renamepostplan.tapetide.com, so anyone running it without explicit env overrides fired 198 assertions at the wrong deployment.Swept the whole tree — 10 stale references in 5 files:
tests/brutal.shAPI/CONTENT+ usage commentdocs/api.mddocs/openapi.yamlservers[0].urldocs/cli.mdconfig.jsonexamplecli/cmd/fetch.goShipped behaviour was already correct —
config.goDefaultAPIURLishttps://api.agentdraft.tapetide.com, so the CLI never used the old host. This is docs + test-harness + comments only, no code-path change.Verified: CLI still builds and vets clean (
fetch.gotouched), openapi still parses (servers: ['https://api.agentdraft.tapetide.com']), 0postplanreferences remain repo-wide.Separately flagged to the owner:
postplan.tapetide.comstill serves 200 as a live duplicate deployment (google_oauth_enabled:false, its own content_base_url) — that's an infra cleanup question, not part of this docs fix.