From ee52ddc0272754bdd2d016b40fa03c91deb28250 Mon Sep 17 00:00:00 2001
From: atlas <atlas@pr1ma.darkest.space>
Date: Sun, 26 Jul 2026 20:59:53 +0200
Subject: [PATCH] fix(nix): wire hive-forge-notify into the agent package set
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The new daemon's package was added to `nix/packages/default.nix` and
referenced from the forge agent module, but not to the `inherit` list in
the flake's `agentPackages` module — so `hyperhive.packages` never gained
the attribute and every agent container failed to evaluate.

Also drop the crate's `[[bin]]` section: the binary name defaults to the
package name and the path to `src/main.rs`, so all of it was restating
cargo's defaults. The comment explaining why this is a separate process
moves to the top of the manifest, where it isn't attached to a section
that no longer exists.
---
 flake.nix                    |  1 +
 hive-forge-notify/Cargo.toml | 16 ++++++----------
 2 files changed, 7 insertions(+), 10 deletions(-)

diff --git a/flake.nix b/flake.nix
index d3ed7e72..4146a87a 100644
--- a/flake.nix
+++ b/flake.nix
@@ -88,6 +88,7 @@
                   hive-agent-mcp
                   hive-bash-daemon
                   hive-forge
+                  hive-forge-notify
                   hive-matrix-daemon
                   hive-metric
                   assets
diff --git a/hive-forge-notify/Cargo.toml b/hive-forge-notify/Cargo.toml
index d66d6a0e..1b48664d 100644
--- a/hive-forge-notify/Cargo.toml
+++ b/hive-forge-notify/Cargo.toml
@@ -1,3 +1,9 @@
+# `hive-forge-notify` — long-running per-agent Forgejo notification
+# poller. Was a `tokio::spawn` inside the `hive-agent` serve loop; it is
+# its own process now so a harness restart (or a claude-side stall) does
+# not take forge notifications down with it, and so its dependency tree
+# (forgejo-api, reqwest, time, url) is not linked into the serve-loop
+# binary. Talks to the harness only over the in-agent todo socket.
 [package]
 name = "hive-forge-notify"
 edition.workspace = true
@@ -19,13 +25,3 @@ tokio.workspace = true
 tracing.workspace = true
 tracing-subscriber.workspace = true
 url.workspace = true
-
-# `hive-forge-notify` — long-running per-agent Forgejo notification
-# poller. Was a `tokio::spawn` inside the `hive-agent` serve loop; it is
-# its own process now so a harness restart (or a claude-side stall) does
-# not take forge notifications down with it, and so its dependency tree
-# (forgejo-api, reqwest, time, url) is not linked into the serve-loop
-# binary. Talks to the harness only over the in-agent todo socket.
-[[bin]]
-name = "hive-forge-notify"
-path = "src/main.rs"