[github-actions]

Automated daily resync of the committed mirrors under docs/content/
via npm run sync-hive-docs and npm run sync-sibling-docs.

This PR was opened with GITHUB_TOKEN, so GitHub does not start
pull_request workflows for it. The refresh run instead dispatches
Build, TypeScript & Lint Check, Vitest, npm audit, Internal Links
and Markdown Lint on the PR branch; their check-runs land on the
head SHA as usual.

Refresh run: https://github.com/hivecommons/docs/actions/runs/41980614246

Refs #496

The hive sweep merges this PR once CI is green.

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign clubanderson for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✅ Deploy Preview for hivecommons-docs canceled.

Name	Link
🔨 Latest commit	8393202
🔍 Latest deploy log	https://app.netlify.com/projects/hivecommons-docs/deploys/6aec2bd162e06ebfef1bc7e0

[hivecommons-hive]

needs-human: GitHub Actions is holding this PR's workflow runs for approval, and Hive cannot start them. /ok-to-test on this repository belongs to Prow, which only accepts it from its trusted users, and hivecommons-hive[bot] is not one. Hive will not post the command again on this PR.

A maintainer can comment /ok-to-test (plus /lgtm and /approve for tide), or install .github/workflows/hive-ok-to-test.yml (hivectl ok-to-test-template) so the repository's own GITHUB_TOKEN approves trusted same-repo bot runs on Hive's command.

[hivecommons-hive]

This refresh cannot merge as-is: Run unit tests is red on head 1bdfd31 (job 127090048147), and the failures are caused by the one non-mirror change in the diff, not by flake. The mirrored markdown itself looks fine (link rewrites only, e.g. docs/content/hive/env-vars.md:129; no new scripts or external fetches).

What happened. This is the first scheduled run where heal mode actually healed: scripts/sync-hive-docs.files.json:212-217 gains integrations/cline.md and integrations/forges.md. Two things in the repo are coupled to that list and break:

1. Nav guard — src/__tests__/page-map-adr-nav-drift.test.ts:20 ("lists every synced page in NAV_STRUCTURE_HIVE") fails because src/app/docs/page-map.ts still lists only integrations/clanker-flue.md (:157); the two healed pages are synced but not in the nav. This is exactly the contradiction #625 fixes for future heals; it does not retroactively fix this PR, and the refresh workflow's add-paths does not include page-map.ts anyway.

2. Drift tests use the live manifest as a fixture — scripts/sync-hive-docs.main.test.ts:327-333 builds upstream = [...listed, "integrations/cline.md", "integrations/forges.md", …] from the real sync-hive-docs.files.json and then asserts those two names are reported as unlisted (:375, :378, :408, :410, :433). Now that they are listed, five tests fail on assertions like expected … not to contain 'integrations/cline.md'. Same pattern at sync-hive-docs.drift.test.ts ("records src/docs markdown pages that Case 2 pushed to GitHub" — expects a GitHub URL for forges.md, gets /docs/hive/integrations/forges). The tests hard-code real upstream filenames that heal mode was always going to add.

Suggested path (a maintainer or the hive needs a separate PR to main; this bot branch is regenerated daily and only carries mirror paths):

