Revert "Repair upstream GitHub references for SDK v0.55 and CometBFT v0.40" (#336)

This reverts commit f84f83b.

Author: evanorti

.claude/skills/pr-description/SKILL.md

@@ -154,17 +154,13 @@ Two things are version-pinned and do not follow the freeze on their own:
 grep -rn 'description: "Version: v' sdk/next --include='*.mdx'
 ```
 
-**GitHub links pinned to the previous release branch.** Pages link into the product repo at `release/v0.<N>.x` (SDK) or `v0.<N>.x` (CometBFT), and those refs keep pointing at the old version. Use the checker rather than a find-and-replace:
+**GitHub links pinned to the previous release branch.** Pages link into the product repo at `release/v0.<N>.x` (SDK) or `v0.<N>.x` (CometBFT), and those refs keep pointing at the old version:
 
 ```bash
-node scripts/versioning/check-github-refs.js --product <product> --targets next --json /tmp/flags.json
+grep -rhoE 'github\.com/cosmos/cosmos-sdk/(blob|tree)/release/v[0-9.]+x' <product>/next --include='*.mdx' | sort | uniq -c
 ```
 
-Review the report, then apply the safe rewrites with `--fix`. It bumps only what it can prove is safe and flags the rest.
-
-Do not blind-replace these by hand. Pinned tags and commit SHAs are deliberate historical citations, and bumping a ref under a `#L` line anchor can leave the link working while pointing at unrelated code. See the GitHub link section in [`scripts/versioning/CLAUDE.md`](scripts/versioning/CLAUDE.md) for the rules and the measured failure rates.
-
-Hand the `--json` output to the [`update-stale-refs`](.claude/skills/update-stale-refs/SKILL.md) skill, which decides whether a flagged link means the page's prose needs a correction.
+Do not blind-replace these. Pinned tags and commit SHAs are deliberate historical citations, and bumping a ref under a `#L` line anchor can leave the link working while pointing at unrelated code. See the GitHub link section in [`scripts/versioning/CLAUDE.md`](scripts/versioning/CLAUDE.md) for the rules and the measured failure rates.
 
 A stale ref is often a symptom rather than the problem. A link that 404s at its current ref usually means the prose describes something upstream deleted, so check what the page claims before repointing the URL.
 

.claude/skills/update-stale-refs/SKILL.md

@@ -64,7 +64,7 @@ purposes.
 We'll start a kvstore application, which was installed at the same time as
 `abci-cli` above. The kvstore just stores transactions in a Merkle tree. Its
 code can be found
-[here](https://github.com/cometbft/cometbft/blob/v0.40.x/abci/example/kvstore/kvstore.go).
+[here](https://github.com/cometbft/cometbft/blob/v0.38.x/abci/example/kvstore/kvstore.go).
 
 Start the application by running:
 
@@ -104,7 +104,7 @@ response.
 
 The server may be generic for a particular language, and we provide a
 [reference implementation in
-Golang](https://github.com/cometbft/cometbft/tree/v0.40.x/abci/server). See the
+Golang](https://github.com/cometbft/cometbft/tree/v0.38.x/abci/server). See the
 [list of other ABCI implementations](https://github.com/tendermint/awesome#ecosystem) for servers in
 other languages.
 

CLAUDE.md

@@ -369,7 +369,7 @@ proposing the next block).
 
 By default, CometBFT checks whether a peer's address is routable before
 saving it to the address book. The address is considered as routable if the IP
-is [valid and within allowed ranges](https://github.com/cometbft/cometbft/blob/v0.40.x/p2p/netaddress.go#L259).
+is [valid and within allowed ranges](https://github.com/cometbft/cometbft/blob/v0.38.x/p2p/netaddress.go#L258).
 
 This may not be the case for private or local networks, where your IP range is usually
 strictly limited and private. In that case, you need to set `addr_book_strict`

cometbft/latest/docs/app-dev/Using-ABCI-CLI.mdx

@@ -63,7 +63,7 @@ Prior to version `v0.38.x`, floats were not supported as query parameters.
 When the validator set changes, the ValidatorSetUpdates event is published. The
 event carries a list of pubkey/power pairs. The list is the same as what
 CometBFT receives from the ABCI application (see the [EndBlock
-section](https://github.com/cometbft/cometbft/blob/v0.40.x/spec/abci/abci++_methods.md#endblock) in
+section](https://github.com/cometbft/cometbft/blob/v0.38.x/spec/abci/abci++_methods.md#endblock) in
 the ABCI spec).
 
 Response:

cometbft/latest/docs/core/Running-in-production.mdx

@@ -39,7 +39,7 @@ cometbft testnet --help
 
 The `genesis.json` file in `$CMTHOME/config/` defines the initial
 CometBFT state upon genesis of the blockchain ([see
-definition](https://github.com/cometbft/cometbft/blob/v0.40.x/types/genesis.go)).
+definition](https://github.com/cometbft/cometbft/blob/v0.38.x/types/genesis.go)).
 
 #### Fields
 
@@ -49,7 +49,7 @@ definition](https://github.com/cometbft/cometbft/blob/v0.40.x/types/genesis.go))
   chain IDs, you will have a bad time. The ChainID must be less than 50 symbols.
 - `initial_height`: Height at which CometBFT should begin. If a blockchain is conducting a network upgrade,
     starting from the stopped height brings uniqueness to previous heights.
-- `consensus_params` ([see spec](https://github.com/cometbft/cometbft/blob/v0.40.x/spec/core/data_structures.md#consensusparams))
+- `consensus_params` ([see spec](https://github.com/cometbft/cometbft/blob/v0.38.x/spec/core/data_structures.md#consensusparams))
     - `block`
         - `max_bytes`: Max block size, in bytes.
         - `max_gas`: Max gas per block.
@@ -71,7 +71,7 @@ definition](https://github.com/cometbft/cometbft/blob/v0.40.x/types/genesis.go))
   application will initialize the validator set upon `InitChain`.
     - `pub_key`: The first element specifies the key type,
     using the declared `PubKeyName` for the adopted
-    [key type](https://github.com/cometbft/cometbft/blob/v0.40.x/crypto/ed25519/ed25519.go#L36).
+    [key type](https://github.com/cometbft/cometbft/blob/v0.38.x/crypto/ed25519/ed25519.go#L36).
     The second element are the pubkey bytes.
     - `power`: The validator's voting power.
     - `name`: Name of the validator (optional).
@@ -565,7 +565,7 @@ library will deny making connections to peers with the same IP address.
 ### Upgrading
 
 See the
-[UPGRADING.md](https://github.com/cometbft/cometbft/blob/v0.40.x/UPGRADING.md)
+[UPGRADING.md](https://github.com/cometbft/cometbft/blob/v0.38.x/UPGRADING.md)
 guide. You may need to reset your chain between major breaking releases.
 Although, we expect CometBFT to have fewer breaking releases in the future
 (especially after the 1.0 release).

cometbft/latest/docs/core/Subscribing-to-events-via-Websocket.mdx

@@ -14,5 +14,5 @@ component—that's the best place to get started.
 
 To dig deeper, check out the [types package documentation][types].
 
-[data_structures]: https://github.com/cometbft/cometbft/blob/v0.40.x/spec/core/data_structures.md
+[data_structures]: https://github.com/cometbft/cometbft/blob/v0.38.x/spec/core/data_structures.md
 [types]: https://pkg.go.dev/github.com/cometbft/cometbft/types