chore: retire tooling superseded by the hub's fan-out kits

[bamr87]

Removes three pieces of local automation that the bamr87 hub's tools/fanout.sh + templates/ now own fleet-wide, and repairs the README that an unclean split from it-journey left behind.

Net: -2610 / +123 lines.

What was removed, and what now owns each job

linting/ (setup-lint-configs.sh, validate-lint-setup.sh, README.md)

Deployed .markdownlint.json / .yamllint.yml / .shellcheckrc / .editorconfig by iterating a hardcoded list of seven /Users/bamr87/github/<repo> paths. Verification:

• Three of those seven (ai-seed, ai-evolution-engine-seed, scripts) no longer exist under that root at all.
• It wrote into local checkouts — nothing it produced ever reached GitHub. Someone had to hand-commit in seven repos.
• Its README.md documented a configs/jekyll/ + configs/shell/ tree that was never committed to this repo.
• Its output is already materialised: this repo's .shellcheckrc and .markdownlint.json are byte-identical to what setup_shell_linting() writes, so running it was a no-op rewrite.

Now owned byfanout.sh --kit standardize --artifacts editorconfig (registry-driven, additive-only, PR-based across ~40 repos). This repo's .editorconfig is already byte-identical to the hub's, confirming the fan-out is the live path. The markdown rule is enforced by --kit prose / .github/workflows/markdown-oneline.yml.

The generated config files themselves (.shellcheckrc, .markdownlint.json) are kept — only the generator is retired.

.github.sh (1,565 lines)

Generated an entire .github/ tree with hand-rolled workflow YAML. Verification:

• Pinned to retired action versions: actions/upload-artifact@v3 and github/codeql-action@v2 (both shut down by GitHub in Jan 2025) and the archived actions/create-release@v1. It emitted immediately-failing CI — precisely the waste the fleet-pulse doctor loop exists to hunt.
• Ran mkdir -p logs/ at source time, before argument parsing — even --help littered the caller's cwd.
• Carried six SC2155 shellcheck warnings; dropping it clears them.
• Last touched 2025-08-21, authored as "IT-Journey Team".

Now owned by:

.github.sh produced	Hub owner	Already adopted here
CI workflow	templates/standard-ci/ci.yml	.github/workflows/ci.yml
Release workflow	templates/release-pipeline/	—
Code quality / CodeQL	full bamr87/.github gate	—
AI evolution workflow	templates/agent-context/claude.yml, fleet-pulse.yml	.github/workflows/claude.yml
copilot-instructions	agent-context kit CLAUDE.md	CLAUDE.md
.markdownlint.json, .yamllint.yml	(duplicated linting/; already in tree)	✅
dependabot.yml	nothing — contrary to policy	—

That last row is the point: the fleet's ALWAYS-LATEST policy (--kit deps-latest, docs/DEPENDENCIES.md) removes the exact pins Dependabot exists to bump.

example.sh

Three-line placeholder whose stated purpose was to show "the scripts folder is being tracked by git", in a repo that tracks twenty other scripts. Not superseded — simply dead.

README rewrite

README.md was two concatenated READMEs: a short "scripts directory" blurb welded onto a full "IT-Journey Scripts Collection" doc at line 8, with four U+FFFD replacement characters where emoji had been mangled (lines 8, 20, 23, 170) — fossil evidence of an unclean split from it-journey.

Rewritten as one coherent document: a tool index verified against git ls-files, per-tool quick starts, prerequisites, the dev/lint gates, and fleet context. Mojibake fixed. Every relative link verified to resolve. Passes tools/unwrap-prose.py --check (one paragraph per line).

install.sh kept, with a disambiguating note

Not deleted — it is the standalone path for users who don't have the hub checked out. The overlap with the hub's tools/setup.sh is now documented in both the install.sh header and the README:

	hub setup.sh → setup_script_cli_tools()	this repo's install.sh
CLI symlinks into ~/.local/bin	all six: forkme, stashme, git-init, project-wizard, rename-dir, create-package	project-wizard only
chmod +x every *.sh	✅	project-init.sh only
~/.project-wizard/ config dir	❌	✅
env.example copy	❌	✅
shell rc PATH update	via hub bootstrap	✅

So the hub is a strict superset for CLI installation, but install.sh uniquely creates the wizard's config directory. Running both is idempotent but redundant.

Follow-ups for the hub (out of scope here — separate repo)

1. Dangling github-setup reference. The hub's tools/setup.sh wires .github.sh as the github-setup CLI at three sites (lines 33, 919, 1089) plus help text at 1127. setup_script_cli_tools skips missing files gracefully, so nothing breaks, but the hub will keep advertising a command it can no longer install.
2. Issue/PR templates are a genuine gap..github.sh was the only thing producing ISSUE_TEMPLATE/*.yml and PULL_REQUEST_TEMPLATE/ — the hub's standardize kit does not seed either, though the hub has its own. Worth considering an issue-templates artifact.

Verification

• shellcheck --severity=warning install.sh — clean (the only shell file touched).
• python3 tools/unwrap-prose.py --check — passes.
• No U+FFFD remaining in any touched file.
• Untouched as required: forkme.sh, FORKME/, STASHME/, project-init.sh, git_init.sh, rename-directory.sh, create_package.sh, tools/unwrap-prose.py.

🤖 Generated with Claude Code