Commit graph

10 commits

Author SHA1 Message Date
codex
ea0452b9a9 Publish cluster resource evidence and gate ThreePhoenix
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa
2026-08-22 12:34:25 +02:00
codex
452e1d7f7f chore: align ThreePhoenix and capacity workplans with current axes
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Cite ADR-0006/0008, cancel leaked PG/forge tasks, retitle ingress to
Traefik, and fix the RAIL-BS-WP- convention in AGENTS.md.
2026-08-15 20:52:03 +02:00
codex
a32a64454a Refresh Current State against the live clusters
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 2s
Verified against railiance01 on 2026-08-12 once API access was restored.

Corrections: two clusters are managed, not one - railiance01 is the current
primary running the live workloads, CoulombCore is the older frozen cluster.
Traefik is the ingress controller, not nginx. ArgoCD is not on railiance01 at
all; it runs on CoulombCore only, so the previous entry was accurate for that
host but misleading as a general cluster-level claim.

Adds the verified addon and CNPG cluster inventory, notes the absence of any
monitoring stack, and points at RAIL-HO-WP-0009 for the source-restricted k3s
API.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-12 00:04:23 +02:00
codex
be3b8ff31e Clarify cluster boundary for rail-kubernetes
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 6s
2026-07-25 11:17:51 +02:00
b3b0c3e3ff Repo hygiene + new workplans (RAIL-BS-WP-0008/0009)
- Add RAIL-BS-WP-0008 (activity-core WP-0016 deploy) and RAIL-BS-WP-0009
  (admin-sync smoke) from inbox asks 87952ff1 / aa8b7986
- Archive finished workplans to workplans/archived/ per ADR-001 convention;
  normalize frontmatter statuses (completed/done -> finished)
- Fill stack-and-commands.md, complete repo-boundary.md, refresh SCOPE
  Current State, add docs/operator-runbook.md for production-touching targets

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-02 00:02:36 +02:00
c7fd4d2715 Scope update from repo-scoping refactor 2026-05-01 12:34:05 +02:00
595a043634 feat(boundary): move Gitea Helm values to railiance-apps (T06)
gitea-values.sops.yaml relocated to railiance-apps/helm/ per
ADR-003 boundary rules — Gitea is S5, values belong in S5 repo.
Tombstone left in helm/MOVED.md. SCOPE.md updated to reflect
resolved violation.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-03-27 13:23:41 +01:00
9fc5a033d5 feat(s2): add Gitea SSH NodePort service + close WP-0004 (backup tool, scope updates)
- helm/gitea-ssh-nodeport.yaml: expose Gitea SSH on NodePort 30022 (targetPort 2222)
  for on-node git automation (RAIL-HO-WP-0004-T07)
- tools/cmd/railiance-backup-s2: fix SQLite hot backup (was broken etcd-snapshot)
- tools/cmd/railiance-restore-s2: update restore instructions for SQLite mode
- workplans/RAIL-BS-WP-0004-safety-net.md: mark done
- SCOPE.md: update current state, document boundary violations, fix connectivity docs

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-03-27 01:07:02 +01:00
a747445790 Updated scope 2026-03-20 23:42:59 +01:00
2acc06f466 docs: add SCOPE.md for rapid orientation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-03-17 23:11:38 +01:00