ee52ddc027
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.
27 lines
864 B
TOML
27 lines
864 B
TOML
# `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
|
|
version.workspace = true
|
|
readme = "README.md"
|
|
|
|
[lints]
|
|
workspace = true
|
|
|
|
[dependencies]
|
|
anyhow.workspace = true
|
|
forgejo-api.workspace = true
|
|
hive-agent-sock.workspace = true
|
|
reqwest.workspace = true
|
|
serde.workspace = true
|
|
serde_json.workspace = true
|
|
time.workspace = true
|
|
tokio.workspace = true
|
|
tracing.workspace = true
|
|
tracing-subscriber.workspace = true
|
|
url.workspace = true
|