Skip to content

docs: begin non-turn-based surfaces protocol planning - #257

Draft
omegent-app[bot] wants to merge 19 commits into
fork/changesfrom
t3code/define-ntbs-object-mapping
Draft

docs: begin non-turn-based surfaces protocol planning#257
omegent-app[bot] wants to merge 19 commits into
fork/changesfrom
t3code/define-ntbs-object-mapping

Conversation

@omegent-app

@omegent-app omegent-app Bot commented Jul 31, 2026

Copy link
Copy Markdown

Summary

  • frame the shared problem for non-turn-based surfaces
  • record the intended event-log and adapter boundaries without choosing protocol details yet
  • establish an incremental decision log for the ongoing design conversation

Testing

  • vp check
  • ELECTRON_SKIP_BINARY_DOWNLOAD=1 vp run -r --cache --log labeled typecheck

github-actions Bot and others added 19 commits July 31, 2026 13:38
Woke-status candidate emits unsnooze alongside unsettled when turn activity
starts; update settled decider expectations to match.
Fork platform layer in one commit: agent/stack docs, pr-stack and overlay
ownership, restack/compose/fork-stack scripts, Fork CI and compose
workflows, and root workspace/lockfile tooling.
Shared schemas for orchestration, RPC, settings, and related protocol
surfaces used by server and clients.
Runtime helpers, product-family helpers, and oxlint plugin rules shared
across the monorepo.
Client runtime state, connection diagnostics, and list helpers shared by
web and mobile.
Supporting packages that diverge from upstream for the fork product.
Server product layer: work-item bridges, queue/recovery, VCS drivers,
single-source RPC authorization scopes, worktree bootstrap, and related
tests. Includes thread.context.compact contracts wiring on the server.
Web UI product deltas including lists, composer, usage gauges, file/content
search, and thread-loading send guards.
Mobile shell product, list modes, composer queue API, and scroll behavior
after rolling back experimental feed layout work.
Desktop packaging scripts/config and backend ownership behavior for the
fork desktop shell.
ElectronApp no longer exposes requestSingleInstanceLock (Clerk bridge owns
the single-instance lock). Remove it from DesktopUpdates test stubs so
desktop typecheck is green on fork/changes.
…ests

Repair HomeHeader ternary/stageLabel, HomeScreen bottom-toolbar clearance,
and drop obsolete requestSingleInstanceLock mocks so Fork CI Check stays green
on fork/changes after the history rewrite.
The unit project reuses workers with isolate:false, so mocking useAssetUrl
and react hooks never sticks when assetUrls is already in the module graph.
Move ProjectFavicon.test.tsx into unit-isolated (same as other React mock
tests) and keep dual-path assetUrl mocks for path resolution.
Compose is an integration rebuild, not a product-layer gate. Drop the
push trigger so force-pushes, deploy-key tip updates, and overlay
auto-rebase no longer attach "Compose and dispatch integration CI" to
permanent fork/* draft PRs or look like layer failures.

Compose now fires only when a PR merges into fork/changes or a
registered overlay base, or via workflow_dispatch. Full Tim/candidates
upstream restacks stay manual/local. Document that layer status is
Fork CI (Check/Test/Mobile/Release Smoke) only.
Make the product default for draft threads match the preferred worktree
workflow: New worktree with Start from origin enabled. Mobile falls back
to the shared server defaults when config is still loading.

Co-authored-by: omegent-app[bot] <306514130+omegent-app[bot]@users.noreply.github.com>
Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
Upstream ci.yml uses blacksmith-* runners this fork does not provide, so
Tim/candidates permanent PRs queued forever. Keep that workflow disabled
and cover stack bases with Fork CI (dispatch for fork/tim → main PR;
PR bases for fork/tim and fork/candidates).
Sit fork/base between upstream main and Tim so Blacksmith-free runners
and Fork CI live once under all provenance layers. Register PR #255 in
pr-stack; retarget Tim to base. Drop the need for tip CI hacks on
tim/candidates.
.vscode/tasks.json only builds the t3-code extension; it belongs with
.vscode/launch.json on fork/vscode, not on shared fork/changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants