Updated by fix-consistency on 2026-06-05: - update .custodian-brief.md for railiance-apps
32 lines
1.3 KiB
Markdown
32 lines
1.3 KiB
Markdown
<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
|
|
# Custodian Brief — railiance-apps
|
|
|
|
**Domain:** railiance
|
|
**Last synced:** 2026-06-05 15:30 UTC
|
|
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
|
|
|
|
## Active Workstreams
|
|
|
|
### S5 app release readiness and scope alignment
|
|
Progress: 3/6 done | workstream_id: `685f1c18-33c0-400d-a2b1-e1dae0f27c3e`
|
|
|
|
**Open tasks:**
|
|
- · 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`
|
|
|
|
### App deployment improvements (lessons from RAILIANCE-WP-0002)
|
|
Progress: 6/7 done | workstream_id: `b61a9aca-4e43-4b3d-a48b-999e0fa842cf`
|
|
|
|
**Open tasks:**
|
|
- ! I03 — Publish `issue-core` to a Gitea Python package registry `f412b874`
|
|
*(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)
|
|
|
|
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.
|