docs: align source entry points with rebuilt wiki #229
No reviewers
Labels
No labels
area:authentication
area:flake-utilities
area:performance
area:tbd
host:chaos
host:electra
host:fleet
host:lyra
host:nova
host:vega
investigation
phase:cutover
phase:deploy
phase:mcp
phase:module
phase:packaging
phase:prep
phase:validation
priority:high
priority:medium
project:attic-postgres-lyra-rollout
project:auto-update-reliability
project:auto-update-remediation
project:declarative-purity-cleanup
project:external-review
project:fleet-boundary-cleanup
project:host-facts-refactor
project:lyra-nixos-deploy
project:lyra-service-stack-migration
project:nebula-mesh-network
project:nixos-build-deployment-pipeline
project:security-hardening
project:service-stack-migration
project:vega-sillytavern-cutover
project:wiki-rebuild
repo:numtide/flake-utils
repo:numtide/nix-auth
repo:numtide/nixos-passthru-cache
repo:numtide/nix-relay
service:auto-update
service:mem0
service:nix
service:sillytavern
service:slskd
service:synthseek
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
nimmo/nixos-config!229
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/wiki-final-cutover"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Refs #223
Condense README to source entry points and essential operator commands; preserve implementation-adjacent auto-update remediation details in docs/auto-update-remediation.md. Replace the update-wiki skill global sync marker with per-page provenance and review triggers. Correct AGENTS host inventory and Paseo topology to match current Nix declarations.
Validation: focused source and wiki comparison; just --list recipe check; local Markdown path check; git diff --check and staged diff check. Documentation-only; no deployment or Nix build required. Live service placement is not asserted from configuration alone.
The wiki clone is committed and published independently. Final Home/navigation and maintenance-page cutover updates follow after this source MR is reviewed.
09f108780c741d0dd06eAutomated code review
Reviewed commit:
bc711db7aa649af0a9e4214a744c67cc2cb56e6fVerdict: Requires further work
Resolve the blocking or important findings and investigate failed deterministic checks before merging.
Overall assessment
The pull request refactors documentation by condensing the root README.md into entry points and essential commands, moving detailed auto-update remediation logic to docs/auto-update-remediation.md. It updates .agents/skills/update-wiki/SKILL.md to replace global wiki sync markers with per-page provenance checks. It also corrects the host inventory in AGENTS.md (adding Cosmos and Chaos) and updates the Paseo topology description to reflect that the relay/web UI has moved from Vega to Chaos, while Vega retains a fallback.
Blocking findings
None.
Important findings
Impact: The documentation states these hosts run NixOS 26.05. If this version is incorrect (e.g., if they are actually on a different stable release or unstable), it misleads operators regarding compatibility and available packages.
Suggested fix: Verify the actual
system.stateVersionand channel for Cosmos and Chaos against their live configurations or deployment records.Suggestions
Paseo remote-work topology: Paseo is the AI agent orchestration layer. Vega and Lyra enable a Paseo daemon bound by default to their Nebula overlay IP... Chaos declares the self-hosted Paseo relay and web UI containers; Vega retains a fallback relay while the Chaos cutover is investigated.
Impact: The text mentions a 'Chaos cutover' being investigated, which implies the change might be provisional or incomplete. If the cutover is complete, this language should be updated to reflect the final state to avoid confusion about service ownership.
Suggested fix: Confirm if the Chaos cutover is finalized. If so, remove 'while the Chaos cutover is investigated' and clarify that Vega's fallback is deprecated or removed.
Tests and validation
Questions
Review limitations
AGENTS.mdcontent.Diff coverage
.agents/skills/update-wiki/SKILL.md: reviewed — included in a context-limited batchAGENTS.md: reviewed — included in a context-limited batchREADME.md: reviewed — included in a context-limited batchdocs/auto-update-remediation.md: reviewed — included in a context-limited batchReview metadata
Review follow-up: the README table is explicitly the configured main package set, not a claim about a live kernel/version. flake.nix pins nixpkgs-stable to nixos-26.05 and passes it to both cosmos and chaos; live deployment remains outside this documentation MR. modules/containers/ and modules/databases/ both exist and are imported by hosts; AGENTS now lists them (
bc711db) and corrects the stale planned-WireGuard wording. modules/services/paseo-daemon.nix defaults listenAddress to the Nebula overlay IP and opens TCP 6767 only on nebula.mesh; hosts/chaos/default.nix enables relay and web UI, while hosts/vega/default.nix retains the fallback relay. No live cutover claim is made. The earlier review JSON-escape failure was in the advisory model; the rebased review and deterministic PR test succeeded before this follow-up commit. Awaiting fresh checks forbc711db.Follow-up
5ebbd32resolves the remaining important wording finding: AGENTS now says the cosmos/chaos flake targets select the NixOS 26.05 package set, without asserting an unverified live OS version. The channel is directly in flake.nix and both hosts pass nixpkgs-stable to makeNixosSystem. The Paseo cutover wording is intentionally provisional because hosts/vega/default.nix retains a fallback relay and the live cutover is not established by this repository alone.Final merge evidence: source commit
5ebbd328d0changes only AGENTS wording from an unverified live NixOS version to the flake-selected 26.05 package set. Local focused review, source Markdown path check, just --list, and git diff --check passed. The deterministic Build and Push Attic Cache PR test succeeded on predecessor741d0dd, and the advisory review succeeded on predecessorbc711db. The final advisory job at run 900 failed while parsing Ollama output (Invalid backslash escape); its log contains no finding or deterministic test failure. This is an advisory model-output failure, not a configured required branch status check. The earlier actionable module-map and version-wording findings were addressed inbc711dband5ebbd32. No deployment or live-state claim is being made.