Files
railiance-infra/.custodian-brief.md
tegwick 5c69f01dc5 chore(consistency): sync task status from DB [auto]
Updated by fix-consistency on 2026-05-17:
  - update .custodian-brief.md for railiance-hosts
2026-05-17 14:50:19 +02:00

41 lines
1.5 KiB
Markdown

<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
# Custodian Brief — railiance-hosts
**Domain:** railiance
**Last synced:** 2026-05-17 12:50 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Current Goal
Secure Single-Server Bootstrap at HostEurope
## Active Workstreams
### Forgejo Production Migration on railiance01
Progress: 0/12 done | workstream_id: `84e17675-0d15-4268-a8bd-540124d37018`
**Open tasks:**
- · T01 — Inventory current Gitea functionality and migration requirements `cf59d171`
- · T02 — Resolve Forgejo production design decisions `f88115bf`
- · T03 — Build forgejo-railiance-probe `b516018a`
- · T04 — Define Forgejo platform services `28b351fe`
- · T05 — Define production Forgejo application deployment `11540ba4`
- · T06 — Implement usable email recovery cycle `417faa4d`
- · T07 — Enable and harden package registry base `9578f672`
- … and 5 more open tasks
### Railiance Production Readiness — Automated, Reproducible Stack
Progress: 8/10 done | workstream_id: `cee078e9-b18c-4f84-8a8a-6f27c2f9f407`
**Open tasks:**
- · T09 — Deploy state-hub to cluster (S5) `d2afe78a`
- · T10 — Deploy activity-core to cluster (S5) `34d73215`
---
## MCP Orientation (when available)
If the state-hub MCP server is reachable, call:
`get_domain_summary("railiance")`
This provides richer cross-domain context.
If the MCP call fails, use this file as your orientation source.