Skip to content

🌱 chore: restore v5 ancestry on v6 after the squash-merged top-up - #18956

Merged
hivecommons-hive[bot] merged 183 commits into
v6from
sync/v5-ancestry-2026-11-18
Nov 18, 2026
Merged

hivecommons-hive[bot] merged 183 commits into
v6from
sync/v5-ancestry-2026-11-18

Conversation

@clubanderson

Copy link
Copy Markdown
Member

#18929 carried v5 through c57fc02 (#18909) into v6 but was squash-merged by Tide (no tide/merge-method-merge label), so v5 is again not an ancestor of v6 and the automated v6-topup.yml would hit the same wall of conflicts on the next v5 push (see #18931).

This PR is an ours-merge of c57fc02: it records the ancestry and changes no file (git diff origin/v6 HEAD is empty). It carries one DCO remediation commit for the author's own v5 commits (the DCO app lists them again because the merge brings their history into the PR range).

It must be merged with a merge commit (tide/merge-method-merge), never squashed or rebased, or the ancestry is lost again.

Refs #18931.

🤖 Generated with Claude Code

clubanderson and others added 30 commits November 17, 2026 03:33
…'s reason (#18600)

* 🐛 meetings: log every failed meetings call and keep a failed approval's reason

A Quorum refusal of a Discord join (blocked: no permission to connect)
was answered as 502 with no log line, and the hosted ingress replaced the
body with its generic page, so the owner saw 'hive unavailable' and the
spoke log said nothing. Every meetings call failure is now logged with
method, path, status and error (Warn for 5xx, Info for caller mistakes),
and ApproveRequest records the failure reason on the still-open request.

Refs #18598

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 🐛 meetings: a blocked Discord join names the bot's permissions, and a failed approval shows on the request

The panel read every blocked meeting as 'The meeting refused a guest bot',
which is a Meet/Teams lobby refusal; on Discord blocked means the bot's
role lacks View Channel, Connect or Speak on the voice channel. The join
request row now also renders the reason a failed approval saved.

Refs #18598

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 📖 api-reference: re-point meetings route citations after the import shift

Refs #18598

Signed-off-by: Andy Anderson <andy@clubanderson.com>

---------

