dtoro/oikos

Fork 0

Files

dtoro d80a394b7f

ci / build-test (push) Has been cancelled

Details

ci / docker-build (push) Has been cancelled

Details

docs: fix plan/repo drift, retire dead Goose+Nomos and Caveman tooling

Documentation and repo-hygiene pass following the client/server split:

Plan drift (audited all other active plans against current code):
- oikos-gaps-and-improvements.md: mark Section C and D.5 resolved (both
  described cmd/hermes, renamed to cmd/nomos with a real LLM loop since);
  refresh ~10 stale file:line citations; fix tool-count (33, not 28).
- liveness-drift-and-ux-cohesion.md: fix stale default-model claim (now
  deepseek-v4-pro since 2026-07-10) and "not yet deployed" status.
- nomos-agent-code-review.md: fix C1's citation (one unauthenticated route
  to nomos now, not two, after the client/server split).
- wails-desktop-app.md: record the production deploy outcome.

Repo structure: added missing directories to README/CONTRIBUTING layout
tables (checks/, tools/, cmd/webhook/, docs/operations/), fixed a broken
link, added ADR 0015 documenting the auth/CORS/client-split model (there
wasn't one despite CONTRIBUTING's own process requiring it), normalized
ADR 0013/0014's format drift, added an Authentication section to
AGENTS.md/CLIENTS.md (every example call was missing the now-required
bearer header).

Retired the Goose+Nomos workstation flow (bootstrap.sh --with-nomos,
tools/setup-nomos-soul.sh, .agents/operations/nomos-agent.md) and the
Caveman auto-install tooling (tools/setup-caveman.sh, tools/caveman/) —
both superseded by the production containerized Nomos agent, which has
never used either. Kept .agents/shared/caveman.md itself (the terse
writing-style convention agents still follow by reading it).

Deleted the orphaned legacy Python oikos/ directory — nothing imports it,
and bin/homelab (the CLI it was kept for) no longer exists in the repo.

Rewrote .agents/operations/agent-enrollment.md (365 -> ~110 lines) and
commands.md to match the current architecture instead of the retired
`homelab` CLI; migrated the still-true networking prerequisites (Netbird,
split-horizon DNS, SSH key distribution) into the knowledge base as a
runbook via upsert_knowledge rather than duplicating them in markdown.
Updated all 10 .agents/skills/ runbooks referencing the dead CLI with
their real MCP tool / REST API equivalents, or flagged them as needing
verification where no equivalent is confirmed yet.

Two real bugs found and fixed, not just docs:
- The tools/setup-*.sh auto-setup glob was tools/*.setup.sh in THREE
  places (tools/post-pull.sh, bootstrap.sh, and internal/httpapi/impl.go's
  GetClientContext handler) since the mechanism's introduction on
  2026-06-02 — never matched any real filename, so no client has ever
  picked up an auto-setup script via git-pull or the context-poller sync.
  Fixed all three; the Go server-side fix is the one that actually matters
  since it's what the current context-poller mechanism depends on.
- bootstrap.sh removed dead vestigial --gitea-token/--gitea-user flags
  (parsed, never consumed) left over from an earlier clone-based model.

Also flagged, not fixed (documented as an open gap in
client-enrollment/SKILL.md): bootstrap.sh tells a freshly-enrolled client
to call POST /api/v1/clients/{slug}/activate to finish enrollment, but
that route doesn't exist in api/openapi.yaml — EnrollClient sets entities
to provisioning and nothing currently transitions them to active.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-07-12 18:19:41 +02:00

2.0 KiB

Raw Blame History

name, risk_class, inputs, verification, docs_update_checklist, transition

name

risk_class

inputs

verification

docs_update_checklist

transition

lifecycle-migrate-node

config_mutation

node_name

source_host

target_host

MCP get_blast_radius (re-check blast radius); MCP get_service_status for every hosted service

doc_page_migration_note

inventory_host_and_lan_ip

active -> migrating -> active

Lifecycle: migrate a node

Modeled on the strong Phase 1+2 migration (archive/hermes-plans/2026-06-03_110000-library-ssd-migration-to-ludo-mini.md). Requires (ontology): preflight + backup-verified before migrating; post-verify + Caddy backends checked + mounts checked + docs updated before returning to active.

MCP preflight for every service the node hosts — capture current health as a baseline.
Verify backups are current for anything with data at rest on the node (see backs-up-to edges once populated).
Set state: migrating in inventory.yaml.
Perform the migration (pct/qm move, or create-on-target + data-copy + destroy-source, per the specific case).
Update inventory.yaml: new host:, lan_ip, mesh addresses for the node; update every services: entry whose backend pointed at it if the backend name itself changes (usually it doesn't — only the host:/lan_ip on the guest entry moves).
Post-verify: re-run the Week-1 drift check by hand — confirm Caddy's backend IP for each affected service matches the new lan_ip (automatic in Week 3's drift detector), confirm mounts still resolve.
MCP get_service_status for every service the node hosts.
Set state: active. Add a migration note to the node's doc page (old host/IP → new, date, phase reference) — this repo's convention for every past migration (see archive/knowledge/containers/101-jellyfin.md, containers/129-house.md).

Regenerate: oikos seed (re-ingests seeds/inventory.yaml into the DB — the DB is authoritative at runtime, the YAML is the source of truth on disk).

2.0 KiB Raw Blame History

Lifecycle: migrate a node

2.0 KiB

Raw Blame History