Files
railiance-apps/.custodian-brief.md
tegwick 3e2eae6b14 chore(consistency): sync task status from DB [auto]
Updated by fix-consistency on 2026-06-05:
  - update .custodian-brief.md for railiance-apps
2026-06-05 17:56:21 +02:00

24 lines
1003 B
Markdown

<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
# Custodian Brief — railiance-apps
**Domain:** railiance
**Last synced:** 2026-06-05 15:56 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Active Workstreams
### 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.