Signed-off-by: Andy Anderson <andy@clubanderson.com>
…p bot (#18610)

* ✨ remote items: follow up on items the hive opened as its App bot

With project.remote_write_identity a write-tier reference repo can write as
the App bot, but the own-item poller listed creator=<owner> under the
owner token only, so feedback on bot-opened issues and PRs never reached
the agent.

- remoteitems: RunTargets takes (repo, login) pairs; each repo is listed and
  its feedback filtered under its own login. Run keeps its signature as a
  one-login wrapper.
- github.RemoteItemsFetcher: optional TokenFor picks the read token per
  repo and is authoritative when set (no fallback to the owner token).
- cmd/hive: every write-tier repo is watched under its CredentialLogin and
  read with the token the proxy injects on its writes (scoped bot token,
  owner token or write_token_file).

Refs #18516

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 🐛 remote items: fix the per-repo login test's use of Store.Items

Store.Items returns a slice; build the tracked set from Item.Key.

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 📖 two-lane doc: the own-item follow-up covers bot-opened items too

Signed-off-by: Andy Anderson <andy@clubanderson.com>

---------

Signed-off-by: Andy Anderson <andy@clubanderson.com>
…assifier outage (#18618)

A fail-closed kick block was always logged as "ioscan fail-closed blocked
kick", which the fleet report classes as ioscan_classifier_unavailable. But
the kick is also withheld when untrusted issue/PR text trips the injection
policy (a Critical finding or a classifier block verdict) while the
classifier is answering: the defense working as designed, not an outage.
The #18459 report carried no classifier_error, i.e. exactly that case.

warnBlockedKick now keeps the fleet-reported wording (with classifier_error
and fix) only when the classifier is failing, and otherwise logs "ioscan
fail-closed withheld kick on an injection finding", listed in
fleetreport.IsBenignMessage. The held-PR coordination path goes through the
same helper, so it now also names the classifier error on an outage.

Closes #18459

Hive-Run: #18459
Hive-Plan: selfreport-ioscan_classifier_unavailable
Hive-Spec: fleet-report#ioscan_classifier_unavailable
Signed-off-by: Karibhou <157208370+Karibhou@users.noreply.github.com>
…8609)

`fetch-depth: 0` makes actions/checkout fetch every branch and tag. That
took 17-35s normally and on #18482 (run 43960382195) hung for the whole
5-minute job budget, failing the required "Sign-off survives the squash"
context before the check ran.

Check out the head shallowly, then fetch the head, base and default-branch
histories in full (unshallow), with a 60s per-attempt stall timeout and
three attempts. Picks up the fix a contributor reverted out of #18482 as
unrelated to that PR, plus the stall retry and post-fetch assertions.

Signed-off-by: Andy Anderson <andy@clubanderson.com>
…spatch once) (#18571)

* ✨ Hand workflow-model states to their agent profiles

The eval cycle now reads the bound model: an item whose state the model
hands to a profile (TechDocs Accepted -> techdocs-drafter, Drafting on
/verify -> techdocs-verifier) is withheld from every generic lane, claimed
for the agent that fills the profile on the issue-claims ledger, and kicked
once. The hand-off key (item, profile, state, triggering comment) is
written to workflow-dispatch.json on delivery, so neither a later cycle
nor a restart repeats it; a failed or deferred kick is retried.

Part of the drafter hand-off for cncf/techdocs#395.

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 🐛 List a bound repository's drafts at most every five minutes

Signed-off-by: Andy Anderson <andy@clubanderson.com>

---------

Signed-off-by: Andy Anderson <andy@clubanderson.com>
… reloads (#18592)

* 🐛 Betty closes the loop on deep dives; research agents survive reconciles

research-1..N are added to the runtime only (not hive.yaml), and
ReconcileAgents (config reload, reviewer autoscale) removes every agent
not in the enabled config set, so the pool was emptied shortly after boot
and each meeting research request failed with "no research agent
available" while nothing was said in the meeting.

- cmd/hive: the reconcile set carries the research pool's agents.
- research.Pool: a dispatch that finds no agent re-registers them once;
  ErrNoAgents carries a sayable Reason; Status() for the settings page.
- live: a persona deep dive that cannot start, errors, or runs past
  5 minutes is answered with "I couldn't look that up: <reason>." in
  the channel it was asked in; one progress note after 30 s; a spoken
  question's follow-up is spoken.
- Settings, Meeting attendee: Research section with agents, availability
  and a "No research agent available" warning.

Part of #18590

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 🐛 tests: set agents through AgentRuntimeConfig

Part of #18590

Signed-off-by: Andy Anderson <andy@clubanderson.com>

---------

Signed-off-by: Andy Anderson <andy@clubanderson.com>
…atus-card sections (quiet mode) (#18616)

* ✨ Review follow-ups, trust-only 090 and issue pr-link notes become status-card sections (quiet mode)

In github.notifications.mode: quiet the review Follow-ups checklist is the
collapsible review-followups section of the PR's hive:status card (ticks
kept via the new prstatus.WriteFunc), a 090 ready-for-human-merge entry
whose only objection is the author's trust tier is the stage-ready line,
and the issue-side PR-link stage note is the issue card's issue-pr-link
section. Every 085 and a held or manual-merge 090 still post a comment.

Fixes #18606

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 🐛 status-card follow-ups use their own marker; tests expect neutralised mentions

The card section carried the legacy Follow-ups comment marker, so the next
pass read the card as the legacy comment and EditIssueMarkerComment
rewrote the whole card. Stamp the section with
<!-- hive:review-followups-card --> and skip status comments in the legacy
check. The 090 card line goes through prstatus.Write, which neutralises
'@sha' to a code span; the test now expects that.

Signed-off-by: Andy Anderson <andy@clubanderson.com>

---------

Signed-off-by: Andy Anderson <andy@clubanderson.com>
…r maintainer reporters (#18617)

* 🌱 ci: no mutation comment for an error verdict; no reopen hint for bot or maintainer reporters

mutation-report.sh post no longer creates a <!-- hive-mutation --> comment
for an 'error' verdict (no report, nothing to act on): the report stays in
the job summary and the failing verdict step, and an earlier finding comment
is edited so it is not stale. issue-closed-reopen-hint.yml skips issues
whose reporter is a bot or OWNER/MEMBER/COLLABORATOR. pr-overlap.sh already
posts only when a sibling PR overlaps (#17870); unchanged.

Fixes #18607

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 🌱 changelog fragment for #18607

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 🌱 re-pin TRUSTED_SCRIPTS_TREE for the mutation-report.sh change

Signed-off-by: Andy Anderson <andy@clubanderson.com>

---------

Signed-off-by: Andy Anderson <andy@clubanderson.com>
…18621)

Until the consent notice is delivered (consent_posted_at), every
transcript segment, draft and chat line is discarded in the manager:
not stored and not emitted to listeners (Betty, Spektacular, research,
facts, Inbox hand-off). Only a pre_consent_dropped count is kept. A
leave phrase is still honoured and the line itself is not kept.

Lines that arrive after the notice but belong before it are dropped
too: seq at or below Quorum's transcript cursor when the notice landed
(consent_seq), chat stamped earlier, and for two minutes segments that
began before the last speech heard while pending (consent_speech_end).
A reconnect or restart while pending asks Quorum for no replay, and
dropped lines advance the replay cursor.

Refs #18590

Signed-off-by: Andy Anderson <andy@clubanderson.com>
…#18624)

The has-open-pr label write shared the caller's 15s deadline with the
open-PR listing ahead of it, so a slow listing of a large repo left it a
spent context. The write failed with context deadline exceeded, the issue
never got the label, and every later claim pass retried it and warned
again, which filed an unclassified_error_repeated self-report.

- give the label write its own 10s budget, detached from the caller
- remember a failed write per issue: 15m after a transient failure, 6h
  after a refusal (403/404/410/422), and log refusals at INFO
- add the open_pr_guard_label_failed fleet-report class for the
  remaining repeated WARNs

Fixes #18589

Signed-off-by: Andy Anderson <andy@clubanderson.com>
#18609's unshallow step fetched full blob history and measured 38-42s on
the self-hosted pool, slower than the all-refs checkout it replaced. The
checker reads only commits and trees, so fetch with --filter=blob:none
(measured 84s -> 14s and 277 MB -> 24 MB locally for the same refs).

Signed-off-by: Andy Anderson <andy@clubanderson.com>
The test returned once the instruction was typed, while the queue worker
and seed delivery were still writing (touch, audit, inbox routing). TempDir
cleanup then raced those writes (directory not empty). Wait for the audit
and for the queue worker to exit before the test ends.

Fixes #18545

Signed-off-by: Andy Anderson <andy@clubanderson.com>
Automated release commit. Compiles changelog.d/ fragments and moves
the CHANGELOG.md Unreleased section into a dated v5.293.0 entry.
See src/docs/releases.md.

Signed-off-by: hive-release-bot <actions@github.com>
)

* ✨ Owner-only Send to <profile> on model-owned stage-tracker rows

A row of a model-bound repository whose state the model hands to an agent
profile offers the owner Send to <profile> in its menu, backed by the
owner-only POST /api/workflows/dispatch: the item is read fresh, the
agent resolved (a profile disabled for automatic dispatch still
resolves), the issue claimed first and the agent kicked; the hand-off is
recorded once the kick lands so the automatic pass does not repeat it.
Audited workflow_dispatch; openapi and api-reference updated.

Part of the drafter hand-off for cncf/techdocs#395.

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 🐛 Register the kicked agent in the dispatch endpoint test runtime

Signed-off-by: Andy Anderson <andy@clubanderson.com>

---------

Signed-off-by: Andy Anderson <andy@clubanderson.com>
…18602)

Record the #18596 comparison as a design page: phone dial-in, a desktop
companion that streams the user's own call audio, and Zoom's RTMP live
stream, each against the free-account, bot-rule, consent and cost
constraints. Recommends the desktop companion (macOS first) and records
its proposed streaming contract, per-user companion token, distribution
plan and prototype PR set. Indexed in docs/design/README.md and linked
from meetings.md, which now notes that Zoom refuses web-client bots.

Hive-Run: #18596
Hive-Plan: 18596 recommendation and prototype PR set
Hive-Spec: #18596#recommendation

Signed-off-by: Karibhou <157208370+Karibhou@users.noreply.github.com>
Co-authored-by: clubanderson <407614+clubanderson@users.noreply.github.com>
…rted clusters included (#18639)

The host_aliases reconcile sweep (#17805) patches Deployments over kubectl,
but vllm-d and a-ks-wec2 are push-reported (pull_only) clusters the hub
cannot reach, so the sweep skipped every hive there silently. Only spokes
rendered from the template after #17805 carried the aliases.

The hub now sends the SaaS record cluster's host_aliases on every heartbeat
response and the spoke converges its own Deployment with a JSON patch
(exact for the managed hostnames, unrelated aliases kept, throttled to one
check per 15 minutes). The hub sweep reports push-reported clusters and
WARNs on unreadable or unreachable Deployments instead of logging at Debug.

Fixes #18637

Signed-off-by: Andy Anderson <andy@clubanderson.com>
* ✨ meetings: desktop companion meetings (/api/companion/*)

A companion meeting is fed by the desktop companion: a person's own meeting
client audio (call) and microphone (mic), captured on their computer after a
versioned consent confirmation, relayed as 16 kHz PCM to Quorum's companion
platform (quorum 0.3.0). Betty's replies go to the companion window through
Quorum's outbox. Owner or read-write; a companion meeting is usable only by
its starter (or an owner).

Refs #18596

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 📖 docs: rewrite api-reference citations shifted by the companion routes

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 🐛 meetings: companion handlers use the logging meetingsError (#18600)

Signed-off-by: Andy Anderson <andy@clubanderson.com>

---------

Signed-off-by: Andy Anderson <andy@clubanderson.com>
Co-authored-by: scanner <280983584+hivecommons-hive[bot]@users.noreply.github.com>
quorum.mjs sha256 from the v0.3.0 release's quorum.mjs.sha256; davey stays
0.1.12 (quorum's package-lock.json).

Refs #18596

Signed-off-by: Andy Anderson <andy@clubanderson.com>
…e queue, delete finished meetings, quiet Spektacular restarts (#18635)

* 🐛 Meetings: don't restart-loop the Spektacular stream child when live mode isn't available

The pinned spektacular (0.31.0) has no `meeting` command
(hivecommons/spektacular#126 is unreleased), so every live meeting child
printed cobra's unknown-command envelope and exited 1. The stream
restarted it five times per meeting, each restart a WARN, which the
slog feed self-reported as unclassified_error_repeated (#18630), and the
session warned once per transcript line it could not forward.

- spektacular.Stream gains an optional Probe (`meeting --help`), run
  once per installed binary; an unknown command marks the stream
  Unsupported: no child is started or restarted, one INFO line per
  binary. A child whose own exit output says unknown command is not
  restarted either.
- Restart lines are WARN at most once per BackoffMax window (INFO
  otherwise) and map to a new log-fed class spek_stream_unavailable.
- The live session treats an unsupported Spek as off from the start
  (panel status unchanged), stops forwarding once Spek is gone, and warns
  about a failed forward only on the transition to paused.

Fixes #18630

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* ✨ Meetings: delete finished meetings and stale join requests

Owner-only DELETE /api/meetings/{id} for meetings in a final state and
pending join requests (declined, then removed); 409 while hive is still
in the meeting. Removes the record, transcript and live state, erases
the meeting in Vexa with Quorum meeting.delete (best effort, surfaced as
upstream_error) and drops the Calendar entry that existed only for it.
POST /api/meetings/clear-finished deletes all finished meetings older
than now; DELETE /api/meetings/schedule/{eid} deletes a past Calendar
entry with its meetings. Knowledge facts and drafts are not touched.
Audited as meeting_delete / meeting_schedule_delete.

UI: 🗑 Delete on finished and join-request rows, Clear finished, and
🗑 Delete on past Calendar entries, all behind the in-page confirm.

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 🐛 Meetings delete: use s.meetingsError after the v5 merge (#18600)

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 🐛 Meetings delete: clear consent tries and load the delete helpers in the role-race test

Carries the fixes from #18615's v5 merge: Delete also forgets the
consent attempt count, and the meetings/calendar role-race harness
extracts meetingsFinished, meetingsCanDelete, meetingsDeleteButtonHtml,
calendarCanDelete and their constants.

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* ✨ Betty runs several model calls per meeting at once

A meeting may now have up to meetings.llm.per_meeting_in_flight (default
3, never above max_in_flight) model calls in flight, so a second request
no longer waits for the first answer. A per-meeting Gate bounds the calls
and reserves each in-flight call's expected cost against the token
budget, so concurrent calls cannot all pass the check on the same ledger
total. On a warm CLI backend the meeting keeps a pool of warm CLIs (one
turn per process, since stream results carry no request id) that grows
only when calls overlap.

Part of #18590.

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 🌱 Show meetings.llm.per_meeting_in_flight in the meetings settings

The Settings parity guard needs every hive.yaml leaf referenced by the
Settings UI; the meetings settings' effective values now include it.

Part of #18590.

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* ✨ Betty names who and what each answer is for when requests overlap

With more than one request in flight, other lines said since the
request, or an answer later than 8 s, each answer opens with the asker's
display name (first name when spoken, never an @mention) and a short
topic phrase: the model's new "topic" label, else the request's own
words. Two or more requests in hand post one queue note per minute
(chat, rate limited, not charged), and spoken acks name their asker
when others are waiting.

Part of #18590.

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* ✨ Betty speaks ready answers shortest first and moves a long voice queue to chat

Quorum's say queues clips and plays them in order, so hive keeps an
estimate of the queued speech. Spoken answers ready in the same loop turn
are said back to back, shortest first; one that would wait behind more
than 20 s goes to chat with one spoken "I've put the rest in chat"; an
ack behind more than 8 s of speech is skipped. Answers to addressed
requests may take meetings.chat_answer_burst (3) extra chat posts a
minute past the chat rate.

Part of #18590.

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 🌱 Show meetings.chat_answer_burst in the meetings settings

Part of #18590.

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* ✨ Betty times every answer stage and answers live-state questions without waiting for search

Each answer carries heard, retrieval, model and answer-ready timings with
its source and budget (4 s for the hive's live state, 8 s otherwise); the
live session adds delivery and say times and keeps the last 20 with a
latency summary in the live state served by the meeting detail API.
Gather stops waiting once the hive status retriever answers.

Part of #18590.

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* ✨ Betty cites the sources of chat answers and says when she is not sure

Chat answers end with up to two sources the model reported using (web
link, work item id, knowledge fact, code map or hive live status); the
prompt asks for issue and PR numbers and forbids guessing; a
low-confidence addressed answer not from the live state is hedged.

Part of #18590.

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 📖 Refresh meetings API doc citations for the combined Betty changes

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 🐛 Betty attribution tests expect the source a chat answer now cites

With #18631's citations combined, an attributed chat answer ends with its
source, so the attribution tests compare against that full text.

Signed-off-by: Andy Anderson <andy@clubanderson.com>

---------

Signed-off-by: Andy Anderson <andy@clubanderson.com>
…#18638)

* ✨ Sessions: per-session git worktrees with a locked shared git config

Each Sessions pane opens in its own git worktree of the hive's one shared
clone, on branch hive-session/<id>, so each session has its own Spektacular
workflow state, checked-out branch and uncommitted work (#18588).

The shared clone's git config and hooks are locked: root rewrites
.git/config from scratch (no git as root) as root:<gid> 0644 with
extensions.worktreeConfig, empties hooks/, info/ and modules/ into root
0755 dirs, places root-owned config.worktree and commondir placeholders,
keeps objects/refs/logs group-writable, and makes .git, worktrees/ and the
clone 3770. It runs before any worktree of a clone is handed out and once
per clone at boot. A session's worktree entry is created with no group
write; panes get no safe.directory, so git refuses a swapped .git. The
hive's own git always passes -c core.hooksPath=/dev/null
-c core.fsmonitor=false.

Existence checks run in the add/remove scripts as the session uid (the hive
runs as dev, outside the sessions group): a resume is a no-op, a missing
clone is reported, a worktree whose .git is not the session's own is
refused. Removal auto-saves uncommitted work on the session branch first.
The worktree sweep does not run while the sessions store failed to load or
an unreadable copy is set aside.

Builds on the design in #18613 by Karibhou.

Fixes #18588

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 🌱 Sessions: split worktree code into its own file, re-pin API citations

Moves the worktree scripts and functions out of usersession_workspace.go
(over the 800-line crux limit) into usersession_worktree.go, updates the
add-count test (the add script runs on every start, as the session uid),
and re-pins the sessions API citations with check-docs-citations.py --fix.

Signed-off-by: Andy Anderson <andy@clubanderson.com>

Co-authored-by: Danathar <6772335+Danathar@users.noreply.github.com>
* 🐛 fix: wait for seed queue before test cleanup

Wait for the seed queue worker to finish its session store writes before temporary directory cleanup.

Hive-Run: #18454
Hive-Plan: dashboard-seed-cleanup
Hive-Spec: issue-18454#dashboard-test-cleanup
Signed-off-by: Karibhou <157208370+Karibhou@users.noreply.github.com>

* fix: wait for all seed test queue workers

Signed-off-by: Karibhou <157208370+Karibhou@users.noreply.github.com>

* test: share pending seed cleanup

Signed-off-by: Karibhou <157208370+Karibhou@users.noreply.github.com>
…8643)

Each owner or read-write user mints a companion token on /companion/token
(shown once, SHA-256 stored, one per user). authenticate admits it only on
/api/companion/info and /api/companion/meetings/*, as the minting user at
their live role (refused below read-write). The hub waves those routes
through to the spoke, which does the check; the token page stays gated.

Refs #18596

Signed-off-by: Andy Anderson <andy@clubanderson.com>
Automated release commit. Compiles changelog.d/ fragments and moves
the CHANGELOG.md Unreleased section into a dated v5.294.0 entry.
See src/docs/releases.md.

Signed-off-by: hive-release-bot <actions@github.com>
Automated pin bump (#8419). Digests recomputed from the downloaded
release artifacts by src/scripts/cli-pin-bump.sh:

  VERSION=18.22.0
  SHA256_AMD64=f706b27ba845834d8f8360705a2e9ba1534f3593fa24411d41358272de33642b
  SHA256_ARM64=7238dd213d5c61bc9bf51735d552bc71901fdd44329f862b0a971146b1cdac3e

Signed-off-by: hive-release[bot] <hive-release@hive.kubestellar.io>
Signed-off-by: clubanderson <407614+clubanderson@users.noreply.github.com>
Automated pin bump (#8419). Digests recomputed from the downloaded
release artifacts by src/scripts/cli-pin-bump.sh:

  VERSION=2.1.326

Signed-off-by: hive-release[bot] <hive-release@hive.kubestellar.io>
Signed-off-by: clubanderson <407614+clubanderson@users.noreply.github.com>
…th (#18604)

The guard was cancelled at its 10-minute timeout whenever the
whisper-linux-amd64 gha cache missed. The repo's Actions cache runs at
12-23 GB against a 10 GB cap, so LRU eviction regularly drops the
whisper-builder blobs; the hosted 4-vCPU runner then compiles FFmpeg and
whisper.cpp from source (~8.5 min serial chain) and the job needs ~13 min.
Warm runs measure 6.5-8 min and are unaffected.

Raise the timeout to 20 min (cold path plus ~50% headroom) and skip the
buildx post-step teardown on the ephemeral runner (16-36s per run).
Regenerated the integration workflows from v2-ci.yml.

Signed-off-by: Andy Anderson <andy@clubanderson.com>
Avoid collisions with delayed tmux operations from shuffled tests and drain the readiness helper before session teardown.

Hive-Run: #18626
Hive-Plan: restart-kick-flake
Hive-Spec: restart-kick#readiness
Signed-off-by: Karibhou <Karibhou@users.noreply.github.com>
Automated release commit. Compiles changelog.d/ fragments and moves
the CHANGELOG.md Unreleased section into a dated v5.295.0 entry.
See src/docs/releases.md.

Signed-off-by: hive-release-bot <actions@github.com>
clubanderson and others added 17 commits November 18, 2026 04:40
Rollout step 1, part A of the hub registration protocol
(#18642), ported from the tuna-os#189 prototype:

- GET /api/hub/v1 discovery: protocol version, operations, limits
  (max_repos, max_per_user, expiry, key_rotation_overlap) and the proof
  method the hub actually offers, hub-session-token. Readable without
  signing in.
- HIVE_HUB_SELFSERVICE_MAX_REPOS makes the per-registration repo cap
  configurable (default 20, clamped to 500). The legacy create keeps its
  400 body; the request body limit scales with the cap.

Everything is behind HIVE_HUB_SELFSERVICE_REGISTRATION. No GitHub writes;
heartbeat_signing.go and the credential fence are untouched.

Signed-off-by: James Reilly <jreilly1821@gmail.com>
Signed-off-by: Andrew Anderson <andy@clubanderson.com>
Co-authored-by: James Reilly <5840441+hanthor@users.noreply.github.com>
* Customers list: GitHub avatars, tag pills and one-line rows (#18885)

Avatars come from github.com for a confirmed GitHub login only, lazy, no
referrer, fixed size, initial as fallback; never keyed by email. Tags,
identities and origin are pills; rows are one line. customers.avatars.enabled
(env HIVE_CUSTOMERS_AVATARS_ENABLED, Settings Features) switches avatars off.

Fixes #18885

Signed-off-by: Andrew Anderson <andy@clubanderson.com>

* docs: keep security-model readable (no URL inside inline code)

Signed-off-by: Andrew Anderson <andy@clubanderson.com>

* config: add customers.avatars to the golden parse

Signed-off-by: Andrew Anderson <andy@clubanderson.com>

* Customers: style the me badge as a pill (#18885)

Signed-off-by: Andrew Anderson <andy@clubanderson.com>

---------

Signed-off-by: Andrew Anderson <andy@clubanderson.com>
…ob (#18891)

* ✨ feature: sandbox node preflight and fail-fast on an unschedulable Job

Add sandbox.preflight: configurable commands run in the Job's main container
before the agent. A failure ends the kick in seconds as node_unhealthy with
the node recorded, retries once with a hostname NotIn affinity, and is not an
agent failure.

Add job.schedule_timeout_s (default 10m): a pod Unschedulable that long fails
the kick as waiting_for_node with the scheduler's message, deletes the Job and
releases the agent. The dashboard shows both states.

Fixes #18811

Signed-off-by: Andrew Anderson <andy@clubanderson.com>

* 🌱 test: poll sandbox preflight kicks on a ticker, not time.Sleep

The sleep ratchet counts time.Sleep calls in tests.

Signed-off-by: Andrew Anderson <andy@clubanderson.com>

---------

Signed-off-by: Andrew Anderson <andy@clubanderson.com>
…18896)

* ✨ hub: v1 registration resources, per-repo proofs and revision

Rollout step 1, part B of the hub registration protocol
(#18642), ported from the tuna-os#189 prototype:

- Per-repo proof times (SelfServiceHive.RepoProofs) and a Revision
  counter. Both are additive JSON fields, so older binaries ignore them;
  a record without a revision loads as 0. Heartbeats do not bump the
  revision, so a live spoke never invalidates an operator's ETag.
- Store update() that restores the key hashes, owner, ID, CreatedAt and
  the heartbeat stamp after any mutation, plus rotate and revoke guarded
  by an ETag precondition.
- selfServiceRegisterCore and selfServiceProveOwnership split out of the
  legacy register handler. Tests pin the legacy /api/hub/selfservice/*
  responses byte for byte.
- v1 POST/GET/list/DELETE and POST .../keys: an ETag on every record,
  optional If-Match on delete and rotate, 413 with limit: max_repos over
  the repo cap, 201 on rotate, and a 400 for a caller-chosen grace window.

Behind HIVE_HUB_SELFSERVICE_REGISTRATION. No GitHub writes;
heartbeat_signing.go and the credential fence are untouched.

Co-authored-by: James Reilly <5840441+hanthor@users.noreply.github.com>
Signed-off-by: James Reilly <jreilly1821@gmail.com>
Signed-off-by: Andrew Anderson <andy@clubanderson.com>

* 🐛 hub: fix v1 registry test fixture and drop an unused helper

Co-authored-by: James Reilly <5840441+hanthor@users.noreply.github.com>
Signed-off-by: Andrew Anderson <andy@clubanderson.com>

---------

Signed-off-by: James Reilly <jreilly1821@gmail.com>
Signed-off-by: Andrew Anderson <andy@clubanderson.com>
Co-authored-by: James Reilly <5840441+hanthor@users.noreply.github.com>
…Refs #18740) (#18881)

A refresh-less session copy would log the CLIs out, so the adopt-back stays the safety net. Pins that adoption never writes the session copy, documents the reasoning and the manual live-install checklist.

Signed-off-by: Andrew Anderson <andy@clubanderson.com>
…pt (#18903)

* ✨ Customers step E: budgeted GitHub mention search on suggestion accept

Fixes #18884

Signed-off-by: Andrew Anderson <andy@clubanderson.com>

* 🐛 Customers step E: reuse existing RateLimitCautionEngaged and searchQueryMaxLen

Signed-off-by: Andrew Anderson <andy@clubanderson.com>

---------

Signed-off-by: Andrew Anderson <andy@clubanderson.com>
#18902)

* 🐛 Key the workflow-dispatch ledger by the qualified repo on every path

Fixes #18901

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 🐛 Reuse the existing qualifiedRepo helper

Fixes #18901

Signed-off-by: Andy Anderson <andy@clubanderson.com>

---------

Signed-off-by: Andy Anderson <andy@clubanderson.com>
… budget (Fixes #18910) (#18911)

Signed-off-by: Andy Anderson <andy@clubanderson.com>
Automated release commit. Compiles changelog.d/ fragments and moves
the CHANGELOG.md Unreleased section into a dated v5.318.0 entry.
See src/docs/releases.md.

Signed-off-by: hive-release-bot <actions@github.com>
…#18868)

* ✨ sandbox Jobs: authenticated GitHub reads through a read-only hive relay (#18865)

Adds an opt-in relay (agent_sandbox.job.github_read_proxy, default off) that sandbox Jobs reach through HTTPS_PROXY. It attaches a read-only, repo-scoped App token (shared-uid-read tier) to GET/HEAD for api.github.com, codeload.github.com, raw.githubusercontent.com and git fetch on github.com; refuses writes, GraphQL and push discovery; tunnels other hosts untouched. The Job holds only a per-kick relay key, never a GitHub credential.

Signed-off-by: Andrew Anderson <andy@clubanderson.com>

* 🐛 sandbox read relay: fix compile, file-size ratchets, harden tunnel host check (#18865)

- Add SetSandboxGitHubReadRelay to crux.Host and implement it on every
  Host: Manager, the sidecar host (in-process-only), the cruxtest recorder,
  and the api HostSetters table. boot calls it through the interface.
- Move SandboxGitHubReadRelay into the crux package (agent aliases it) and
  keep the Manager's relay wiring in one atomic value so the relay and its
  NO_PROXY hosts can never be read from different installs.
- Keep agent/manager.go and config/agent_config.go under their ratchets by
  moving code out (ACMM level accessors, sandbox job types and the relay
  config) instead of raising any limit.
- Refuse a request inside a tunnel whose Host or absolute URL names a host
  other than the CONNECT target, so the credential decision cannot be
  borrowed for another host.
- Fix the boot test's Config literal (AgentSandbox is promoted).
- Tests: relay logs never contain the token, relay key or agent header;
  keys are per kick; Host mismatch is refused without an upstream dial;
  manager install/clear copies noProxy.

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 🐛 crux/api: move HostSetter type out of runtime.go to stay under its ratchet (#18865)

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 🐛 sandbox read relay boot: Serve always returns an error (staticcheck SA4023) (#18865)

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 🐛 sandbox read relay: remember a failed token mint for 30s instead of retrying per request (#18865)

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 🐛 sandbox read relay test: reuse the package's lockedBuffer after the v5 merge (#18865)

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 🔒 sandbox read relay: TLS-only listener, no default bind, https endpoint, NetworkPolicy docs (#18865)

Owner decision on the needs-decision review item:
- listen_addr has no default; enabling without it fails config validation
  with an error naming the key (default off is unchanged).
- The listener serves TLS only, with a certificate issued by the existing
  hive proxy CA for the endpoint host (DNS or IP SAN); endpoint must be
  https:// and http:// is rejected at validation. No new CA or key on disk.
- Jobs verify the https proxy against the hive CA bundle, including
  libcurl's separate proxy CA setting for git (http.proxySSLCAInfo).
- Tests: plain HTTP is refused and its key never logged, no key still gets
  407 over TLS, certificate SANs, config validation, env.
- Docs: example NetworkPolicy, two-layer statement, client TLS-to-proxy
  limits, example config, changelog fragment.

Follow-up for the tunnel that outlives its key: #18895.

Signed-off-by: Andy Anderson <andy@clubanderson.com>

* 🐛 hive.yaml.example: resolve merge markers (#18865)

Signed-off-by: Andrew Anderson <andy@clubanderson.com>

---------

Signed-off-by: Andrew Anderson <andy@clubanderson.com>
Signed-off-by: Andy Anderson <andy@clubanderson.com>
…read-only route and Advisor card (#18904)

* ✨ Expose the knowledge advisor rank-versus-holdout summary (read-only route + Advisor card)

Adds GET /api/knowledge/advisor/summary and a Knowledge-section Advisor card:
decision counts by mode/arm/outcome, Lane.AdvisorArmSummary() per-arm bead
means (mixed/none separate), mean latency and tokens, advisor settings and a
small-n caveat. Counts and means only. Decision records now carry latency and
token counts.

Signed-off-by: Andrew Anderson <andy@clubanderson.com>

* ✨ OpenAPI entry for GET /api/knowledge/advisor/summary

Signed-off-by: Andrew Anderson <andy@clubanderson.com>

* ✨ Advisor card: avoid a settings-leaf literal the parity test treats as a Settings UI reference

Signed-off-by: Andrew Anderson <andy@clubanderson.com>

---------

Signed-off-by: Andrew Anderson <andy@clubanderson.com>
… a 422 forever (#18909)

Fixes #18907

Signed-off-by: Andrew Anderson <andy@clubanderson.com>
#18929 carried v5 through c57fc02 into v6 but was squash-merged, so v5 is
again not an ancestor of v6. This ours-merge records that ancestry; it
changes no file (the tree equals v6's).

Signed-off-by: Andrew Anderson <andy@clubanderson.com>
I, Andy Anderson <andy@clubanderson.com>, hereby add my Signed-off-by to this commit: 3d8d438
I, Andy Anderson <andy@clubanderson.com>, hereby add my Signed-off-by to this commit: f444b4f

Signed-off-by: Andy Anderson <andy@clubanderson.com>
I, Andy Anderson <andy@clubanderson.com>, hereby add my Signed-off-by to this commit: c57fc02
I, Andy Anderson <andy@clubanderson.com>, hereby add my Signed-off-by to this commit: 5fcb84e
I, Andy Anderson <andy@clubanderson.com>, hereby add my Signed-off-by to this commit: accb8f9
I, Andy Anderson <andy@clubanderson.com>, hereby add my Signed-off-by to this commit: e3823a7
I, Andy Anderson <andy@clubanderson.com>, hereby add my Signed-off-by to this commit: 7b534d0
I, Andy Anderson <andy@clubanderson.com>, hereby add my Signed-off-by to this commit: d5dfc48
I, Andy Anderson <andy@clubanderson.com>, hereby add my Signed-off-by to this commit: 04d4d03
I, Andy Anderson <andy@clubanderson.com>, hereby add my Signed-off-by to this commit: 095dde4
I, Andy Anderson <andy@clubanderson.com>, hereby add my Signed-off-by to this commit: 41029a4
I, Andy Anderson <andy@clubanderson.com>, hereby add my Signed-off-by to this commit: b7028dc
I, Andy Anderson <andy@clubanderson.com>, hereby add my Signed-off-by to this commit: 9d2b999
I, Andy Anderson <andy@clubanderson.com>, hereby add my Signed-off-by to this commit: ed1d6eb
I, Andy Anderson <andy@clubanderson.com>, hereby add my Signed-off-by to this commit: 8ce72d8
I, Andy Anderson <andy@clubanderson.com>, hereby add my Signed-off-by to this commit: 3d8d438
I, Andy Anderson <andy@clubanderson.com>, hereby add my Signed-off-by to this commit: f444b4f

Signed-off-by: Andy Anderson <andy@clubanderson.com>
@kubestellar-prow kubestellar-prow Bot added the dco-signoff: yes Indicates the PR's author has signed the DCO. label Nov 18, 2026
@clubanderson clubanderson added the tide/merge-method-merge Denotes a PR that should use a standard merge by tide when it merges. label Nov 18, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Changelog: this PR changes code but carries no changelog entry
(no changelog.d/ fragment and no CHANGELOG.md edit).

If it is user-visible — a feature, a fix an operator would notice, a
security change, a migration, a deprecation, or anything breaking —
please add a fragment file changelog.d/<category>-<pr-or-slug>.md
containing exactly your entry (see changelog.d/README.md; the
category is one of added/changed/deprecated/fixed/security). Please
do not append to CHANGELOG.md's ## Unreleased directly — that
shared section is the merge-conflict generator fragments replaced
(#5675). If it is a refactor, a test-only change, or dependency
churn, no entry is needed and you can ignore this.

This is a reminder, not a gate; it never blocks a merge.

@kubestellar-prow kubestellar-prow Bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Nov 18, 2026
@clubanderson clubanderson changed the title 🌱 chore: restore v5 ancestry on v6 after the squash-merged top-up #18929 🌱 chore: restore v5 ancestry on v6 after the squash-merged top-up Nov 18, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@clubanderson this PR is back in your court (stage/071-needs-author). Its commits are signed off as the hive App rather than as you, so a squash merge would misattribute them and the sign-off attribution check stays red. No hive agent can rewrite a contributor's commits — the fix is yours:

  • 15 commits are signed off as the hive App instead of you, so a squash merge would misattribute them — set git config user.email to your own address, then run git rebase --exec 'git commit --amend --no-edit --reset-author -s' HEAD~151 && git push --force-with-lease

Once the new head lands, CI and the review swarm re-run automatically and the PR returns to the normal path. Current head: 80b30c336773.

@clubanderson clubanderson added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Nov 18, 2026
@kubestellar-prow

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@hivecommons-hive
hivecommons-hive Bot merged commit 5ac5173 into v6 Nov 18, 2026
84 checks passed
@kubestellar-prow
kubestellar-prow Bot deleted the sync/v5-ancestry-2026-11-18 branch November 18, 2026 12:20
@hivecommons-hive

hivecommons-hive Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

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

Evidence bundle `#1895680b30c3` sha256:06ae4cff56ed48132ab7b6ebc5d4f38a03eb3db1604865681986b1b9c32939ee — download from the dashboard or `hivectl review evidence #18956`.

merged by Hive trusted-author auto-merge: author clubanderson holds role owner and GitHub permission admin on repo; CI green at 80b30c3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has signed the DCO. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. tide/merge-method-merge Denotes a PR that should use a standard merge by tide when it merges.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants