The repo record moved from topic "custodian" (the register default) to "helix-forge", where these repos belong: they are one loop around HelixForge, and a query for its work should return the loop intact. rmgr sync updates the hub but not the topic id embedded in these files, so the orientation commands here were still querying the old topic. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0172sgCZEEDJcnQmr4SGDvKa Assistant: claude-code Assistant-Model: opus Assistant-Process: 1361245@bnt-lap001 Assistant-Session: b3b428ef-f3e6-4688-b091-01f71461d66a
This commit is contained in:
parent
c32baf548a
commit
f1dabd48bd
2 changed files with 66 additions and 60 deletions
|
|
@ -6,7 +6,7 @@
|
|||
|
||||
**Domain:** infotech
|
||||
**Repo slug:** fluid-core
|
||||
**Topic ID:** `cee7bedf-2b48-46ef-8601-006474f2ad7a`
|
||||
**Topic ID:** `f39fa2a3-c491-414c-a91b-b4c5fcc6139c`
|
||||
**Workplan prefix:** `FLUID-WP-`
|
||||
|
||||
---
|
||||
|
|
@ -44,7 +44,7 @@ with `make -C ~/state-hub configure-codex WITH_MCP=1`.
|
|||
cat .custodian-brief.md
|
||||
|
||||
# Active workplans for this domain
|
||||
curl -s "http://127.0.0.1:8000/workplans/?topic_id=cee7bedf-2b48-46ef-8601-006474f2ad7a&status=active" \
|
||||
curl -s "http://127.0.0.1:8000/workplans/?topic_id=f39fa2a3-c491-414c-a91b-b4c5fcc6139c&status=active" \
|
||||
| python3 -m json.tool
|
||||
|
||||
# Check inbox
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue