coulomb/state-hub
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: update standalone state hub wiring

Browse Source
This commit is contained in:
Bernd Worsch
2026-05-17 20:01:21 +02:00
parent d444462de0
commit fdc395a600
23 changed files with 40 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
scripts/project_rules/session-protocol.template
View File

@@ -12,7 +12,7 @@ Then call the MCP tool for richer cross-domain context (skip if unreachable):
```
get_domain_summary("{DOMAIN}")
```
If the hub is offline: `cd ~/the-custodian/state-hub && make api`
If the hub is offline: `cd ~/state-hub && make api`
**Step 2 — Check inbox**
```
@@ -51,12 +51,12 @@ add_progress_event(summary="...", topic_id="{TOPIC_ID}", workstream_id="<uuid>")
If workplan files were modified, ensure the local copy is up to date first:
```bash
git -C <repo_path> pull --ff-only
cd ~/the-custodian/state-hub && make fix-consistency REPO={REPO_SLUG}
cd ~/state-hub && make fix-consistency REPO={REPO_SLUG}
```
For repos where implementation runs on a remote machine (e.g. CoulombCore),
use the combined target which pulls before fixing:
```bash
cd ~/the-custodian/state-hub && make fix-consistency-remote REPO={REPO_SLUG}
cd ~/state-hub && make fix-consistency-remote REPO={REPO_SLUG}
```
**C-15** (DB task ahead of file) is normal in multi-machine workflows — writeback
will sync the file to match DB. **C-16** (repo behind remote) blocks all writes