railiance-apps/workplans/archived/260710-RAPPS-WP-0011-inbox-suggestions-core-hub-cnpg-backup.md
codex d03edc946c
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
fix(workplans): migrate archived workplans off the retired RAILIANCE-WP prefix
Completes the migration begun on 2026-08-25, which covered active workplans
only. The archived copies kept their historical identifiers, and three
repositories shared one number space — so their task identifiers collided,
blocking task-level projection reset for those workplans.

Numbering continues each repository's active sequence rather than restarting,
so no identifier is reused. Projection UUIDs are re-derived from the new
canonical ids.

Refs CUST-WP-0068, STATE-WP-0083-T06

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
2026-08-26 08:05:43 +02:00

2.7 KiB

id type title domain repo status owner topic_slug created updated state_hub_workstream_id
RAPPS-WP-0011 workplan Inbox suggestions — Core Hub S5 release and CNPG backup observability financials railiance-apps finished codex railiance 2026-07-10 2026-07-10 5b9f0df2-0af1-57bd-91e1-eec1fd777553

Inbox suggestions — Core Hub S5 release and CNPG backup observability

Sources:

  • State Hub inbox a1957cce (HIGH): no CNPG backups on railiance01 production DB clusters; evidence the-custodian/docs/evidence/vergabe-teilnahme-delivery-lane-20260710.json.
  • State Hub inbox 3ced85c7: Core Hub release ownership follow-up from CUST-WP-0052; cite the-custodian/docs/core-hub-helixforge-build-alignment.md and core-hub/docs/deployment/staging-profile.md.

Core Hub Helm chart and production values

id: RAPPS-WP-0011-T01
status: done
priority: high
state_hub_task_id: "af1caa40-40dc-51ff-aa74-dd45c65de5cf"

Promote the temporary core-hub/k8s/railiance-production/ profile into charts/core-hub/ with non-secret production and staging values under helm/. Secrets remain operator-owned (core-hub-prod-env, core-hub-staging-env).

Makefile release targets and smoke gate

id: RAPPS-WP-0011-T02
status: done
priority: high
state_hub_task_id: "52206806-c93a-5866-91d9-69ff22ed1e15"

Add core-hub-dry-run, core-hub-server-dry-run, core-hub-deploy, core-hub-status, core-hub-migrate, core-hub-smoke, and staging counterparts. Require explicit CORE_HUB_IMAGE_TAG=<sha> for production deploys.

Operator runbook for Core Hub on railiance01

id: RAPPS-WP-0011-T03
status: done
priority: medium
state_hub_task_id: "19b9322f-466d-5f1d-ab68-cc0ca74ead53"

Document the S5 release path in docs/core-hub-on-railiance01.md, including migration boundary, ingress cutover notes, rollback, and links to Core Hub service-repo smokes.

CNPG backup posture observability

id: RAPPS-WP-0011-T04
status: done
priority: high
state_hub_task_id: "b26183dc-9aca-5a66-a349-eb82c0d8ebd4"

Add make cnpg-backup-status and tools/cnpg-backup-status.sh to report backup spec and ScheduledBackup coverage for apps-pg, forgejo-db, net-kingdom-pg, and state-hub-db. Include operator-ready manifest templates for barman ObjectStore and ScheduledBackup wiring once platform supplies object-store credentials.

Update app data backup handoff with delivery-lane evidence

id: RAPPS-WP-0011-T05
status: done
priority: medium
state_hub_task_id: "cd515d43-f8e2-5de7-b179-e40cb82d71cc"

Refresh docs/app-data-backup-restore-handoff.md with the 2026-07-10 custodian conformance snapshot, the cluster inventory, and the platform coordination path for backup implementation.