docs(tech-specs): worker-compose tech pack + interactive deck#1963
Draft
guibeira wants to merge 3 commits into
Draft
docs(tech-specs): worker-compose tech pack + interactive deck#1963guibeira wants to merge 3 commits into
guibeira wants to merge 3 commits into
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Proposes the compose daemon v1 contracts as a tech spec pack (tech-specs/2026-07-14-worker-compose): compose-file schema, scripts (pre_start / run / post_run), runtime namespaces, daemon-fed configuration, the standardized worker CLI/env contract, and lifecycle (readiness, cascading failure, optimistic trigger buffer). Ships the paired interactive deck (website/presentations/ 2026-07-14-worker-compose): 11 slides plus a crash-restart deep dive, built entirely from registry components. Renders at /roadmap/ once live.
post_start becomes post_run: it fires once after the run process exits (down, post-ready crash, or up rollback), is never awaited, and failure is a warning. There is no post-readiness hook in v1. Trigger routing is strict: no namespace resolves only in the default namespace; an explicit namespace targets exactly that instance. The best-fit heuristic is gone.
…ayout The #1955 refactor moved decks from website/presentations/ (standalone vite project) into website/roadmap/ inside the single astro site. Move the deck accordingly: drop the per-deck index.html/main.tsx, adapt App.tsx to the new chrome contract (no Footer component, TopNav without meta), keep the content layer intact.
guibeira
force-pushed
the
tech-spec/worker-compose
branch
from
f6df520 to
9dae23b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The tech pack for the worker-compose proposal, as agreed in the 2026-07-13 review — a spec directory plus its paired interactive presentation.
Spec (
tech-specs/2026-07-14-worker-compose/, markdown only):compose-file.mdworker-compose.yamlv1 — id-keyedcontainers:,depends_onscoped to one filescripts.mdscripts:—pre_start(blocking, 60s default timeout),run(supervised;path://only),post_run(fires after the run exits, any exit path, not awaited)namespace.mdtrigger()), never a function rename; same-namespace collision = rejected registrationconfiguration.mdconfig_override, delivers final config at spawncli-contract.md--url/--namespace/--configwithIII_*env fallbacks; zero-argregisterWorker()lifecycle.mdcompose::up id=<daemon>control surfaceDeck (
website/presentations/2026-07-14-worker-compose/): 11 slides + a#/crash-restartdeep dive. Registry components only — no new shared components, no changes underwebsite/presentations/src/.Verification
pnpm type-checkclean;node build.mjs(full) builds all 4 decks with no registry/frontmatter warnings#/specrenders all 7 docs, no horizontal scroll at 375px, roadmap card links to the deckNotes for review
status: draftin the spec frontmatter; flips toliveafter team sign-off.runonly for local workers), andcompose::*as a shared function family addressed byid=(implies argument-based dispatch or one daemon per namespace — worth pinning which).