174 commits

This branch

This branch

All branches

Author	SHA1	Message	Date
tegwick	e3e05eddf0	Adopt repo-owned workplan prefix per ADR-007 ... Retires the shared prefix. Live plans move to the new prefix keeping their running number; finished and archived files keep the old prefix as historical record, per the ADR-007 option 2 migration ruling. Hub UUIDs are unchanged, so reconciliation matches on state_hub_workstream_id rather than filename and will update the slug in place instead of registering duplicates. Assigned in RMGR-WP-0004-T09. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-17 10:48:58 +02:00
tegwick	963de9cd4f	Publish NetKingdom registration entry point	2026-08-14 00:40:08 +02:00
tegwick	ad96deec9f	Deploy coulomb-social:7fcd0cf space content sync (T05)	2026-08-12 03:31:37 +02:00
tegwick	93688e1ffd	Deploy coulomb-social:9c10037 Forgejo markdown read path	2026-08-12 02:00:46 +02:00
tegwick	b1a43125ef	Point coulomb-social image at 86b5424 (Space model)	2026-08-12 01:38:44 +02:00
tegwick	b1637d04d2	Fix core-hub Makefile image repository default too ... CORE_HUB_IMAGE_REPOSITORY was the only one of four app image defaults still on gitea.coulomb.social. It is passed as --set image.repository= when a tag is supplied, so it overrides helm/core-hub-values.yaml at deploy time - fixing the values file alone would have left the actual deploy path pointing at the frozen CoulombCore registry. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-11 23:18:37 +02:00
tegwick	48a5e6eac0	Point core-hub production values at forgejo.coulomb.social ... helm/core-hub-values.yaml was the last file still pulling from gitea.coulomb.social. Both hostnames resolve, but to different machines - gitea.coulomb.social to 92.205.130.254 (CoulombCore) and forgejo.coulomb.social to 92.205.62.239 (Railiance01) - so this quietly deployed core-hub from the frozen CoulombCore registry rather than failing loudly. Every other values file in this repo, including charts/core-hub/values.yaml for the same app, already used forgejo. The tag is a render-time placeholder; deploys pass CORE_HUB_IMAGE_TAG=<sha>, so the next core-hub rollout must confirm that sha is present on the Forgejo registry before promoting. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-11 23:18:14 +02:00
tegwick	5ef514b96d	Correct stale Gitea current-state claims to Forgejo ... Forgejo has replaced Gitea as the forge. Updates SCOPE.md Current State, AGENTS.md and .claude/rules/repo-identity.md, which still described Gitea as the operational forge. Deliberately NOT changed, because they are accurate rather than stale: - migration and coexistence prose in docs/forgejo-on-railiance01.md, docs/forge-source-of-truth-decision.md and the capability registry, where Gitea is the thing being migrated from - gitea-charts/gitea 12.5.0, the real Helm chart Forgejo deploys from - gitea-db, a running CNPG cluster, and the gitea- prefixed doc filenames in railiance-forge, which still exist under those names Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-11 23:08:52 +02:00
tegwick	668c54da05	Deploy coulomb-social:ea8dc12 app shell (Spaces + session details)	2026-08-11 02:34:16 +02:00
tegwick	55a6427509	Deploy coulomb-social:f5537d8 with id_token OIDC claims ... Fixes public Sign-in on app.coulomb.social when KeyCape /userinfo returns 401.	2026-08-10 08:56:29 +02:00
tegwick	3f3ffd279f	Use websecure-only ingress for coulomb-social HTTP-01 ... Leave port 80 free for cert-manager solvers (forgejo pattern) so ACME challenges are not contended by the app router.	2026-08-09 23:37:08 +02:00
tegwick	8eca75735d	Point coulomb-social Helm and ingress at app.coulomb.social ... Public parallel host; leave apex coulomb.social for Bubble until cutover.	2026-08-09 23:20:31 +02:00
tegwick	ca804ef148	Deploy coulomb-social image tag as string; pin 7067145 ... Helm --set-string for numeric git SHAs (InvalidImageName fix). Ingress entrypoints web+websecure; values pin first release tag.	2026-08-09 02:32:37 +02:00
tegwick	2ab6662142	Note apps-pg DB ready for coulomb-social deploy path ... Role coulomb_social and database coulomb_social_db are live on apps-pg.	2026-08-09 02:18:22 +02:00
tegwick	c79f07aadf	Add coulomb-social-env secret create/patch script ... Builds SECRET_KEY, optional URL-encoded DATABASE_URL from app DB credentials, and USER_ENGINE_PROXY_SECRET from user-engine-runtime. Never prints values; Makefile dry-run and apply targets.	2026-08-09 02:04:32 +02:00
tegwick	32610e9090	Add coulomb-social Helm chart and deploy targets ... Chart mirrors vergabe-teilnahme Django probe/secret pattern. Non-secret values pin KeyCape OIDC and user-engine URL; env Secret holds secrets. Makefile: dry-run, deploy, ingress, status, logs.	2026-08-09 02:00:13 +02:00
tegwick	dd1bd6cccc	Adopt Target Revenue Source License V1C1 (org-wide preliminary rollout) ... Maintainer decision, 2026-07-29: adopts TRSL V1C1 as this repo's preliminary governing license, per target-revenue's workplans/TREV-WP-0008-governance-and-pilot-rollout.md T05. Full specialist legal review is deferred until out of beta (target-revenue SCOPE.md §1). No Phase is yet declared for this repo. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-29 23:47:00 +02:00
tegwick	40ffa9db21	work records file added	2026-07-22 21:18:14 +02:00
custodian-sync	8ab448e30c	chore(consistency): sync task status from DB [auto] ... Updated by fix-consistency on 2026-07-22: - update .custodian-brief.md for railiance-apps	2026-07-22 20:34:52 +02:00
tegwick	4a06c0884a	RAILIANCE-WP-0016: finish unattended hybrid Option A backups ... Core in-cluster CronJobs with cnpg-option-a-backup image + NetworkPolicy; R01 activity-core schedule enabled; status healthy; evidence recorded.	2026-07-22 20:34:24 +02:00
custodian-sync	65e71884a9	chore(consistency): sync task status from DB [auto] ... Updated by fix-consistency on 2026-07-22: - update .custodian-brief.md for railiance-apps	2026-07-22 19:51:36 +02:00
tegwick	c202fbf7be	RAILIANCE-WP-0016: promote active; inventory and activity-core cutover prep ... Mark workplan active with T01/T02 done, document topology, extend status for activity-core mode, and wire Make targets to the platform multi-host backup CLI. T03 remains operator-blocked on ESO token.	2026-07-22 19:50:59 +02:00
tegwick	04626b6335	chore(consistency): write state-hub IDs into RAILIANCE-WP-0016 ... C-06 registration IDs from fix-consistency.	2026-07-22 19:36:36 +02:00
tegwick	7bc76dc0c6	docs: STATE.md assessment; propose RAILIANCE-WP-0016 activity-core backups ... Capture post-WP-0015 posture (workstation SPOF) and register a workplan to move unattended Option A + Forgejo backup automation to railiance01 via activity-core without a laptop control plane.	2026-07-22 19:35:25 +02:00
tegwick	1376b4f34c	RAILIANCE-WP-0015: use workstation cron; suspend in-cluster CronJobs ... Cluster egress blocks age installs (github + Alpine CDN). Declare workstation-cron schedule ConfigMap as the unattended path and keep Option A CronJobs suspended until a prebuilt image is available.	2026-07-22 18:06:06 +02:00
custodian-sync	cf742a0868	chore(consistency): sync task status from DB [auto] ... Updated by fix-consistency on 2026-07-22: - update .custodian-brief.md for railiance-apps	2026-07-22 18:01:10 +02:00
tegwick	6635fdc976	RAILIANCE-WP-0015: Option A CNPG logical backup coverage healthy ... Materialize offsite Secret from OpenBao, deploy per-cluster CronJobs, generalize multi-cluster logical backup + status health for Option A, seed encrypted uploads and restore-drill evidence; workplan finished.	2026-07-22 18:00:48 +02:00
custodian-sync	374ebed349	chore(consistency): sync task status from DB [auto] ... Updated by fix-consistency on 2026-07-22: - update .custodian-brief.md for railiance-apps	2026-07-22 17:53:57 +02:00
custodian-sync	b9c524a9c1	chore(consistency): sync task status from DB [auto] ... Updated by fix-consistency on 2026-07-22: - RAILIANCE-WP-0015-T04: progress → wait	2026-07-22 17:53:55 +02:00
custodian-sync	2968aee461	chore(consistency): sync task status from DB [auto] ... Updated by fix-consistency on 2026-07-22: - RAILIANCE-WP-0015-T03: progress → wait	2026-07-22 17:53:55 +02:00
custodian-sync	5859d2cf94	chore(consistency): sync task status from DB [auto] ... Updated by fix-consistency on 2026-07-22: - RAILIANCE-WP-0015-T02: progress → wait	2026-07-22 17:53:55 +02:00
tegwick	d5772d2a1a	RAILIANCE-WP-0015: activate workplan; close T01 offsite credentials ... CCR-2026-0004 / railiance-backup-offsite-lane is resolvable; mark T01 done and move T02–T04 into progress for Option A schedule implementation.	2026-07-22 17:53:35 +02:00
tegwick	b836dcecc2	docs: mark weekly Forgejo package prune as enabled ... Point retention table at ACTIVITY-WP-0020 closeout and live-tag protection.	2026-07-21 19:20:42 +02:00
tegwick	c9ed0637b3	chore(consistency): write state-hub IDs into RAILIANCE-WP-0015 [auto] ... Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-14 00:38:26 +02:00
custodian-sync	488a5d3445	chore(consistency): sync task status from DB [auto] ... Updated by fix-consistency on 2026-07-14: - update .custodian-brief.md for railiance-apps	2026-07-14 00:37:32 +02:00
tegwick	deef13e8a5	RAILIANCE-WP-0015: CNPG backup ScheduledBackup coverage followup ... Descoped out of RAIL-HO-WP-0005 T04/T09. Drives cnpg-backup-status degraded→healthy. Blocked on CCR-2026-0004 offsite credential provisioning (operator/OpenBao). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-07-14 00:36:54 +02:00
tegwick	a307041cac	docs(forgejo): document automated package prune retention policy ... Reference ACTIVITY-WP-0020 weekly prune lane and depth-3 retention.	2026-07-12 11:35:04 +02:00
custodian-sync	7d003a9d6c	chore(consistency): sync task status from DB [auto] ... Updated by fix-consistency on 2026-07-12: - update .custodian-brief.md for railiance-apps	2026-07-12 11:29:24 +02:00
tegwick	fd8537af7a	docs(backup): close RAILIANCE-WP-0013 S5 Phase 1 gate ... Update app-data-backup-restore-handoff and vergabe-teilnahme with backup and restore evidence references. Mark workplan finished and archive.	2026-07-12 11:29:05 +02:00
tegwick	9b0b988e20	docs(backup): record successful forgejo-backup run for WP-0013 T03 ... forgejo-dump-20260711T233637Z uploaded after chunk-copy and preflight fixes.	2026-07-12 10:53:01 +02:00
custodian-sync	96663283d2	chore(consistency): sync task status from DB [auto] ... Updated by fix-consistency on 2026-07-12: - update .custodian-brief.md for railiance-apps	2026-07-12 01:11:41 +02:00
custodian-sync	22dc41a25d	chore(consistency): sync task status from DB [auto] ... Updated by fix-consistency on 2026-07-12: - RAILIANCE-WP-0013-T05: progress → wait	2026-07-12 01:11:39 +02:00
custodian-sync	8c89e54464	chore(consistency): sync task status from DB [auto] ... Updated by fix-consistency on 2026-07-12: - RAILIANCE-WP-0013-T03: progress → wait	2026-07-12 01:11:38 +02:00
tegwick	dc65a3b9fd	feat(backup): apps-pg restore drill + close WP-0014 ... Add tools/apps-pg-restore-drill.sh and make target; T04 evidence for vergabe_db row-count gate. Archive finished RAILIANCE-WP-0014.	2026-07-12 01:09:49 +02:00
tegwick	a0cb579679	chore(vergabe): deploy tag 064d295 (Forgejo-only issue-core lock)	2026-07-12 01:02:38 +02:00
tegwick	745874c7a0	docs(wp-0014): close vergabe Forgejo deploy (dfbc13a) ... Image pushed to forgejo.coulomb.social and deployed on CoulombCore; health smoke passed. Retires Gitea image for vergabe-teilnahme.	2026-07-12 00:57:35 +02:00
tegwick	859d0051b3	docs(wp-0014): record Forgejo CI fix and deploy blocker	2026-07-12 00:45:56 +02:00
tegwick	115d7a4095	chore(vergabe): target Forgejo image tag dfbc13a for deploy ... Align production values with the CI fix commit that unblocks Forgejo container builds (uv sync --frozen).	2026-07-12 00:45:17 +02:00
tegwick	d207f69f25	chore: add check-vergabe-image phony targets	2026-07-12 00:34:21 +02:00
tegwick	e9f406da2a	feat(vergabe): deploy from Forgejo OCI registry only ... Switch helm values and Makefile image gates to forgejo.coulomb.social; retire gitea.coulomb.social for vergabe-teilnahme production pulls.	2026-07-12 00:32:32 +02:00