fix: CLAUDE.md @includes pointed at stale .muse/agent.md path
Both includes (@../.muse/agent.md for the workspace-shared rules, @.muse/agent.md for musehub-specific rules) referenced a path that no longer exists -- the canonical agent-config source moved to .museagent.md (workspace root and per-repo) some time ago, per `muse agent-config status`, but this file's includes were never updated. Since Claude resolves @includes silently (no error on a missing target), every Claude Code session rooted at ~/ecosystem/musehub -- including this one -- has been getting zero content from either include: no HARD RULE sections, no commit conventions, no localhost-container restart guidance, nothing.
Fixed both paths to .museagent.md. Confirmed via `muse agent-config status --json`: claude adapter now reports in_sync=true.
Discovered while auditing whether musehub#182/#185's new muse-dev object-store safety guardrail is actually visible to future agents (see matching fix in the ~/ecosystem workspace repo, commit 81cc1902).
Co-Authored-By: Claude Sonnet 5 <[email protected]>
Semantic Changes
Files Changed
~1
1072 in snapshot
0 comments
muse hub commit comment sha256:ce798e919c1ffbea9d03dc8dcd339ad549e170ce7f453c9b0fc46a0b044a1f05 --body "your comment"
No comments yet. Be the first to start the discussion.