Current operating decision
The supported application path isapps/web on Next.js, the satellite apps
(Next.js today, moving per app to native TanStack Start + Void + Vite+ on
Cloudflare Workers), shared TypeScript packages, and their owning hosted
services. The Docker cron runner and apps/tanstack-web are retired; do not
revive them. Docker setup and apps/backend (Rust) are not in use until
explicitly resumed. They are not prerequisites for documentation, routine
development, focused validation, or release delivery.
This applies to the live app surfaces, developer onboarding, and incident
runbooks. Retained files, Compose services, scripts, dashboards, route manifests,
and future-cutover procedures are historical or resumption references. Their
presence does not establish an active service. An explicitly isolated experiment
or separately approved resumption can use those artifacts; it must not silently
become a prerequisite for the active path.
TanStack Query remains in use for client fetching/caching. Per-app
TanStack Start on Cloudflare Workers is the active target for every web app
except apps/web; it is unrelated to the retired apps/tanstack-web tree,
whose source refreshes, tests, dependency updates and CI stay disabled. Shared
contracts still belong in reusable packages; do not require updates to the
retired trees for a live change.
Each app migrates under the native Start migration runbook:
one integration writer per app, next/* only through
@tuturuuu/start-bridge, basePath readiness for
both its subdomain and tuturuuu.com/<app>, and exact-commit CI, sealed
emitted-Worker acceptance and the app’s reviewed hosted cutover acceptance.
Wave-1 uses a private production smoke before routing, then immediate signed-in
production acceptance and a 30–60 minute watch; hosted staging is not a flip gate. Current
hosting (Vercel or Next.js/OpenNext Workers) stays canonical until that app’s
explicit cutover PR. See
Oxc and Cloudflare adoption.
Wave-1 production publication hold
Calendar frontend is admitted for route-free production preparation inproductionPublicationPolicy in tuturuuu.ci.ts; Meet, Mail and Apps remain
held for wave-1 cutover. The production planner reports
Held with that reason and selects neither their native nor legacy publishers,
including manual and package recovery selection. Native CI validation stays enabled.
Meet’s direct production job also checks the same policy before publication.
A production sync therefore retains the currently deployed Meet frontend and realtime
Worker versions and the existing Calendar/Mail/Apps Vercel deployments. Other apps
and central API suppliers retain their normal production behavior; the hold is not
an assertion of compatibility with newly published suppliers. Vercel Git deployment
stays disabled; do not change framework, domains, bindings or scheduler ownership.
See the wave-1 cutover runbook.
Runtime map
Wave-1 native staging publishers
The Meet, Calendar, Mail and Apps Start/Void source and scoped native CI are active. This does not reviveapps/tanstack-web, resume the Rust/Docker stack, or
authorize canonical cutover.
Calendar, Mail and Apps have separately sealed native staging/production profiles.
Calendar has a separately gated private production publisher, which never attaches
routes. Other wave-1 apps remain held. Only owner-provisioned, explicitly enabled
staging can publish from trusted main runs; no workflow creates provider resources or
changes DNS as setup. The native publisher runbook
records exact identities, secret names, resource continuity, archive/runtime gates,
stop control, rollback receipts and remaining hosted acceptance. Meet’s off-canonical
profile is defined separately and has no automated staging publisher here.
Drive staging candidate
apps/drive has an additive Start/RSC bridge candidate. Its current Next app
continues to own production. void.config.ts defines the route-free
staging profile with workers_dev: false; only the Drive staging host is
admitted at the Worker root. No DNS, custom domain,
production route, publisher or infrastructure provisioning is part of this candidate.
The candidate uses the staging Supabase project pinned in supabase-staging.yaml,
forwards storage to the central staging API, and refuses missing or mismatched
runtime origins before loading routes. The Vite config also rejects non-staging
build origins. Supply only the staging publishable key and staging server secrets;
never reuse production credentials. Candidate response cookies stay host-only,
with Secure and HSTS. Outgoing Domain cookies are rejected, including prefixed cookies. Global
Supabase cookie configuration remains deferred to the issuer migration. Staging
responses are private and unindexable. English and Vietnamese
routes, Drive session audience and central API ownership remain unchanged.
Storage still uses the existing central APIs, path guards and storage RLS from
#6879. No candidate-specific storage grants, bucket changes, service-role bypasses
or migrations are introduced. Focused regression tests live in
apps/drive/src/start-candidate and the Supabase cookie adapter tests.
Before cutover, require exact-commit CI and native build acceptance, independent
security review, emitted Worker and browser acceptance, central staging auth/API
availability, and an explicit promotion/rollback review. A separately authorized
staging deploy must verify cross-app login, refresh/logout and cookie deletion,
wrong-app/expired sessions, bilingual navigation, upload/list/download/share,
consent and private/cross-workspace storage denials against the staging database.
Unit fixtures do not establish hosted session or storage RLS acceptance. Keep
Wrangler for Worker runtime checks until cf CLI operation parity is verified.
Hosted scheduler map
New schedules go to Cloudflare; the background work inventory
lists every remaining legacy owner and its migration target.
The Cloudflare Cron Control guide
explains the idle skip, requeue RPC, pending-batch check, and delivery token.
Calendar’s Infrastructure gateway authenticates the scheduler and uses its
configured credential to reach Calendar. It must not be bypassed by adding a
second direct Calendar schedule.
vercel: false in the old Web cron catalog excludes that entry from Web’s
Vercel scheduler. It does not mean the retired Docker runner will execute
it. A route or enabled source configuration is not proof of an active schedule.
If a job appears only in retained Docker configuration, identify its hosted
owner explicitly before calling it active. Do not activate a replacement or
change production schedules merely to resolve documentation ambiguity.
Diagnose missed work without Docker
- Identify the owning scheduler declaration and deployed revision.
- Inspect the hosted invocation result, authentication failure, timeout, and retry behavior for the relevant bounded time window.
- Trace the processor/gateway response and terminal domain state. For Calendar, confirm a fresh provider-sync timestamp with all clients closed. For notifications, confirm claimed/terminal delivery state rather than merely a scheduled invocation.
- Use an authorized, scoped manual processor recovery only when necessary; retain deduplication and recipient/workspace rules.
- Report missing deployment or scheduler evidence separately from source correctness.
tmp/docker-web/cron/status.json, old runner heartbeats, and queued local
Docker recovery requests are not health signals for these hosted schedulers.
Retained tooling may still contain runner/watchdog code. The standard Docker
commands, Docker setup CI, Docker-backed E2E jobs, inactive implementation test
suites, and migration refresh commands are disabled. This does not delete the
retained files or cancel already-running external jobs.
Regression and maintenance evidence
node --test scripts/ci/paused-migration-workflows.test.js guards the Docker setup and migration pause, including manual workflow jobs. scripts/docs-audit.test.js guards the active-runtime decision,
links, navigation, and reproducible documentation/SEO inventories. Hosted job
configuration and actual execution evidence remain necessary for operational
claims. Without Docker gives the
minimal development path.
Update and test pause until further notice
Default Node script-test discovery excludes inactive Docker/Rust/TanStack implementation suites while retaining tests that verify the pause. Shared Next.js unit tests, type checks, lint, and app builds stay active. The old Docker-backed E2E workflow is paused, so it no longer establishes browser integration proof. Direct Playwright commands can target an already prepared, safe local Next.js environment without starting Docker; their seeded database requirements still apply. A hosted build is not a replacement for that missing integration evidence.bun update-all targets maintained workspace names explicitly. Legacy shell
and batch entrypoints delegate to the same updater. Renovate ignores inactive
app manifests and Docker files; broad lockfile maintenance is disabled to avoid
refreshing retained dependencies. Shared lockfile resolutions can still reflect
active package changes and must be reviewed separately from paused manifests.
Generated documentation inventories do not refresh Rust/TanStack source or
versions. Existing migration runbooks remain retained reference material.
Resumption requires an explicit instruction and a coordinated change to the
command guards, test discovery, CI job/switchboard gates, dependency policy,
docs inventory, and operating docs. Do not selectively re-enable one gate and
assume the rest of the runtime is maintained.
Release Please excludes the inactive TanStack Start package from release generation;
its historical manifest version remains frozen. Renovate also ignores the inactive
runtime and Docker workflow files, in addition to the paused source/Dockerfiles.
Policy tests guard these exclusions. Do not reactivate them indirectly during
ordinary active-package release maintenance.
The only Docker CI exception is the trusted-main, self-hosted
e2e-smoke-report-only.yaml Web browser workflow (authorized 2026-10-28).
Its scoped launcher enforces admission, per-run identities and owned cleanup;
the general paused commands and existing disabled jobs remain paused, including
Rust, TanStack and the cron runner. See the GitHub Actions runbook’s
Report-only Web E2E
section for runtime bounds, host-lock recovery and report-only acceptance.