0db83c40a0
hive-forge-notify grows a second binary, hive-github-notify. The two share the notification half of the job — tolerant parse, classification, formatting, dedupe, todo delivery — and nothing else: each binary owns its host's protocol outright. Two binaries rather than one multi-source daemon, and rather than a cargo feature. A feature would unify across the workspace and cost every crate its build cache. Two binaries keep the decision in nix: forge.nix installs the forge unit, github.nix installs the github one under hyperhive.github.enable, so a hive built without that module has no github poller in its closure at all — GitHub access is separable (a tier, a policy boundary), not merely switched off. Both binaries ship from the existing derivation, so packages.nix is untouched. The split is real at the code level too, not just at the unit level. source.rs is a trait; the impls live in the binaries that use them, so neither binary links the other's protocol code and the library names no host at all. The forge-only assigned-issue rollup moves into the forge binary for the same reason: it asks the forge what is assigned to this agent, which is not a notification-protocol concern. At runtime the github unit needs a PAT at <state>/github-token, the same dashboard-provisioned token the gh wrapper and the git credential helper already use. No PAT: it logs why and exits 0, which is why the unit is Restart=on-failure and not always. Forgejo's notifications API is modelled on GitHub's, so one tolerant parse serves both — the differences (string thread ids, PullRequest vs Pull) are absorbed by lenient deserializers rather than a second parse path. Thread ids normalise to String at the parse boundary; they are only ever opaque keys. Todo keys gain a per-source prefix so the two hosts cannot collide, and the forge's is deliberately empty to keep existing forge todo keys stable across the deploy that lands this. The github loop honours the server's X-Poll-Interval, re-arming only when the server asks for a slower cadence than ours; the hint is read before the status check, because it arrives on error and empty pages too and that is exactly when it matters. Reading the notification stream needs the notifications scope on the PAT, which a token minted for push access typically lacks; the failure mode is silence, so docs/github.md says so explicitly.
23 lines
996 B
Nix
23 lines
996 B
Nix
# The hyperhive-built packages the harness modules consume, threaded
|
|
# in explicitly as an option — no overlay. The flake's
|
|
# `nixosModules.{agent-base,ruth}` set this to the flake's own package
|
|
# outputs via `lib.mkDefault`, so a per-agent override of an
|
|
# individual key still wins.
|
|
{ lib, ... }:
|
|
{
|
|
options.hyperhive.packages = lib.mkOption {
|
|
type = lib.types.attrsOf lib.types.package;
|
|
internal = true;
|
|
description = ''
|
|
hyperhive package outputs consumed by the harness modules: the
|
|
per-binary daemon/CLI packages (`hive-agent`, `hive-agent-mcp`,
|
|
`hive-bash-daemon`,
|
|
`hive-forge`, `hive-forge-notify`, `hive-github-notify`,
|
|
`hive-matrix-daemon`,
|
|
`hive-metric`, `hive-screen-mcp`) plus the `assets`, `frontend`,
|
|
`reference-docs` and `claude-plugins` trees. Wired by the flake's agent-base/ruth
|
|
nixosModules to `hyperhive.packages.<system>.*`; override an
|
|
individual key per-agent to swap in a patched binary.
|
|
'';
|
|
};
|
|
}
|