Skip to content

✨ feature(hub): bounded activity digest contract and per-user /api/hub/activity - #16001

Closed
Karibhou wants to merge 2 commits into
hivecommons:v5from
Karibhou:feat/hub-activity-monitor-rfc-15861
Closed

Karibhou wants to merge 2 commits into
hivecommons:v5from
Karibhou:feat/hub-activity-monitor-rfc-15861

Conversation

@Karibhou

Copy link
Copy Markdown
Contributor

First implementation slice of the hub-wide Activity Monitor: RFC #15861, proposed by @hanthor, child #15951.

Closes #15951
Refs #15861: partial. Still to do: the cached spoke publisher with coalesced ≤1/15 s updates (#15963), bounded events and merge toasts (#15964), the Fleet activity page and display shell (#15965), and the disabled-by-default hivecommonsfleet broadcast (#15966).

What changed

pkg/hubactivity (new): the shared wire contract for the heartbeat activity block. Both ends import it, so the caps and the ordering cannot drift between spoke and hub.

  • Build caps at 100 items by default under a hard 250-item ceiling.
  • Items are ordered by urgency: needs-human / needs-decision, then stalled, then furthest stage, then oldest.
  • Private-repo items are dropped unless the spoke opts in. They are always counted in totals, and the drop is not reported as truncation.
  • Each digest carries a weak content etag that does not change with generated_at.
  • Sanitize re-applies every bound on the hub, because spoke input is untrusted:
    • repo must be owner/name;
    • kind and author_kind come from closed sets;
    • stage and mods must be slugs;
    • duplicate repo#n rows are removed;
    • integers are clamped;
    • control, format and line-separator characters are stripped from titles (200 runes max).

Hub storage and acknowledgement

  • The block rides the existing per-hive heartbeat bearer, so there is no new credential.
  • It is stored in memory only: a leaf-locked activityStore, never in the persisted registry. A hive's block is forgotten after 24 h of silence.
  • The heartbeat response returns activity_etag. A spoke can then send an etag-only "unchanged" marker, and the marker is compared on the cleaned etag.

GET /api/hub/activity (signed-in users, read-only, no actions)

  • Authorization is checked per user and per hive before any block is read. Admins see every hive. Everyone else sees owned hives plus unexpired grants, the same rule as My Hives.
  • Merged items are tagged with hive_id.
  • Each hive gets a status: ok, stale (more than two missed heartbeats), not_reporting (spoke too old) or missing (granted but unknown).
  • Truncation is disclosed per hive and for the whole response (response cap 2000).
  • Filters hive/repo/stage/mod/author_kind/q are bounded; an invalid one returns 400.
  • ETag + If-None-Match returns 304. Headers are Cache-Control: private, no-cache and Vary: Cookie, Authorization.

