the meta flake takes docs from the pinned hyperhive input
This commit is contained in:
parent
bb13909d8e
commit
daf38e4c55
16 changed files with 29 additions and 197 deletions
|
|
@ -9,7 +9,7 @@
|
|||
{
|
||||
options.services.hyperhive.agent.docs.enable = lib.mkEnableOption ''
|
||||
make the hyperhive reference docs (the repo `docs/` tree, shipped
|
||||
read-only as the standalone `hyperhive-docs` derivation) available
|
||||
read-only as the `reference-docs` package) available
|
||||
in-container. When enabled the harness exposes the docs dir to claude
|
||||
via `claude --add-dir`, so the markdown is readable at
|
||||
`$HIVE_DOCS_DIR/`, and appends a single pointer sentence to the agent's
|
||||
|
|
@ -26,11 +26,7 @@
|
|||
Store path of the reference-docs tree exposed at `$HIVE_DOCS_DIR`
|
||||
when `services.hyperhive.agent.docs.enable` is set. Defaults to the flake's
|
||||
`reference-docs` package (the `nix/packages/reference-docs.nix`
|
||||
build) so a standalone container build from a full checkout
|
||||
works unchanged. The generated meta flake overrides this with the
|
||||
narrow `hyperhive-docs` flake input so a doc edit only
|
||||
re-locks that input instead of rebuilding the container from a
|
||||
re-hashed `hyperhive` source.
|
||||
build), which the meta flake's pinned `hyperhive` input provides.
|
||||
'';
|
||||
};
|
||||
|
||||
|
|
@ -40,9 +36,7 @@
|
|||
# `--add-dir` so the docs are readable, and appends a single
|
||||
# pointer sentence to the system prompt
|
||||
# (hive-agent::prompt::render) telling the agent the docs exist.
|
||||
# Source is `services.hyperhive.agent.docs.source` (the narrow `hyperhive-docs`
|
||||
# meta-flake input, or `pkgs.hyperhive-docs` for standalone
|
||||
# builds). See hive-agent::turn.
|
||||
# Source is `services.hyperhive.agent.docs.source` (default: the `reference-docs` package). See hive-agent::turn.
|
||||
HIVE_DOCS_DIR = "${config.services.hyperhive.agent.docs.source}";
|
||||
};
|
||||
};
|
||||
|
|
|
|||
Loading…
Reference in a new issue