[hivecommons-hive]

The committed snapshot predates hivecommons/hive#13950 moving the agent runtime to src/crux, so its source links (trajectory, skillreg, manager_pause) 404 on GitHub and the offline fallback of check-internal-links sees stale content. This resyncs docs/content/ mirrors via npm run sync-hive-docs and npm run sync-sibling-docs.

Fixes #496 (needs-human: the scheduled hive-docs-refresh workflow still has to be added by a maintainer — the hive App cannot push .github/workflows/ files)

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

[netlify]

❌ Deploy Preview for hivecommons-docs failed. Why did it fail? →

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

[hivecommons-hive]

hive/awaiting-ci: 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

[hivecommons-hive]

Looks correct to me — this is a faithful regeneration, not a hand edit.

What I verified at f1ebb39:

• Checked out the PR head, ran npm ci && npm run sync-hive-docs && npm run sync-sibling-docs from package.json:16-17. git status is clean afterwards — the committed mirror is byte-identical to what the sync scripts emit today, so nothing was edited by hand or left out.
• The body's stated goal matches the diff: e.g. docs/content/hive/adr/0009-trajectory-review.md moves its source links from src/pkg/trajectory/… to src/crux/trajectory/…; https://github.com/hivecommons/hive/blob/v5/src/crux/trajectory/trajectory.go returns 200.
• Check internal doc links, markdownlint, Lint and build and unit tests are green.

One open question, not a defect in the diff: the netlify/hivecommons-docs/deploy-preview status is Deploy Preview failed. (and the three Netlify "rules" statuses with it). The repo's own Lint and build passes on the same head, so I could not tell from here whether this is the content or the Netlify side; the deploy log at the status URL would settle it before merge.

Issue-link note: the body uses Fixes #496 (needs-human: …) — the scheduled refresh workflow it mentions still needs a maintainer to add it under .github/workflows/, so #496 will auto-close on merge even though that part is outstanding.

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

[hivecommons-hive]

Decision needed: @clubanderson should this PR close #496 on merge (body says Fixes #496), given #496's primary ask — the scheduled hive-docs-refresh workflow — is explicitly left for a maintainer and would lose its open tracker?

The resync itself checks out; the only thing I'd change is the issue link.

Verified

• Every https://github.com/hivecommons/hive/blob/... link added by this diff (34 unique URLs, including the src/crux/... paths #496 lists for adr/0009, adr/0012 and running-at-level-6.md) returns HTTP 200 as of this review.
• The failing Netlify checks are not attributable to this diff: netlify.toml runs the same npm run build (next build) that the passing "Lint and build" check ran at f1ebb39, and the {{ … }} template-looking text in docs/content/promptargs/readme.md is already on main (34 occurrences) and deploys there. The Netlify log is external, so I can't say more than that.

Issue link — Fixes vs Refs

#496 is titled "…add a scheduled resync workflow" and frames the drift as a gate gap: a hand resync is the symptom fix, the workflow is the ask. This PR is the hand resync, and its own body says the workflow "still has to be added by a maintainer — the hive App cannot push .github/workflows/ files". With Fixes #496, GitHub closes #496 on merge and nothing open records that the workflow was never added — the exact drift #496 describes recurs next time hive moves a file. Refs #496 (needs-human: scheduled hive-docs-refresh workflow still to be added — App cannot push .github/workflows/) keeps the tracker alive and says why. A maintainer's call; I have not changed anything.

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

[hivecommons-hive]

Needs a decision, not a merge:

• the reviewer swarm returned requires_human @f1ebb39
• reviewer question: @clubanderson should this PR close [scanner] Committed Hive docs mirror drifts between hand resyncs — add a scheduled resync workflow #496 on merge (body says Fixes #496), given [scanner] Committed Hive docs mirror drifts between hand resyncs — add a scheduled resync workflow #496's primary ask — the scheduled hive-docs-refresh workflow — is explicitly left for a maintainer and would lose its open tracker?
• the automerge lane will not merge this unattended

Head: verdict requires_human @f1ebb39, 6/6 checks green, DCO yes, soak 0s of 30m0s.

What to do: approve this head (f1ebb39) to merge as-is, or leave a changes requested review (or reply /hive decision <what to change>) and the hive will push the fix.

How to release it:

• After reading the verdict, a trusted merger can submit a GitHub Approve review for the current head and the lane clears the hold on its next pass; /hive approve replies on a PR are acknowledged but not consumed.

_{Clear the cause and the hive re-evaluates on its next pass; the stage moves to stage/090-ready-for-human-merge, stage/095-pre-merge-soak or the merge queue on its own. Approval does not bypass CI, hold labels or other merge gates.}

[clubanderson]

/hive decision approve

Approving head f1ebb39 as-is: the diff is a plain mirror resync (43 files, all under docs/content/, no workflows, no secrets) and the 6 repo checks are green — the Netlify deploy-preview failures are the same pre-existing preview breakage seen on every recently merged docs PR, not a gate here.

On the reviewer question: the scheduled hive-docs-refresh workflow is still wanted and the hive App cannot push workflow files, so I'll push that piece myself. #496 should stay open as the tracker for it — if GitHub auto-closes it on merge via Fixes #496, I'll reopen it.

[clubanderson]

Owner approval for head f1ebb39 — see /hive decision approve above. Mirror-only resync; owner will push the scheduled workflow and keep #496 open.

[kubestellar-prow]

LGTM label has been added.

Details

Git tree hash: b103bead42a185aadcb2278591e15961d0e52820

[hivecommons-hive]

Decision recorded by @clubanderson for head f1ebb39. The hive is treating it as a changes requested review: this PR moves to the fixing stage and the author agent pushes a new head following your instruction verbatim. The review swarm then re-reviews that head; if it approves, the PR comes back for your merge approval.

[hivecommons-hive]

Supersession sweep found that this PR's claimed issue is already closed by another merged PR.

• Claimed issue: docs#496
• Closing PR: #499

This PR touches files the merged PR did not, so the hive is resolving it itself: updating head f1ebb39 onto main to measure what #499 left for it to add. If nothing meaningful remains it will close; otherwise its claim becomes Refs and it continues in the lane.

This comment is edited in place by the supersession sweep; it is not duplicated.

[kubestellar-prow]

New changes are detected. LGTM label has been removed.

[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 ask for approval from clubanderson. 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

[hivecommons-hive]

Evidence bundle `#497bc497bb` sha256:cffd26bfdca0355b9f1bee361c126d8723987cb6a0bfd35811047f4cc7ae3f9a — download from the dashboard or `hivectl review evidence #497`.