Spoke: the payload and response structs carry the optional fields. Nothing populates the digest yet (that is #15963), so beats are byte-identical today.

Also included: a docs row in src/docs/api-reference/hub-server.md and changelog.d/added-15951-hub-activity-api.md.

Tests

The tests were written before the implementation. Per AGENTS.md, nothing was run locally (gofmt -l is clean), so CI gives the verdict.

  • hubactivity: default cap and truncation, ceiling clamp, urgency order, private drop with totals still counted, share_private, etag stability, no input mutation, hub ceiling, token validation and dedupe, separator stripping, the unchanged marker.
  • Hub end to end through handleHeartbeat:
    • Two spokes on one hub: a user granted one hive sees only that hive's rows and freshness; an admin sees both.
    • An anonymous request gets 401.
    • A user with no grant, or with an expired grant, gets nothing.
    • A private item never appears in the response but is counted.
    • ETag 304, then a new etag after a change.
    • Oversized filters get 400.
    • A beat without a block keeps the held digest and is still acknowledged.
  • Store and view: ack and marker semantics (including a dirty marker etag), the hub ceiling, the 24 h forget, stale / not-reporting / missing disclosure, filters and the response cap, the spoke→hub wire round-trip.

Review notes

The change was reviewed by a Go reviewer and a security reviewer. Neither found a CRITICAL or HIGH issue, and their findings were applied before the push. Known limits, deliberately left out of this slice:

  • Owner trust: for a brand-new self-hosted hive with no SaaS record, Owner is spoke-asserted. This is the same trust model My Hives uses today. The worst a spoke can do is show its own rows to another user; it cannot read anything.
  • Private flag: the Private opt-in is enforced in the spoke builder, as ✨ Bounded activity heartbeat contract and authorized hub aggregation API #15951 scopes it. A hub-side consent record would be a follow-up.
  • Rate limiting: the endpoint has no rate limit or per-user view cache. The hub has no generic limiter, and per-request cost is bounded by the 2000-item cap.
  • Docs citations: inserting the route and wiring in server.go may shift existing docs citations. If the guard reports drift, I'll run check-docs-citations.py --fix as AGENTS.md describes.

Deployment and activation status

Unchanged. No spoke populates the digest yet, and no rollout, participation (hub.activity.*) or broadcast setting was added or changed. The existing hivecommons stream is untouched. @hanthor will get a completion note when this PR actually merges.

🤖 Generated with Claude Code

https://claude.ai/code/session_01HRH6kkRUk7o2ootvBTQceV

— hive: backend=claude

@kubestellar-prow kubestellar-prow Bot added the dco-signoff: yes Indicates the PR's author has signed the DCO. label Oct 31, 2026
@kubestellar-prow

Copy link
Copy Markdown
Contributor

[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 hanthor 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:

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

@kubestellar-prow kubestellar-prow Bot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Oct 31, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Open PR overlap check

Base branch: v5

Conflicts are checked with every PR merged onto the current tip of v5, so a PR that only needs a rebase is not reported as conflicting with its siblings.

No conflicting open PRs or same-file overlaps were found.

@hivecommons-hive

Copy link
Copy Markdown
Contributor

@Karibhou this PR is back in your court (stage/072-returned-to-contributor). The hive will not merge it until the head changes.

Failing checks:

  • relative links and anchors resolve

Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path.

Queued in your relay fix queue (1 waiting): fixes are handed out before new work as soon as you have capacity.

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Intent alignment (#15951) — read at head e7da30d. The diff delivers every bullet of the child issue (default-100/ceiling-250 digest in pkg/hubactivity, urgency order, builder-side private drop with totals kept, heartbeat ack + memory-only activityStore, per-user/per-hive GET /api/hub/activity with ETag, stale/not_reporting/missing/truncation disclosure, no rollout/participation/broadcast change). visibleActivityHives (src/pkg/hub/activity.go:143-170) matches the My Hives rule in saas_hives_api.go:747-777 (admin / owner / grant) and is stricter on expiry. No unrelated files touched. Two low notes, neither blocking:

  1. Docs row disagrees with the code on Vary. src/docs/api-reference/hub-server.md:49 says Vary: Cookie; the handler sets Cookie, Authorization (src/pkg/hub/activity.go:363) and the test asserts that (activity_test.go, TestHubActivity_ETagPolling).

    `Cache-Control: private, no-cache`, `Vary: Cookie, Authorization`
    

    (replace the Vary: Cookie fragment in the row.)

  2. The response ETag churns on every beat even when no content changed. The etag is ETagFor(json.Marshal(view)) (activity.go:352-358), and the view embeds received_at (activity.go:291), which record refreshes on each unchanged marker (activity.go:97). So with any reporting hive a viewer's If-None-Match will miss every ~2 min regardless of content, which undercuts the "ETag polling" the issue asks for. The 304 test does not interleave a beat, so it does not catch this. A small fix: hash the view with the volatile timestamps cleared.

    -	body, err := json.Marshal(view)
    +	body, err := json.Marshal(view)
     	if err != nil { ... }
    -	etag := webstatic.ETagFor(body)
    +	stable := view
    +	stable.Hives = slices.Clone(view.Hives)
    +	for i := range stable.Hives {
    +		stable.Hives[i].ReceivedAt, stable.Hives[i].GeneratedAt = nil, nil
    +	}
    +	stableBody, _ := json.Marshal(stable)
    +	etag := webstatic.ETagFor(stableBody)

    stale/status stay in the hashed body, so a freshness flip still produces a new etag.

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

@hivecommons-hive

Copy link
Copy Markdown
Contributor

Hive filed review findings that do not block this PR as backlog items:

Cap: 10 backlog item(s) per PR per day.

@hivecommons-hive

hivecommons-hive Bot commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

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

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

Read pkg/hubactivity/hubactivity.go, pkg/hub/activity.go, the wiring in pkg/hub/server.go / heartbeat.go / spoke/heartbeat.go, and the callers they lean on (buildMyHivesResponse in saas_hives_api.go:747-777, accessGrantExpired, isHubAdmin, canonicalEqual, requireAuth, webstatic.ETagFor). The code looks correct to me; the only blocker is the citation drift the body already predicted.

What I verified

  • Authorization is decided before any digest is copied out of the store: visibleActivityHives (activity.go:154) resolves admin / owner / unexpired grant, and only those IDs go to s.activity.snapshot(ids) (activity.go:351). The rule is My Hives' predicate (saas_hives_api.go:749,766,773) plus an accessGrantExpired check (activity.go:162) — strictly narrower, never wider.
  • s.activity.record (server.go:2737) runs after the beat is authenticated and the registry updated, outside s.mu, so the leaf-lock claim holds.
  • Sanitize re-applies the same ceilings on the hub; Build and Sanitize share normalizeItem, so repo shape, closed sets, slugs, title/mod bounds and the dedupe key cannot diverge between ends.
  • No time.Sleep in either new test file (the TestSleepRatchet baseline is safe).

Why CI is red (all three failures share one cause)

changelog-fragment-guard fails in its "Route-registering or static page files changed — api-reference citations must be resynced" step: inserting the /api/hub/activity route at server.go:1728 shifted the lines cited by src/docs/api-reference/hub-server.md:36-38 (DRIFT … GET /fleet -> pkg/hub/server.go:1769, GET /my-hives -> :1770, POST /api/shared-agent-pool/leases -> :1707). relative links and anchors resolve fails the same Check api-reference source citations step, and native-queue-policy fails as the group gate ("earlier member failure blocks the whole group"). The fix is the one the body names: bash src/scripts/check-api-reference-citations.sh --fix and commit. This is a fork branch, so I cannot push it.

Two small, non-blocking notes

  • ActivityHiveView.ReceivedAt (activity.go:291) is part of the JSON body the response ETag hashes, and record refreshes receivedAt on every beat including unchanged markers (activity.go:97). So the view's ETag changes every time any visible hive beats (~2 min each); for an admin watching tens of hives a 15 s poller will almost never see 304. Correct, just weaker than "ETag polling" suggests — consider hashing a view without received_at, or exposing it separately, in the [scanner] Publish the bounded activity digest from the spoke heartbeat with coalesced 15 s change updates #15963 slice.
  • Docs row (hub-server.md:49) says Vary: Cookie; the handler sets Vary: Cookie, Authorization (activity.go:363).

I have not approved or changed anything.

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

Correctness review (head e7da30d). Authorization rule matches buildMyHivesResponse (saas_hives_api.go:747-777, with stricter expiry handling), the store is a true leaf lock (server.go:2737 records after s.mu.Unlock()), and hub test shards pass. No blocker; two advisories.

1. Response ETag churns on every heartbeat, so If-None-Match rarely yields 304 (low)
ActivityHiveView.ReceivedAt (src/pkg/hub/activity.go:249, set at :291) is part of the body the ETag is hashed over (:358). receivedAt is refreshed on every beat, including unchanged markers (activity.go:98-105), so for a viewer with N hives the etag changes roughly every 120/N seconds even when no item or total changed. TestHubActivity_ETagPolling passes only because no beat lands between the two GETs. Suggest hashing the view with ReceivedAt cleared:

-	body, err := json.Marshal(view)
+	body, err := json.Marshal(view)
 	if err != nil { ... }
-	etag := webstatic.ETagFor(body)
+	// Freshness timestamps change every beat; keep them out of the validator
+	// so an unchanged board polls to 304.
+	tagView := view
+	tagView.Hives = slices.Clone(view.Hives)
+	for i := range tagView.Hives {
+		tagView.Hives[i].ReceivedAt = nil
+	}
+	tagBody, _ := json.Marshal(tagView)
+	etag := webstatic.ETagFor(tagBody)

2. Hub-side test overstates the private guarantee (low, test adequacy)
TestHubActivity_PrivateItemsNeverServedButCounted (src/pkg/hub/activity_test.go:170-190) builds the digest with hubactivity.Build, which already drops the private row (hubactivity.go:139); the hub never sees it. On the hub, Sanitize/normalizeItem keep Private (hubactivity.go:158, 257) and buildActivityView serves every stored item (activity.go:298), so any private: true row a spoke sends (opt-in or non-conforming spoke) is served to every granted viewer. That is within #15951's scope ("private-item exclusion in the digest builder") — but the test name and PR body ("never appears in the response") describe a hub guarantee that does not exist. Suggest a second test that posts a raw Digest{Items: []Item{{…, Private: true}}} through postActivityHeartbeat and asserts the actual pass-through behaviour, so the trust boundary is documented rather than implied.

Note: CI changelog-fragment-guard / relative links failures are the api-reference citation drift you anticipated; the fix is bash src/scripts/check-api-reference-citations.sh --fix.

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

Read the two new packages, the wiring in heartbeat.go/server.go/spoke/heartbeat.go, and the callers they lean on (requireAuth, isHubAdmin, accessGrantExpired, canonicalEqual, buildMyHivesResponse). The code looks correct to me; what is blocking the PR is the api-reference citation drift, which is fixable in one command.

Blocking (CI red): api-reference citations drifted. The three lines inserted at src/pkg/hub/server.go:1726-1728 shift every citation below them in src/docs/api-reference/hub-server.md; the relative links and anchors resolve and changelog-fragment-guard jobs fail on 29 DRIFT … (line does not register it) rows (e.g. hub-server.md:36 GET /fleet -> pkg/hub/server.go:1769). I ran bash src/scripts/check-api-reference-citations.sh --fix on this head locally: 29 rewritten, 0 unresolved, only hub-server.md touched. Commit that result and the two red checks should go green (native-queue-policy is red only because it mirrors the guard). This is a fork branch, so I cannot push it for you.

Verified correct

  • src/pkg/hub/server.go:2735 — s.activity.record runs after the heartbeat is authenticated and after the registry branch that returns 403/503 for unprovisioned or overfull hives, so an unaccepted beat never writes a digest. It is also after s.mu.Unlock(), consistent with the leaf-lock comment on activity.go:60.
  • src/pkg/hub/activity.go:155-178 — visibleActivityHives matches the My Hives rule at saas_hives_api.go:747-777 (admin → all; otherwise user.Hives grant or canonicalEqual(h.Owner, username)), and additionally drops grants accessGrantExpired rejects. snapshot (activity.go:124) only copies the authorized IDs, so unauthorized blocks never enter the body or its ETag.
  • src/pkg/hub/activity.go:85-101 — the unchanged-marker path compares against CleanETag, matching how Sanitize stores the etag (hubactivity.go:170), so a marker cannot wedge. A marker for an unknown hive returns "", which correctly forces a full resend.
  • src/pkg/hubactivity/hubactivity.go:165-192 — Sanitize enforces the 250 ceiling, repo shape, closed kind/author_kind sets, slugs, dedupe on repo#n, clamps, and strips Cc/Cf/Zl/Zp; boundCounts is deterministic (sorted keys). No mutation of the input.

Two small things, not blockers

  1. Docs row says Vary: Cookie (hub-server.md:49) but the handler sets Vary: Cookie, Authorization (activity.go:349). Worth aligning while you are in that file.
  2. ActivityHiveView.ReceivedAt (activity.go:261) is refreshed on every beat, including unchanged markers (activity.go:97), so the response ETag changes roughly every heartbeat even when no item changed. Fine for the stated 15 s polling cadence; just noting that 304 hit rate is bounded by heartbeat interval, not by content stability.

Open question for the follow-ups, not this slice: Sanitize keeps Private items a spoke sends (hubactivity.go:177-187 has no Private check); the drop lives only in Build (hubactivity.go:143). The body states this is per #15951 scope and TestHubActivity_PrivateItemsNeverServedButCounted exercises the spoke-side builder, so I am treating it as decided — flagging only so the hub-side consent record is not forgotten in #15963/#15966.

Body and diff agree otherwise: the changelog fragment is present and correctly named, nothing populates the digest yet, and no participation/broadcast setting changed.

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

Style / conventions review (read at head e7da30d, diff + pkg/hub/server.go, pkg/hub/activity.go, docs/api-reference/hub-server.md, scripts/check-api-reference-citations.sh).

1. hub-server.md route citations drifted — CI changelog-fragment-guard will fail (src/docs/api-reference/hub-server.md:46-67)

The new struct field (src/pkg/hub/server.go:1002) and route registration (server.go:1726-1728) shift every pkg/hub/server.go:NNNN citation below them, but the table still says e.g. /api/fleet-stats → server.go:1722 (now 1723) and /api/hub/version → server.go:1727 (now 1731). Running the repo's checker at this head:

$ bash src/scripts/check-api-reference-citations.sh src/docs/api-reference/hub-server.md
DRIFT api-reference/hub-server.md:46 GET /api/fleet-stats -> pkg/hub/server.go:1722 (line does not register it)
…
api-reference citations: 29 drifted citation(s).

(merge-base is clean: "all pkg/: references verified"). .github/workflows/changelog-fragment-guard.yml:159 runs this in CI. Fix:

bash src/scripts/check-api-reference-citations.sh --fix && git add src/docs/api-reference/hub-server.md

2. Doc/code mismatch on Vary (src/docs/api-reference/hub-server.md:49 vs src/pkg/hub/activity.go:363)

The new table row documents Vary: Cookie, but the handler sets h.Set("Vary", "Cookie, Authorization"). Change the doc text to `Vary: Cookie, Authorization` (or drop Authorization from the header if a cookie is the only accepted credential on this route — requireAuth is cookie-based, so the latter is arguably the more accurate contract).

Otherwise the package layout (pkg/hubactivity shared contract, activityStore leaf lock documented at server.go:1002, same hub/spoke HeartbeatPayload mirroring as existing fields) follows existing idioms.

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

docs-currency review (read at head e7da30d against true merge-base 1c25e90; the operator-reference/README.md and api_event_triggers_test.go hunks GitHub shows are master commits #15995/#15997 missing from this branch, not changes of this PR — a rebase makes them disappear).

1. hub-server.md route citations drift — the changelog-fragment-guard CI step will fail. src/pkg/hub/server.go gains a struct field at :1002 and three lines at :1726–1728, so every pkg/hub/server.go:<line> citation from src/docs/api-reference/hub-server.md:36 through :67 is now off by 1–4 (e.g. row 46 still says /api/fleet-stats → server.go:1722; at head the registration is at server.go:1723). .github/workflows/changelog-fragment-guard.yml:159 runs check-api-reference-citations.sh, which reports 29 drifted citation(s) at this head. Fix (mechanical, I ran it: 29 rewritten, 0 left unresolved):

bash src/scripts/check-api-reference-citations.sh --fix && git add src/docs/api-reference/hub-server.md

2. Vary header documented too narrowly. hub-server.md:49 says Vary: Cookie; src/pkg/hub/activity.go:363 sets Vary: Cookie, Authorization.

`Cache-Control: private, no-cache`, `Vary: Cookie, Authorization`.

(apply inside the existing row text — the row is one line.)

Everything else in the new row checked out against the code: 401 for anonymous (activity.go:326), 400 on filters > 200 runes (:45, :205), response cap 2000 = 8 * MaxItemsCeiling (:42, hubactivity.go:33), two-heartbeat staleness (:31-32), 304 on If-None-Match (:365), and the hives[]/items[]/totals field names (activity.go:241-268, hubactivity.go:67-99). Optional: the row could also mention that a hive's digest is forgotten after 24h of silence (activity.go:38), which the changelog fragment alludes to but the reference does not.

@hivecommons-hive

Copy link
Copy Markdown
Contributor

@Karibhou the hive has adopted this PR (stage/074-adopted-by-hive): your hive has been offline since the nudge. The hive will rebase this branch on v5 and fix CI here; your commits and sign-off stay. Push a new head yourself at any time and the hive yields it back to you.

Karibhou and others added 2 commits October 31, 2026 05:38
…b/activity

First implementation slice of the hub-wide Activity Monitor (RFC hivecommons#15861 by
@hanthor, child hivecommons#15951):

- pkg/hubactivity: shared wire contract for the heartbeat `activity` block.
  Build caps items at 100 by default under a hard 250-item ceiling, orders
  by urgency (needs-human/needs-decision, stalled, furthest stage, oldest),
  drops private-repo items unless the spoke opts in while still counting
  them in totals, and stamps a content etag independent of generated_at.
  Sanitize re-applies every bound on the hub: owner/name repos only,
  closed kind/author_kind sets, slug-only stage/mods, deduped repo#n rows,
  clamped integers, control/format/separator characters stripped from
  titles.
- Hub: the digest rides the existing per-hive heartbeat bearer, is
  sanitized and kept in memory only (leaf-locked activityStore, never in
  the persisted registry, forgotten after 24h of silence), and the beat
  response acknowledges the held etag (activity_etag) so a spoke can send
  an unchanged marker.
- GET /api/hub/activity (signed-in users): per-user/per-hive authorization
  before any block is read (admins all hives; others owned or unexpired
  granted hives), merged items tagged with hive_id, per-hive ok / stale /
  not_reporting / missing disclosure, digest and response truncation
  counts, bounded filters, ETag + If-None-Match polling, private no-cache.
- Spoke payload/response carry the optional fields; nothing populates the
  digest yet (hivecommons#15963). No rollout, participation or broadcast setting
  changes.

Hive-Run: hivecommons#15861
Hive-Plan: rfc-15861 decomposition, child 1 (hivecommons#15951)
Hive-Spec: rfc-15861#A-B-C
Signed-off-by: Karibhou <157208370+Karibhou@users.noreply.github.com>
…i/hub/activity

The new activityStore field and /api/hub/activity registration in
pkg/hub/server.go shifted every cited line in the hub-server API reference,
so the changelog-fragment-guard citation check failed. Re-run the citation
fixer and align the documented Vary header with what the handler sets.

Signed-off-by: scanner <280983584+hivecommons-hive[bot]@users.noreply.github.com>
@hivecommons-hive
hivecommons-hive Bot force-pushed the feat/hub-activity-monitor-rfc-15861 branch from e7da30d to 51bd49a Compare October 31, 2026 09:39
@hivecommons-hive

Copy link
Copy Markdown
Contributor

hive/awaiting-ci: rebased the adopted branch onto v5 (author commit kept intact, cf94811) and added one signed docs commit (51bd49a) that re-runs check-api-reference-citations.sh --fix (29 pkg/hub/server.go citations in hub-server.md) and aligns the documented Vary header with the handler (Cookie, Authorization). That single drift was the cause of changelog-fragment-guard, relative links and anchors resolve and the downstream native-queue-policy failure. 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

Copy link
Copy Markdown
Contributor

Superseded by hive: re-authored as #16005 with the same commits and sign-off because its commits needed a sign-off only a hive-owned branch can carry. This PR is closed; if #16005 fails, hive reopens it.

@hivecommons-hive hivecommons-hive Bot added the hive/superseded Closed by Hive: a different merged PR already landed this change label Oct 31, 2026
@hivecommons-hive hivecommons-hive Bot closed this Oct 31, 2026
@Karibhou
Karibhou deleted the feat/hub-activity-monitor-rfc-15861 branch November 15, 2026 11:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dco-signoff: yes Indicates the PR's author has signed the DCO. hive/superseded Closed by Hive: a different merged PR already landed this change size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

✨ Bounded activity heartbeat contract and authorized hub aggregation API

1 participant