Dai Ha
bc13b8e92c
Two leads now work as peers rather than one primary plus workers. The arc:
CB-530/531 lead identity: `leaders:` names panes, `leadScan:` discovers them by
tab label (LeadTabScanner, TTL-cached, worker spaces excluded).
CB-532 leads can message each other AND be answered. Principal.leader now
carries its terminal, so ownsSession() can be true for a lead; the
"and you must be a worker" conjunct beside it protected nothing.
Retires `primary:` — reply nudges follow the delegating lead, a
binding recorded at bridge_send where both halves are known.
CB-533 ClaudeCodeLauncher passes --model. argv is usually a wrapper
(`ccs <profile>`) that re-exports its own model family, so
ANTHROPIC_MODEL alone was silently overruled.
CB-534 a lead is deliverable. The CB-113 readiness gate only opened for
terminals in WorkerPresence, which only workers ever enter, so every
lead->lead send waited out the ~60s grace and failed having never
been typed. The gate guards a *spawned* peer's boot window; a lead
is never spawned.
CB-535 bridge_list returns `leads` alongside `workers`, with `self` on the
caller's row. An empty worker roster no longer reads as "no peers".
CB-536 CLAUDE.md: lead<->lead is coordinate-only, never sideways delegation.
Propagated byte-identically to wiki/7-Use-Cases.md.
MIXED PROVENANCE — recorded deliberately rather than hidden. This tree also carries
in-progress CB-537 (context separation) authored by the peer lead gpt-sol-5.6 and
its worker: Capability.CONTEXT_RESET, SessionManager.clearAfterTurn, and the
Injector/TurnListener/CompletionResolver/launcher changes around it. That work was
done in this shared working tree rather than a worktree, and is entangled with the
above in BridgedConfig.java, Bridged.java and ClaudeCodeLauncher.java, so neither
lead could stage its own half without sweeping in the other's. Committing the whole
green state is the honest resolution; the peer branches from here.
Note for whoever picks CB-537 up: the design in this commit is SUPERSEDED. Both
leads agreed to replace the global `clearAfterTurn` boolean with per-delivery
policy (inherit|fresh|thread) applied PRE-delivery, because a post-turn reset races
by construction — Injector.onStatus clears awaitingCompletion and dequeues the next
message in the same tick. `fresh` is also a correctness guarantee, so an adapter
without a reset capability must refuse it rather than log a no-op.
mvn clean install: Tests run: 464, Failures: 0, Errors: 0, Skipped: 0. BUILD SUCCESS.
35 lines
714 B
JSON
35 lines
714 B
JSON
{
|
|
"$schema": "https://opencode.ai/config.json",
|
|
"instructions": [
|
|
"CLAUDE.md"
|
|
],
|
|
"mcp": {
|
|
"bridged": {
|
|
"type": "remote",
|
|
"url": "http://127.0.0.1:8765/mcp",
|
|
"enabled": true
|
|
},
|
|
"context7": {
|
|
"type": "remote",
|
|
"url": "https://ct7.ltms.dev/mcp",
|
|
"enabled": true,
|
|
"headers": {
|
|
"Authorization": "Bearer {file:.secrets/context7-token}"
|
|
}
|
|
},
|
|
"gitea": {
|
|
"type": "local",
|
|
"command": [
|
|
"gitea-mcp",
|
|
"-t",
|
|
"stdio"
|
|
],
|
|
"enabled": true,
|
|
"environment": {
|
|
"GITEA_ACCESS_TOKEN": "{file:.secrets/gitea-token}",
|
|
"GITEA_HOST": "{file:.secrets/gitea-host}"
|
|
}
|
|
}
|
|
}
|
|
}
|