fork: re-align with upstream rtk-ai/rtk v0.38.0

[princess-myra]

What

Re-aligns the algolia fork with upstream rtk-ai/rtk v0.38.0 (300+
commits absorbed, last sync was v0.34.2 in March 2026).

This PR follows the re-fork strategy documented in CLAUDE.md
(restored in this same PR — see commit 7): instead of merging upstream
into main, the branch is created off upstream/master and our fork
patches are re-applied as small focused commits on top.

How to review

The PR diff against main is large (300+ commits absorbed = lots of
file moves, dep bumps, doc reorgs from upstream). That's not the diff
to look at. Look at the diff against upstream/master:

git diff upstream/master..HEAD

This is the actual algolia-specific delta: 53 files, +401 / -1980
(net negative — telemetry deletion dominates).

The 8 commits (each independently reviewable)

#	Commit	Why
1	fork: strip telemetry	No phone-home in algolia builds. Removes src/core/telemetry.rs, telemetry_cmd.rs, the Telemetry CLI variant, the maybe_ping() call, the ureq dep, the RTK_TELEMETRY_* env vars in release.yml, and all telemetry docs.
2	fork: skip rewrite for curl/wget pipes	Re-applied patch. Upstream's is_pipe_incompatible list still excludes curl/wget, so piping their output to jq/python would be broken by rtk curl's JSON compression.
3	fork: skip rewrite for shell function definitions	Re-applied patch. Upstream still has no guard against rewriting commands inside name() { … } bodies, which produces invalid rtk curl references at function-invocation time. Bug report preserved at bug-reports/2026-03-31-…md.
4	fork: bump version to 0.38.0-algolia.1	Distinguishes this build from upstream's v0.38.0.
5	fork: tighten semgrep rules — network access banned	Removed the ureq carve-out (it had no caller anymore). Now any network primitive is a hard error.
6	fork: rebrand and purge upstream references	Sed-style rewrite of rtk-ai/rtk → algolia/rtk in install instructions, rtk-ai.app → algolia repo, removed Homebrew section / Star History / Core team blocks, deleted upstream's docs-pipeline-contract.md. CHANGELOG historical references intentionally untouched.
7	docs: restore Fork Policy + Upstream Catchup Procedure in CLAUDE.md	These sections were originally added in 653a29e (March 2026) but lost during a previous catchup. Restoring them prevents the next catchup from accidentally going merge-based.
8	fork: post-rebuild cleanup	Cargo.lock auto-pruned 387 lines of stale ureq transitive deps; #[allow(dead_code)] on 16 telemetry-orphan helpers in tracking.rs; cargo fmt fix in config.rs.

Patches re-validated against upstream v0.38.0

Per the policy, every catchup re-tests fork patches against the new
base. Status of our 2 bug-fix patches:

• curl/wget pipe rewrite skip: Upstream's tokenizer-based rewriter
  (src/discover/registry.rs) marks find and fd as
  pipe-incompatible. Curl and wget are not on that list. Reproducer
  from bug-reports/2026-03-31-curl-python3-not-found-in-shell-functions.md
  still fails on a clean upstream build → patch still required.
• Shell function-definition skip: Upstream's rewrite_command() has
  no equivalent guard. Same reproducer also covers this case →
  patch still required.

Neither patch was made obsolete by upstream changes.

Verification

Built and tested locally on aarch64-apple-darwin with rustc 1.95.0
(matches CI's dtolnay/rust-toolchain@stable):

• cargo build — passes; auto-pruned 387 lines of stale ureq
  transitive deps from Cargo.lock (now committed)
• cargo test --all — 1679 passed, 0 failed, 6 ignored (the 6
  ignored are upstream's pre-existing #[ignore] tests)
• All 8 fork-specific tests pass (4 curl/wget pipe + 4 shell-function
  detection)
• cargo clippy --all-targets -- -D unsafe_code — passes (matches CI
  exactly)
• cargo fmt --all --check — clean
• Fork hygiene grep — clean (only historical CHANGELOG entry remains)

40 dead-code warnings remain. Verified that all 40 are present on a
clean upstream/master checkout — none introduced by this PR.

What I deliberately did NOT carry forward

• src/parser/error.rs — was added in upstream commit edab4e1 and
  later dropped by upstream; was dead code (#[allow(dead_code)], no
  callers) in our main.
• ROADMAP.md — algolia roadmap, but content was stale (talks about
  "establishing the fork as the standard if upstream remains inactive";
  upstream is very active). Drop in line with the "thin fork"
  principle. Easy to restore in a follow-up if desired.
• docs/TROUBLESHOOTING.md — algolia-specific install URLs, but
  upstream now has docs/guide/resources/troubleshooting.md at the
  new canonical location (rebranded with algolia URLs in commit 6).
  One troubleshooting doc instead of two.
• docs/filter-workflow.md, docs/images/gain-dashboard.jpg,
  .claude/skills/performance.md (replaced by performance/SKILL.md
  upstream).

If any of these turn out to matter, they're trivial to add back in a
follow-up PR.

Why this approach (vs merging upstream into main)

A previous draft of this PR used a 3-way merge from upstream/master
into main, producing 193 files / +22,374 / −6,964. Throwing it
away and re-forking from upstream/master (this PR) produced
53 files / +401 / −1,980 — same end state, ~30× smaller diff
against upstream, every patch in its own commit.

More importantly, the re-fork forced explicit patch re-validation
(each fork patch had to be re-applied with a justification), instead
of letting them be carried forward by inertia. That matches the
documented policy and the admin's note that "bugfixes are often
superseded by origin fixes".

The Fork Policy + Upstream Catchup Procedure restored in commit 7
documents this so the next catchup doesn't have to rediscover the
strategy.

CI gate

• cargo build
• cargo clippy --all-targets
• cargo test --all — including the 8 new fork tests in
  src/discover/registry.rs
• cargo fmt --check
• Fork hygiene grep returns zero (CHANGELOG historical refs
  excluded):
  bash rg -i 'brew install rtk[^-]|rtk-ai\.app|contact@rtk|"rtk 0\.\d+\.\d+"' --glob '*.md' --glob '*.rb' --glob '!CHANGELOG.md'

[princess-myra]

Once reviewed
we'll need to override main with this !

RTK_DISABLED=1 git fetch origin
RTK_DISABLED=1 git checkout main
RTK_DISABLED=1 git reset --hard origin/fork/upstream-realign-v0.38.0
RTK_DISABLED=1 git push --force-with-lease origin main