coulomb/railiance-apps
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(consistency): sync task status from DB [auto]

Browse Source 
Updated by fix-consistency on 2026-06-04:
  - update .custodian-brief.md for railiance-apps
This commit is contained in:
Bernd Worsch
2026-06-04 09:40:30 +02:00
parent 6bfbabe9c2
commit c7292f02ce
1 changed files with 13 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
.custodian-brief.md
View File

@@ -2,17 +2,28 @@
# Custodian Brief — railiance-apps # Custodian Brief — railiance-apps
**Domain:** railiance **Domain:** railiance
**Last synced:** 2026-05-22 20:24 UTC **Last synced:** 2026-06-04 07:40 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)* **State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Active Workstreams ## Active Workstreams
### S5 app release readiness and scope alignment
Progress: 0/6 done | workstream_id: `685f1c18-33c0-400d-a2b1-e1dae0f27c3e`
**Open tasks:**
- · T01 - Write `INTENT.md` `af15d202`
- · T02 - Normalize app image promotion and package registry docs `f8f63edb`
- · T03 - Create a reusable S5 app onboarding checklist `4eab93a9`
- · T04 - Define app data backup and restore handoffs `299d9623`
- · T05 - Make manifest dry-run workflow prerequisites explicit `6cf0e662`
- · T06 - Define Gitea package registry storage and retention posture `382ba252`
### App deployment improvements (lessons from RAILIANCE-WP-0002) ### App deployment improvements (lessons from RAILIANCE-WP-0002)
Progress: 6/7 done | workstream_id: `b61a9aca-4e43-4b3d-a48b-999e0fa842cf` Progress: 6/7 done | workstream_id: `b61a9aca-4e43-4b3d-a48b-999e0fa842cf`
**Open tasks:** **Open tasks:**
- ! I03 — Publish `issue-core` to a Gitea Python package registry `f412b874` - ! I03 — Publish `issue-core` to a Gitea Python package registry `f412b874`
*(blocked: railiance-apps enabled and documented the Gitea PyPI registry; remaining work requires publishing issue-core from its repo and switching vergabe-teilnahme away from the local path dependency.)* *(wait: issue-core package build and vergabe-teilnahme registry dependency are prepared; final unblock requires a Gitea package username/token to publish issue-core==0.2.0 and regenerate vergabe-teilnahme/uv.lock from the Gitea PyPI registry.)*
--- ---
## MCP Orientation (when available) ## MCP Orientation (when available)