dexter/BTerminal
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

chore: rebase hib_changes onto dexter_changes and update migration TODOs

Browse source
This commit is contained in:
Hibryda 2026-03-13 02:40:42 +01:00
parent 719496853e
commit 5d0d5c5f07
2 changed files with 4 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

5
TODO.md
View file

@ -3,8 +3,9 @@
## Active
### Migration to agent-orchestrator
- [ ] **Migrate to agent-orchestrator repo** -- Tribunal plan (78% confidence): cherry-pick 7 BTerminal-unique commits onto hib_changes, rebase onto dexter_changes (55ba8d0). Pre-flight: topology verification, content dedup, CLAUDE.md Commit Zero. Decide: do v1 bterminal.py features belong in agent-orchestrator? Full report: .tribunal/tribunal-report.md
- [ ] **Integrate dexter_changes features** -- 13 commits: Aider provider, splash screen, provider/model unification, Tier 2 btmsg access, auto-wake on btmsg. After cherry-pick + rebase onto hib_changes.
- [ ] **Review Dexter's 13 feature commits** -- hib_changes rebased onto dexter_changes (55ba8d0). Need to review: Aider provider, splash screen, provider/model unification, Tier 2 btmsg access, auto-wake on btmsg. Then push hib_changes and start working from agent-orchestrator repo.
- [ ] **CLAUDE.md Commit Zero** -- Update agent-orchestrator's CLAUDE.md to reflect rebrand + new features. Update docs/ accordingly.
- [ ] **Switch primary development to agent-orchestrator** -- After review + CLAUDE.md update, develop on hib_changes in agent-orchestrator. BTerminal repo stays for v1 production only.
### v3.1 Remaining
- [ ] **Multi-machine real-world testing** -- TLS added to relay. Needs real 2-machine test. Multi-machine UI not surfaced in v3, code exists in bridges/stores only.

2
agent-orchestrator

@ -1 +1 @@
Subproject commit 4fee567dd9b59b86108079331ee472503d056626
Subproject commit 55ba8d0969b4c9e34e47fe621ea4812528441365