• add { 'Cline': 'integrations/cline.md' } and { 'Forges': 'integrations/forges.md' } (titles per each page's first #) to the integrations section of NAV_STRUCTURE_HIVE in src/app/docs/page-map.ts;
• switch the drift fixtures in sync-hive-docs.main.test.ts / sync-hive-docs.drift.test.ts to synthetic names (e.g. integrations/zz-fixture-a.md) or filter them against listed, so they stop depending on what upstream happens to ship.

Once that lands on main, the next daily refresh regenerates this branch and should go green. @clubanderson flagging since you are the OWNERS approver; I have not changed anything.

— hive: agent=reviewer-2 backend=copilot model=claude-fable-5.1 copilot=1.0.88

[hivecommons-hive]

Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor.

hive/awaiting-ci: pushed a prettier-only fixup for scripts/sync-hive-docs.main.test.ts (the sole format:check failure; main is green). CI pending — sweep will merge when green.

---

🐝 Hive Agent: scanner | Instance: hosted-available-oke-11-placeholder-r05x | SHA: unknown

— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88

Review findings from ci-maintainer (folded here because this head already carries its hive review):

docs-currency re-review @ 6ddeeef (delta from 1bdfd31)

Fixed: src/app/docs/page-map.ts:159-160 adds integrations/cline.md and integrations/forges.md to the "Integrating with Hive" sidebar; titles match the synced pages' H1s (docs/content/hive/integrations/cline.md:3, forges.md:3). Prior docs-currency finding resolved.

Still blocking — the delta leaves CI red at this head:

1. scripts/sync-hive-docs.drift.test.ts:234-250 still uses the real integrations/forges.md as an "unsynced" fixture. rewriteLinks resolves routes from scripts/sync-hive-docs.files.json (sync-hive-docs.ts:10,37), and this PR now lists integrations/forges.md there (files.json:217), so the link rewrites to /docs/hive/integrations/forges and unsynced stays empty → assertion at :247 fails ("Run unit tests" job 127094784087). The synthetic-name rename was applied only to sync-hive-docs.main.test.ts; apply the same to drift.test.ts (also :223 uses integrations/cline.md, which passes today only because it's a literal report string).
2. Prettier fails on scripts/sync-hive-docs.main.test.ts:538 — the renamed line exceeds the print width ("TypeScript & ESLint" job 127094783362). Run npm run format:check -- --write / prettier on the file.

Review findings from adjudicator-3 (folded here because this head already carries its hive review):

Delta re-review (intent-alignment), read at 6ddeeef and the newer head fc5e70f.

Previous findings: all three are fixed — src/app/docs/page-map.ts:159-160 now lists integrations/cline.md / integrations/forges.md (titles match the synced pages' H1s), and scripts/sync-hive-docs.main.test.ts:332-333 uses synthetic drift-sibling-* names.

One in-scope blocker remains — the fix commits leave CI red on the same files they touch:

1. Prettier fails on scripts/sync-hive-docs.main.test.ts (TypeScript & Lint Check, run 41983887051 at fc5e70f; also at 6ddeeef). Two lines exceed printWidth: 80 (.prettierrc.json): fc5e70f line 392 expect(fs.existsSync(outPath("integrations/drift-sibling-b.md"))).toBe(false); and line 454 the "integrations/drift-sibling-b.md": "# Forges\n…" entry (at 6ddeeef also line 538, the unwrapped ternary). Fix: npx prettier --write scripts/sync-hive-docs.main.test.ts.
2. At 6ddeeef scripts/sync-hive-docs.drift.test.ts:234,242 still used real integrations/forges.md, which is now in sync-hive-docs.files.json:217, so rewriteLinks emits a site route and Vitest failed (run 41982245874). This is fixed in fc5e70f (drift-sibling.md); noting only so the record is complete.

Scope otherwise matches the title: the mirror resync plus the nav/test follow-ups the previous review asked for; no unrelated changes.

Review findings from reviewer-2 (folded here because this head already carries its hive review):

The only red check (TypeScript & ESLint → npm run format:check) is two Prettier line-wraps in scripts/sync-hive-docs.main.test.ts, introduced by the two commits stacked on the bot's resync.

I reproduced it against this head (fc5e70f) with the repo's prettier@3.9.10 + .prettierrc.json; --write changes exactly two spots:

• scripts/sync-hive-docs.main.test.ts:392 — expect(fs.existsSync(outPath("integrations/drift-sibling-b.md"))).toBe(false); exceeds the print width; Prettier wants .toBe(\n false\n);
• scripts/sync-hive-docs.main.test.ts:454 — the "integrations/drift-sibling-b.md": "# Forges\nSee [new](../new-root.md).\n", stub entry; Prettier wants the value on its own line.

fc5e70f's message says "wrap heal-mode ternary", so a wrap was attempted, but these two lines (both renamed to the synthetic drift-sibling-b fixture in 6ddeeef) were missed. npx prettier --write scripts/sync-hive-docs.main.test.ts and a push clears the gate; everything else (build, vitest, links, markdownlint, audit) is green.

Not a defect, for context: the hand-added nav entries in src/app/docs/page-map.ts:159-160 (Cline, Forges) are what #625 will produce automatically once heal mode edits NAV_STRUCTURE_HIVE itself. The two PRs are not duplicates (different mechanism), but both touch scripts/sync-hive-docs.main.test.ts and scripts/sync-hive-docs.drift.test.ts, so whichever lands second will likely need a rebase.

Evidence bundle `#6268393202` sha256:6cb3181873d17059d0fa8ecdc1bb0b05043ec585b746e718c1b81cbe8e376883 — download from the dashboard or `hivectl review evidence #626`.

[hivecommons-hive]

Still red at 6ddeeef, for two concrete reasons; both are one-step fixes.

1. scripts/sync-hive-docs.drift.test.ts:233-247 has the same fixture collision the fix commit removed from main.test.ts. The rewriteLinks unsynced-reference collection test still uses the real integrations/forges.md as its "unsynced" page (line 233, [a](integrations/forges.md)) and asserts it is pushed to a GitHub URL (line 246-248). But the resync commit 1bdfd31 healed integrations/forges.md into scripts/sync-hive-docs.files.json (+6 lines, entries for integrations/cline.md and integrations/forges.md), so rewriteLinks now resolves it to the site route and CI fails exactly there:
AssertionError: expected '[a](/docs/hive/integrations/forges) …' to contain '[a](https://github.com/hivecommons/hi…' at drift.test.ts:247. Renaming the fixture to a synthetic page (e.g. integrations/drift-sibling-b.md, matching what 6ddeeef did in main.test.ts:332-333) in lines 233, 234, 240-253 fixes it.

2. Prettier. The TypeScript & ESLint job fails only on [warn] scripts/sync-hive-docs.main.test.ts — npx prettier --write scripts/sync-hive-docs.main.test.ts and recommit.

Context for maintainers: this PR is the first real heal run, and it shows the exact gap #625 closes — heal appended two pages to files.json without touching src/app/docs/page-map.ts, so the #616 nav guard failed and 6ddeeef had to add the two nav lines by hand (page-map.ts:159-160). Those two lines match what #625's addToHiveNav would generate ({ '<first # heading>': '<target>' }), so landing #625 and adding page-map.ts to the workflow's add-paths (#627) stops this from recurring.

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88