docs: HexoKit Banner Sweep (wt)

[sahil-noon]

Meta

Change ID	Type	Confidence	Plan	Review
2qsh	docs	4.9/5.0	3/3 tasks, 9/9 acceptance ✓	✓ 1 cycle

Impact	+/−	Net
raw	+295 / −5	+290
true	+1 / −1	+0
└ impl	+1 / −1	+0
└ tests	+0 / −0	+0

_{excludes fab/, docs/ · generated by fab-kit v2.25.0}

Pipeline: intake ✓ → apply ✓ → review ✓ → hydrate ✓ → ship → review-pr

Summary

Adopts the revised readme-extraction rule 1 blockquote from the HexoKit rebrand (plan row C7, gated on shll change ttoa / sahil87/shll#98): the first line under the README H1 becomes > Part of [HexoKit](https://hexokit.com) — see all projects there., removing the two-brand split the rename exists to fix. A repo-wide audit found no present-tense run-kit product mentions on wt's live surfaces, so the banner is the only content edit; rk substrate, shll.ai install and command-reference URLs, "shll toolkit" prose, and historical run-kit mentions in docs/memory/ and fab/ are deliberately untouched (plan D2/D11/D14, Phase 2/3 rows own them).

Changes

• README blockquote (the one mandated edit) — README.md:3
• Present-tense run-kit product mentions → HexoKit: none on live surfaces (audit dispositions recorded in the intake)
• Explicitly unchanged: install URLs, command-reference URL, "shll toolkit" prose, repo links, code/tests
• Conformance verification — the standard's § Verifying conformance checklist runs clean; go test ./... reproduces only the pre-existing TestCreate_InitFailureInteractive_OpenAnyway failure (identical on main, unrelated)
• Memory: wt-cli/toolkit-standards-conformance receipt re-verified against the PR-branch revision, with a design decision on auditing landed-but-unreleased standard revisions

[Copilot]

🟡 Changes recommended

Documentation and generated-receipt inconsistencies should be corrected before approval.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Updates the README toolkit banner from shll to HexoKit and records related Fab and conformance documentation.

Changes:

• Replaces the README banner.
• Adds Fab intake, plan, status, and history records.
• Refreshes conformance documentation and the generated memory index.

File summaries

File	Description
README.md	Updates the toolkit banner.
fab/changes/260911-2qsh-hexokit-banner-sweep/plan.md	Defines requirements and verification receipts.
fab/changes/260911-2qsh-hexokit-banner-sweep/intake.md	Records scope and audit assumptions.
fab/changes/260911-2qsh-hexokit-banner-sweep/.status.yaml	Tracks pipeline status and impact.
fab/changes/260911-2qsh-hexokit-banner-sweep/.history.jsonl	Records change history.
docs/memory/wt-cli/toolkit-standards-conformance.md	Records standards conformance.
docs/memory/wt-cli/index.md	Updates the generated memory index.

Review details

Suppressed comments (4)

docs/memory/wt-cli/toolkit-standards-conformance.md:90

• R3/A-006 and the T003 receipt say every run-kit occurrence in docs/memory/ is unchanged and the count remains 38, but this newly added cross-reference introduces run-kit twice outside fab/changes/. Please either reword this source note so it does not add the historical token, or update the scope fence, count, and acceptance receipt to account for the intentional new references.

- Source (`readme-extraction` rule 1 revision, `260911-2qsh`): `README.md` line 3 (the HexoKit toolkit blockquote). Upstream: sahil87/shll `docs/site/standards/readme-extraction.md` via change `260911-ttoa-hexokit-banner-and-policy` / [shll#98](https://github.com/sahil87/shll/pull/98); sequencing and the brand/substrate/historical naming tiers (why `run-kit` mentions in `docs/memory/` and `fab/` are left as-is) are owned by the HexoKit rebrand plan in the sahil87/run-kit repository (`fab/plans/sahil/26-09-10-hexokit-rebrand.md`, row C7).

fab/changes/260911-2qsh-hexokit-banner-sweep/intake.md:85

• docs/memory/wt-cli/log.md is not updated in this PR and contains no 2026-09-11/2qsh entry, despite this receipt claiming it was regenerated. Because that file is generated, please include the generated log change or remove / log.md from the hydrate claim so the change record matches the tree.

- **Files changed in this repo**: `README.md` (1 line). Hydrate: `docs/memory/wt-cli/toolkit-standards-conformance.md` (+ regenerated `docs/memory/wt-cli/index.md` / `log.md` via `fab docs-index`).

fab/changes/260911-2qsh-hexokit-banner-sweep/plan.md:98

• The final PR includes hydrate changes that add new HexoKit/run-kit hits under docs/memory/ (notably toolkit-standards-conformance.md:90), so this T003 receipt is only true for the pre-hydrate tree. Because the plan defines hydrate artifacts as part of the change, rerun the audit after hydrate or explicitly scope the claim to apply-time and distinguish intentional receipt cross-references from unchanged historical mentions.

- **T003 scope fence** — repo-wide grep: the only `hexokit` hit outside this change folder is `README.md:3`; `run-kit` hit count excluding this change folder is unchanged at 38 (all `docs/memory/`, `fab/`, and the `skill_test.go:97` comment); `git diff --name-only main -- . ':!fab/changes'` = `README.md` only.

fab/changes/260911-2qsh-hexokit-banner-sweep/plan.md:47

• This design decision is stale by the time the plan was applied: it says the installed shll remains pre-C1 until PR #98 merges and ships, but shll v0.1.31 already includes that merged PR. Keeping this as the current rationale makes the source-of-truth and the rejection of release-based auditing misleading; revise it to record the released-version audit, or explicitly preserve it as an intake-time snapshot and document the later rerun.

#### Revised standard text sourced from the C1 PR branch, not the installed `shll`
**Decision**: The mandated blockquote is taken verbatim from shll PR #98's diff to `docs/site/standards/readme-extraction.md` (shll change `ttoa`), because the installed `shll standards readme-extraction` still prints the pre-C1 line until that PR merges and ships.
**Why**: The rebrand plan gates C7 on C1 being *up and reviewed*, not released; the blockquote text has no pipeline coupling (the consuming site's extractor matches any leading blockquote), so ordering against the shll release buys nothing and would block Phase 2's X1.
**Rejected**: Waiting for a shll release carrying the revised standard before editing satellite READMEs — delays X1 for no correctness gain; the conformance receipt records the change/PR as the audited revision instead of a release version.

• Files reviewed: 7/7 changed files
• Comments generated: 2
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[sahil-noon]

Fixed — the receipt now cites shll v0.1.31 (the release carrying shll#98) and the tagged docs/site/standards/readme-extraction.md text as the audited revision; the (260911-2qsh) token is this change's provenance citation, not a release, and the unreleased/landed-but-unreleased wording and its design decision were removed. It also records that the locally installed shll (v0.1.30) lagged the release, which is why the tagged source was read directly. (918f3af)

[sahil-noon]

Fixed — the intake now records shll#98 as an open draft at intake time, merged 17:51Z and released as shll v0.1.31 at 17:53Z the same day, with Assumption 2 marked superseded in effect; the plan's design decision and the T003 receipt were corrected to match (apply-time snapshot, post-hydrate note). (918f3af)