issue-core/.custodian-brief.md
custodian-sync faf2fbc66b
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s
chore(consistency): sync task status from DB [auto]
Updated by fix-consistency on 2026-08-19:
  - update .custodian-brief.md for issue-core
2026-08-19 20:15:48 +02:00

35 lines
1.2 KiB
Markdown

<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
# Custodian Brief — issue-core
**Domain:** infotech
**Last synced:** 2026-08-19 18:15 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Active Workstreams
### rapp-issue-core: move the runtime off CoulombCore onto railiance01
Progress: 2/7 done | workplan_id: `a2bc717a-64cf-45fa-8a9d-59d3bc9e96c7`
**Open tasks:**
- · Tasks `e0427de0`
- · Tasks `d6e5e2ac`
- · Tasks `21974fbd`
- · Tasks `3fdbd9ab`
- · Tasks `668e37dc`
### Forgejo-only forge + projection boundary (not ops queue)
Progress: 0/4 done | workplan_id: `0b75b7ae-c8e3-4737-8fa8-2f60a12e6d14`
**Open tasks:**
- · T01 — Terminology sweep: Gitea → Forgejo (product language) `e2148c3f`
- · T02 — INTENT/SCOPE: ops queue non-goal `78247ad9`
- · T03 — Connector docs: projection path only `41bd7596`
- · T04 — Coordinate rein-aharness intake docs `8f217196`
---
## MCP Orientation (when available)
If the state-hub MCP server is reachable, call:
`get_domain_summary("infotech")`
This provides richer cross-domain context.
If the MCP call fails, use this file as your orientation source.