Router status fails: SIDE_LANES declares muse → Muse but agents/Muse.md is not in the release

Open Beginner friendly
  • Is something wrong?
#2,616 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 9 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
bun, typescript
Domain
backend-api-design, testing

Research direction

Start with hooks/lib/lane-rules.ts and the shipped agents roster; reproduce the failure with bun LIFEOS/ROUTER/Router.ts status. The issue describes a roster consistency test using sideLaneViolations(roster(agentsDir)); inspect its existing test location and verify every declared side lane resolves to a shipped agent. Done when the status check passes with the chosen lane behavior and the roster test passes.

Written by the indexing model from the issue text.

Description

Version: 8.761.0

hooks/lib/lane-rules.ts declares SIDE_LANES.muse = { agent: "Muse", ... }, but no agents/Muse.md ships in the 8.761.0 payload (nor on current main as of this report). On any install without that agent file, bun LIFEOS/ROUTER/Router.ts status reports ✗ side lane: muse → Muse: no such agent or no lane and the status line stays failed.

Locally we removed the muse entry from SIDE_LANES (the lane is never auto-routed and needs a Muse Code subscription we don't have) and added a test that every declared side lane resolves to an agent in the shipped roster (sideLaneViolations(roster(agentsDir)) is empty). Shipping agents/Muse.md, or declaring the lane only when the agent file exists, would fix it upstream.

Dominant language
TypeScript
Stars
19.7k
Forks
2.5k
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from danielmiessler/LifeOS

All issues in danielmiessler/LifeOS

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.