refs: repoint seven comments that name files which have moved
Comments cite nix modules, scripts and crate source files constantly,
and nothing evaluates a comment — so when a file moves, the reference
rots silently and `nix flake check` stays green. A reader following one
finds nothing and cannot tell whether the file was renamed, deleted, or
never existed.
Seven such references, each repointed at the file that actually holds
the thing the sentence is about rather than at the directory the old
name became:
hive-c0re/src/agent_config/limits.rs hive-agent/src/mcp.rs
-> hive-agent-mcp/src/mcp/mod.rs
hive-agent-mcp/src/mcp/mod.rs hive-c0re/src/limits.rs
-> hive-c0re/src/agent_config/limits.rs
(and the module path in the doc
comment above it, which was stale
in the same way)
hive-c0re/src/forge/mod.rs hive-c0re/src/knowledge.rs
-> hive-c0re/src/workers/knowledge.rs
nix/host-modules/hive-c0re/options.nix hive-c0re/src/hive_stats.rs
-> hive-c0re/src/stats/hive_stats.rs
nix/packages/default.nix nix/host-modules/hive-c0re.nix
-> .../hive-c0re/options.nix
nix/agent-modules/network.nix nix/host-modules/hive-gateway.nix
-> .../hive-gateway/dnsmasq.nix
frontend/README.md nix/modules/frontend.nix
-> nix/packages/frontend.nix
The two `limits.rs` comments are a matched pair: each names the other's
old path, so the "keep in sync" instruction they exist to carry pointed
both ways at nothing.
Where a flat module became a directory the target is the file that
declares the named thing, not `default.nix` by reflex — the
`preBuildAgentTemplates` option is declared in `options.nix`, and the
DHCP pool that sentence is about lives in `dnsmasq.nix`.
Comments only; no behaviour change. Refs #3923, which is about whether a
gate should cover this class at all — that question is unanswered and
this does not close it.
This commit is contained in:
parent
9b14014077
commit
d2747c7b77
7 changed files with 8 additions and 8 deletions
|
|
@ -45,11 +45,11 @@ use render::{
|
|||
/// harness runs as the agent user and has write access to `state/`, whereas
|
||||
/// hive-c0re's `hive-core` user does not after the privsep migration).
|
||||
///
|
||||
/// Mirrors the validation in `hive-c0re::limits::check_status_text` so
|
||||
/// Mirrors the validation in `hive-c0re::agent_config::limits::check_status_text` so
|
||||
/// the file is never written with text the server would later reject (which
|
||||
/// would leave a stale invalid entry on disk).
|
||||
fn write_status_file(text: &str) -> Result<(), String> {
|
||||
// 200 chars mirrors STATUS_MAX_CHARS in hive-c0re/src/limits.rs.
|
||||
// 200 chars mirrors STATUS_MAX_CHARS in hive-c0re/src/agent_config/limits.rs.
|
||||
// Keep in sync if that constant changes.
|
||||
const STATUS_MAX_CHARS: usize = 200;
|
||||
let trimmed = text.trim();
|
||||
|
|
|
|||
Loading…
Reference in a new issue