You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
STOP: agent direction reset — trios-server is Rust on :9005, NOT TypeScript mcp-bridge #18
Agent worked on trios-mcp-bridge (TypeScript, port 9200) — this is WRONG PATH.
The Truth (SSOT)
CORRECT ARCHITECTURE:
trios-server (Rust, Axum, port 9005) ← THIS IS THE SERVER
└── crates/trios-server/src/tools.rs ← 7 tools already implemented
WRONG PATH (do not continue):
trios-mcp-bridge (TypeScript, port 9200) ← NOT IN THIS REPO, NOT GOLD
Why
CLAUDE.md Law L1: NO TypeScript in trios — all automation is Rust binaries
CLAUDE.md Law L5: port 9005 is trios-server — not 9200
trios is a Rust workspace (Cargo.toml) — no package.json, no bun
crates/trios-server/src/tools.rs already has 7 tools in Rust
trios/
├── crates/trios-server/src/ ← Rust only
├── crates/trios-git/src/ ← Rust only
├── crates/trios-gb/src/ ← Rust only
├── crates/trios-core/src/ ← Rust only
└── .trinity/experience/ ← seal logs only
Files to NEVER create
❌ any .ts files
❌ any .js files
❌ any package.json
❌ any .sh files
❌ trios-mcp-bridge/ directory
Activity
gHashTag commentedon Apr 18, 2026
✅ Architecture confirmed:
crates/trios-server/src/tools.rscargo test→ 14 passed, 0 failedcurl localhost:9005/mcp/tools/list→ 7 toolsCloses #18. Next: RING 2.
fix(mcp): register git_unstage_files in TOOL_DEFINITIONS