docs: Project Direction for the toolboxmd workspace fork

MISSION.md

@@ -0,0 +1,12 @@
+# Mission
+
+The toolboxmd fork of T3 Code is the user's working surface. It stays a thin,
+rebasable layer on upstream `pingdotgg/t3code`: features live in new files and
+packages, upstream files carry the smallest possible edits, and generic
+extension points are offered upstream so the patch set shrinks over time.
+
+On T3's core the fork adds what the user's tools need instead of rebuilding
+harness plumbing: Model Router jobs run as T3 threads, visible and reachable
+from the thread that started them; OpenBot becomes a mode switched in the UI,
+bringing Bots, Channels and the Computer; further capabilities such as VMs
+follow. AgentsMD plugins extend the fork rather than competing with it.

OBJECTIVE.md

@@ -0,0 +1,17 @@
+# Objective
+
+Make the fork maintainable and bring Model Router into it.
+
+The Objective is complete when:
+
+- A documented rebase routine keeps the fork's changes as a small commit
+  stack on upstream `main`, with CI, and one upstream update has been
+  absorbed through it.
+- Model Router jobs run as T3 threads: hidden from the sidebar, shown and
+  openable from the parent thread's Agents panel, messageable there, and
+  continued after a server restart where the provider supports it.
+- An OpenBot-on-T3 spike measures the Computer as a right-panel tab and a Bot
+  as a thread with a persona, with its upstream edit count.
+
+The OpenBot mode UI, VMs, mobile builds and multi-machine operation remain
+outside this Objective.

VISION.md

@@ -0,0 +1,5 @@
+# Vision
+
+One workspace where a person does all their coding, project handling and work
+with bots: every harness, every machine and every agent in one place, built on
+the open T3 Code core.