Repository navigation
ISS-13446: Run vibe and fleet in any repository - #426
Merged
Merged
Conversation
Move every ClosedLoop and symphony-alpha specific line out of vibe and vibe-core into the new optional vibe-closedloop-provider plugin, which ships text and data only. With the provider bound, sessions keep today's behavior; without it, vibe and fleet work from the repository itself: the person's description, plans in the private git directory, the AGENTS.md test command, the lockfile install, and a requested PR or named recipient at the end. - provider binding, provider text assembly and data access in vibe-core - guards read their rules from the bound provider and stay silent outside an activated chat - main sync gates its provider-only machinery on the provider's recipe - the recipes opt-in file is validated and withholds recipes with one reason - the provider is offered for install once, never re-enabled or reinstalled - generic scan gate, generic walk fixture, eval arms, and generic twins for the provider-bound tests - vibe 1.1.81, vibe-core 1.0.5, vibe-closedloop-provider 1.0.0
- writer ledgers parse capabilities by shape; grants are checked against the session binding at register and launch - the Claude launcher resolves provider text for its roles - writers inherit the lead's binding through a Provider line, enforced by the Codex launcher, the Claude launcher and the Agent guard - the recipes opt-in file is validated and judged in the session repository - adopting a session keeps its binding; moved provider releases re-resolve - every installed provider's plan folder stays private - generic fleet recovery ids and duties, the worktree exclude rule, the guardrails formatter from the verify recipe - dangling reference paths fixed, provider text free of ticket ids and home paths, the inventory snapshot and mapping checked in pytest - the eval provider arm installs provider-resolved text - bundles build byte-identically from any working directory
Bind the tracker in the tracker-duty tests, run spawned scripts outside the real checkout so the cwd repository leg cannot pick it, derive the provider line in fleet tests from the fixture binding, fix the shadowed prototype deploymentHost check and rebuild dist, list provider.mjs as a vibe-core wrapper, and record the changelog word count.
Pass the lead's binding to remote fleet writers, read the recipes opt-in from the main checkout for older sessions and for a named checkout, know UI files by extension without an areas recipe, never write a legacy provider record generic, keep old hook scope records active, restore the exact ticket pattern for Prior removal, keep clerkOrgId for older vibe, report a main sync with no check as needing review, require the sole workflow for an undeclared lane source, keep generic plans in the common git dir, move the repository E2E text into provider blocks, and stop offering an install over an unreadable provider.
…c-vibe-v2 # Conflicts: # CHANGELOG.md # plugins/vibe/.claude-plugin/plugin.json # plugins/vibe/.codex-plugin/plugin.json
…ider - provider.mjs assemble writes a vibe file merged for the session's binding, and assemble --blocks gives every bound block of a loaded SKILL.md in one call; the reading rules use them - each generic region and its provider block share their identical lines once, so assembled text is unchanged and the provider is smaller - only an unbound capability falls back to the generic text: a bound provider that is gone, a missing block or an unreadable record stops with its reason and fix (exit 4) in the CLI, the launcher, every script and the hooks, and a guard refuses the action it guards - session records are written whole and renamed into place - the 1.1.82 word count is measured at this tree
ISS-14039 (#427) took vibe 1.1.82 and vibe-core 1.0.5. Keep both sides of the claude-worker launcher (the broken-provider mapping and the review model), rebuild the bundles, drop the ticket slugs the merge brought into runtime files, and remeasure the word count against the new main.
ISS-14028 and ISS-14024 (#428) took vibe 1.1.84 and vibe-core 1.0.7. The unit-status guard keeps the bound provider's rule and gains the chat's own program board; its tests keep both cases. The fleet-resume header covers both changes, the bundles are rebuilt, the ticket slugs the merge brought into runtime comments are dropped, the launcher mark written into installed launchers stays as an allowlisted compatibility line, and the word count is remeasured against the new main.
This was referenced Nov 14, 2026
…e check A bound session now behaves like main. The start is one version check when the provider skill's description names its calls, and --closedloop/--graph are accepted again as aliases of --connection; otherwise the read-only provider probe runs first, and a check with no states records unprobed instead of binding generic. Each capability binds on its own connection, so a missing graph keeps the ClosedLoop text and restores the graph. The check writes the bound text once per repository and binding, and readers open files from that folder instead of assembling each one. check always exits 0 and prints the setup block in every state. Also: precedent stays live-only, a brief without a Provider: line inherits the lead's binding, the preflight finds the checkout as main did when bound, vibe-bench binds through the real check, and the eval runner gains a provider-installed arm.
This was referenced Nov 14, 2026
…-generic - tools/vibe-closedloop-build assembles plugins/vibe plus the provider into the committed plugins/vibe-closedloop (the `vibe` entry), with cold deploy and environment sections in their own files, recipes inline, and a CI drift check. plugins/vibe is published as `vibe-generic`. - Retire runtime provider text: the rule paragraph (two generic sentences stay, dropped by the build), provider-text.md, the bind-time folder, model-run assemble/block/path/tree, the install offer, provider-install, provider-match, the skill-listed flag and the provider skill. Discovery reads only the provider bundled in vibe. - Each install finds its own plugin name and marketplace; with both installed the ClosedLoop vibe runs the hooks and binds, and the check reports both-installed. - Eval arms install the built folder (with the repository opt-in file in the case folder) and plugins/vibe as `vibe`; no harness assembly. - Resolve run.py's private homes and every main guard to real paths.
…the word-count entry - provider.mjs knownProviderContracts lists the provider bundled in every vibe install or checkout, enabled or not; local-plans uses it so a plan written while bound stays private when the session is not, whichever vibe the lookup order picks. Binding and lookup orders are unchanged. - The vibe CHANGELOG entry names the full Markdown scope of its word count again, with the generated folder's exclusion stated after it.
… 1.1.97 - The build places the provider's whole-file references (ticket-template, closedloop-graph, ticket-units) at main's paths in plugins/vibe-closedloop and rewrites provider: names to main's relative forms; provider/ holds only provider.json, whose placed map providerPath resolves through. A build test requires every Markdown file reference in the built tree to resolve. - vibe 1.1.97, vibe-core 1.0.13 (VIBE_CORE_MIN raised to it); #432's new cloud code follows the branch's generic rules.
shafty023
added a commit
that referenced
this pull request
Nov 17, 2026
Merge feat/iss-13446-generic-vibe (e316b80) per the stack-on-#426 ruling. Generic behavior stays in plugins/vibe; the ticket-units and handoff unit-review pointers move to the provider. Ticket ids leave generic runtime text per OQ10, provenance kept. Build excludes every test fixture module by name; plugins/vibe-closedloop rebuilt.
The built ClosedLoop vibe named no connection in its Plugin version command, so sessions invented --connection names and lost the setup check eval. A provider block now carries main's text, naming --closedloop and --graph; generic vibe keeps its --connection form.
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
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.
Summary
ISS-13446: vibe and fleet-orchestrator run in any git repository. Everything ClosedLoop and symphony-alpha specific moves into a new optional plugin,
vibe-closedloop-provider, that ships text and data only (provider.jsonplus reference blocks). Plan: the approved v2 plan, with Daniel's answers to its open questions (OQ1 to OQ12) recorded on the ticket.Both prerequisites have landed: symphony-alpha #9779 (merged as e3f9f4d8e7, commits
.closedloop-ai/vibe-recipes.json, the opt-in this PR reads) and the fleet orchestrator's migration of its orchestration directory into the fleet home. origin/main is merged in, most recently 8a858bb (ISS-14109: Default vibe writers to Opus, overridable models #429 and ISS-14077: Honor a recorded targeted-tests ruling in the handoff gate #430, vibe 1.1.86 / vibe-core 1.0.9; see Merged with main), so this change takes vibe 1.1.88 and vibe-core 1.0.10.Binding: one probe at vibe or fleet start records
provider: {name, state, capabilities, ...}on the startup record and the session; scripts, workers and hooks read it and never probe. States arenone,boundandbound-disconnected(a failed precondition is surfaced, never a silent downgrade). Records from before bindings existed wait for a chat that binds instead of being written generic.Repository opt-in (OQ5): recipes bind only when the repository commits
.closedloop-ai/vibe-recipes.jsonnaming the provider; it is judged in the session's repository, falling back to its main checkout for sessions branched before the file landed. No repository names are hard-coded anywhere.Generic path (vibe-generic installed): description intake with no tracker, operator identity from
gh, local#nwork ids for fleet units, plans and decision tables under<git common dir>/vibe/<slug>/, bootstrap from AGENTS.md or the lockfile, an unknown layout takes the full review path, UI files known by extension, repo-owned gates run only when the repo ships them, main sync with nothing to run reports NEEDS_REVIEW, an undeclared lane source must be the AGENTS.md test command or the repo's only workflow.Hooks: every vibe-core guard is gated on activation (a vibe-plugin skill in the chat, a launcher-started worker, or a cwd in a vibe worktree); elsewhere a guard prints, writes and calls nothing. ClosedLoop guard rules (unit status, e2e slot) come from the bound provider's data.
Fleet: writers inherit the lead's binding through the brief's
Provider:line; remote writers get it with the launch (--lead-provider). Status sweeps, ticket units and placement by ticket are provider duties.Install (OQ1), superseded at this head: there is no provider plugin to install. ClosedLoop machines get the built
vibe; going generic means installingvibe-generic(see Release-time build).Gates:
vibe_generic_scan.py checkfails on provider-specific text in runtime files (exact-line allowlist with reasons); the inventory diff test proves no gating line of the base was dropped;generic-walk.test.mjsruns the walk's deterministic steps in a personal repository and requires an empty blocker ledger; the Codex eval runner has provider and generic arms.Two independent adversarial reviews (A and B) ran on the full diff; every finding was verified against the code. A1 to A7 and B2 to B10 are fixed with tests: remote fleet writers could not start under a bound lead; the opt-in was read only from the session branch; generic UI diffs counted as server-only; legacy records could be written generic; old hook scope records stopped activating; the Prior removal check widened;
clerkOrgIdwas no longer written for an older vibe; main sync with no check reported DONE; an undeclared workflow lane source could be any workflow; generic plans lived in the per-worktree git dir; symphony E2E text sat in generic handoff text; an unreadable provider was offered for reinstall.Reported, not changed:
Known limit, tracked as ISS-14022 (review finding B1) and not changed here: vibe still assumes the default branch is
mainunlessvibe.baseRefis set (session creation, handoff gate, several merge-base diffs, main sync).Reading provider text, superseded at this head: runtime assembly (
assemble,--blocks, the bind-time folder) is retired; the text is assembled at release time (see Release-time build).Broken provider (orchestrator rulings): only "no provider with is bound" (exit 3) means generic text. A bound provider that is gone, a missing block or reference, or a session or startup record that exists but cannot be read stops with
provider-broken: <reason>. Fix: ...(exit 4) in provider.mjs, the Claude launcher (PROVIDER_BROKEN), and every vibe script that reads the provider. Hooks never throw: they show the reason and fix and keep their generic default, and a guard whose default would relax the bound rule refuses the action it guards (unit-status-guard on an MCP status write, shell-safety-guard on an executed e2e script, pr-create-guard when the override decides). Session records are written atomically.Also fixed:
prototype-session.mjsshadoweddeploymentHostwith aconstof the same name (a throw on every call) and its bundle was stale; test helpers ran scripts from the real checkout, which the new cwd repository leg could pick up.Versions at this head: vibe 1.1.97, vibe-core 1.0.13 (
VIBE_CORE_MIN1.0.13), vibe-closedloop-provider 1.0.0. These are above main's 1.1.94 / 1.0.12 and every open PR's reserved version. Earlier, at 22c726c: vibe 1.1.88, vibe-core 1.0.10; dist bundles rebuilt. Word count against 1.1.86 (origin/main 8a858bb) at this head (instruction-words.mjs --changelogpasses): vibe about 19982 words shorter, the provider adds about 42419, all plugin Markdown about 22833 longer. The merges brought ticket slugs into runtime files (four(ISS-14039)from ISS-14039: Accept a Fable review for a Claude cloud import #427, fiveISS-14028/ISS-14024comments from ISS-14028, ISS-14024: Bind fleet chats to their programs, safe migrate #428, and theISS-14109/ISS-14077comments from ISS-14109: Default vibe writers to Opus, overridable models #429 and ISS-14077: Honor a recorded targeted-tests ruling in the handoff gate #430); they are removed here (OQ10). The sixth from ISS-14028, ISS-14024: Bind fleet chats to their programs, safe migrate #428, fleet-home.mjsLAUNCHER_MARK, is text written into installed launchers and matched before an overwrite, so it stays as an allowlisted compatibility line.Merging ISS-14028, ISS-14024: Bind fleet chats to their programs, safe migrate #428: unit-status-guard keeps the bound provider's rule and gains ISS-14028, ISS-14024: Bind fleet chats to their programs, safe migrate #428's per-chat program board (both tests kept; ISS-14028, ISS-14024: Bind fleet chats to their programs, safe migrate #428's chat test now passes the provider rule).
provider.json(1310 words) is data only scripts read; per-file provider headers and block markers are never printed to an agent.Release-time build (this head)
The realistic eval arm showed a real ClosedLoop session reading the generic text and missing main's steps (findings/iss13446-realistic.md). This head drops runtime assembly and builds the ClosedLoop vibe at release time.
Operator rulings this head implements (quoted from the program's rulings record):
vibein its own eval marketplace, with no grader change. The ClosedLoop build keeps the name vibe.What ships. Both entries are in
closedloop-ai(Claude and Codex catalogs):vibe:plugins/vibe-closedloop/, a generated folder with manifest namevibe. Every existingvibe@closedloop-aiinstall updates into it.vibe-generic:plugins/vibe/, with manifest namevibe-genericin both harnesses. Codex refuses an entry whose name differs from its manifest's ("plugin.json namevibedoes not match marketplace plugin namevibe-generic", codex-cli 0.167.2). Real generic users seevibe-generic:*skill names. A bare$vibestill resolves (step 0).vibe-closedloop-providerleaves both catalogs. Its folder is build input only.The build (
tools/vibe-closedloop-build,npm run build):assembleProviderTextwith every declared capability. There is one assembler; the Python twinskill_split.assembledis deleted.skills/vibe/references/closedloop-deploy.mdandclosedloop-environment.md, each reached by one provider-written line..closedloop-ai/vibe-recipes.json.ticket-template.md,closedloop-graph.md,ticket-units.md) are placed at main's paths (skills/vibe/references/,skills/fleet-orchestrator/references/), andprovider:<file>names become main's relative forms.provider/holds onlyprovider.json; itsplacedmap is whatproviderPathresolves through. Block sources are not shipped. A build test requires every Markdown file reference in the built tree to resolve. The exceptions that also fail on main (target-repository names, other plugins' files) are listed with their reasons.vibe-generic:,vibe-generic@and/vibe-generic/become main'svibeforms.plugins/vibe-closedloop-provider/build.json.plugins/, so the version-bump job and the manifest tests cover it with no new wiring. The AC1 scan'splugins/vibe/prefix does not match it, and the scan is unchanged.tools-tsmatrix row rebuilds and fails on any diff or untracked file.Discovery and binding.
<vibe>/provider/provider.json; the sibling-plugin scan is gone.Retired.
references/provider-text.md.tree.assemble,blockandpathcommands.providerTextPolicy.provider-installandprovider-match.run.py.Where fixes go. This rule is added to CLAUDE.md (Claude) and AGENTS.md (Codex):
plugins/vibe, andvibe_generic_scan.py checkgates it.plugins/vibe-closedloop-provider.plugins/vibe-closedloopis build output and never hand-edited; CI'sTypeScript (vibe-closedloop-build)drift check enforces that.Plan-folder privacy.
knownProviderContractslists the provider bundled in every vibe install or checkout, enabled or not.local-plansuses it, so a plan written while bound (<artifactRoot>vibe-plans/) stays private evidence after the session is unbound, whichever vibe the lookup order picks.local-plans.test.mjsexpectedknownLocalPlanPrefixes(null)to be empty in this checkout. It now expects.closedloop-ai/vibe-plans/, because the built ClosedLoop vibe sits beside the source.Name and lookup.
plugin-roots.mjs, vibe-core canonical, vibe mirror) holdsDEFAULT_MARKETPLACEand the two plugin names. No hook keeps its own copy.conflict: "both-installed"(a code, no new sentence).catalog-namescheck fails when a catalog entry name differs from its manifest name.Compatibility shims kept (an installed older client can still call these):
provider.mjs tree|assemble|block|pathprint oneprovider-broken: ... is retiredline and exit 4.plugin-version.mjs provider|provider-install|provider-matchanswer{"ok":false,"retired":...}.--skill-listedand--expectare accepted and ignored.--closedloop/--graphremain aliases.isEntryPoint.Eval arms.
provider-installed(the realistic arm) installs the committedplugins/vibe-closedloopasvibeunchanged. It writes symphony-alpha's opt-in file ({ "schema": 1, "provider": "vibe-closedloop-provider" }, as committed at abe87d83) into the run's copy of the case folder before the real check.plugins/vibeasvibe, renaming only the snapshot's manifest, as main's baseline does.recipeswithheld: run.py's case folders are not git checkouts, so the opt-in file is present but unused (provider.mjs finds the repository by walking up to.git). The built text has recipes inline either way, so the arm compares like for like. Not built: having run.pygit initthe run's copy of each provider-arm case folder before the bind. It is only revisited if Step 1 shows a failure caused by withheld recipes, because it changes what the model sees.Harness fixes.
run.pyresolves its private homes to real paths.isEntryPointthat compares real paths.tools/shared/cli.tsrunWhenMain(bundled into other plugins), the closedloop-core gh-monitor-pr scripts,tested-head.mjs(runs from a lone copy), and the eval checkeriss-13760-reply-format.mjs.Generic noise, for reading the generic arm.
Merged with main
At this head (regular merges, no rebase):
startClaudewhole, and this branch's connector refusal moved to cloud-routines.mjs, whose message now names the approved connectors rather than ClosedLoop. ISS-13998, ISS-14140: Remove vibe's cloud routines, fix check #432's comments lost their ticket slugs (the generic scan requires it). vibe-triage.test's abandon case got its provider binding back (setup only).#N; its main guard uses isEntryPoint.Earlier merges:
origin/main 8a858bb is merged in (merge commit 72a2a7c). It brought #429 (ISS-14109: overridable model defaults) and #430 (ISS-14077: targeted-tests rulings in the handoff gate, cloud-import PR titles). Main's behaviour is kept; this PR's provider extraction is applied on top where both touched the same lines. 18 files conflicted:
CHANGELOG.md: main's vibe 1.1.86 and vibe-core 1.0.9 entries kept; this PR's entries renumbered to vibe 1.1.88, vibe-core 1.0.10 and vibe-closedloop-provider 1.0.0 (1.1.87 is held by ISS-14112's open work), word counts remeasured against 8a858bb.plugin.json(Claude and Codex),test_vibe_ws8_load_contract.py,test_pr_takeover_skill_contract.py,reply-checker.test.ts: version numbers only, now 1.1.88 and 1.0.10.plugins/vibe/README.md: main's model-defaults text kept inside this PR's generic README; version line 1.1.88.review-models.mjs,claude-worker.ts: main's model resolver andmodel/reviewModellaunch fields kept as written, with this PR's binding checks (sessionBinding,requireSupportedCapabilities, brief inheritance,recordModes(binding)) around them; ticket slugs dropped from the comments. The dist bundle was rebuilt, not hand-merged.handoff-gate.mjs,targeted-tests-ruling.mjs: main's ruling logic kept; this PR'sexitOnProviderBrokenadded; slugs dropped from comments.pr-facts.mjs: judgment. Main added a ruling id parameter toselectionProblems; this PR had added the provider's PR rules parameter to the same function. Both are kept:selectionProblems(runsFile, files, requiredTests, commit, rules = GENERIC_PR_RULES, rulingId = null), and the ruled-test check passesrulestoe2eCarriedForCi.pr-facts.test.mjs,vibe-triage.test.mjs: main's new ruling and title cases kept, run under this PR's bound-provider fixtures.plugins/vibe/agents/vibe-verify-worker.mdandvibe-environment-worker.md: judgment. This PR had moved the sections main edited into the provider's copies of those agents, so main's targeted-tests text (the verify worker's ruling paragraph,--rulingson the gate and evidence commands) went intovibe-closedloop-provider/.../references/agents/only. Operator ruling (Daniel, 2026-11-13): this text stays in the provider copies only ("only closedloop sessions will have access to closedloop-graph"). A session with no provider bound keeps the existing fallback (vibe-verify-worker.mdlines 86 to 97): the tests related to each changed file, through the repository's documented command.Checks on 72a2a7c, through the local heavy slot: ruff, pyright, plugin manifests, vibe-bench, the whole Python lane (2806 passed, 3 skipped), the 53 node test files the merge touched (637/637), vibe-workers typecheck and build with the committed bundle matching,
claude-worker.test.ts69/69, the changelog word count. vibe-workers' full vitest run had 37 timeouts at load average about 57 and no assertion failure; the 5 inclaude-worker.test.ts(merge-touched) passed on rerun, and the 32 inmain-sync*andscope-intakefiles the merge did not touch are left to CI. The ISS-14077 ruling tests pass with the provider bound; with no provider bound, the 9 that need the provider's tracker ticket or lanes fail as expected, as the ruling above intends.A bound session behaves like main (previous head f1d1e02; superseded by Release-time build)
Operator rulings (Daniel, 2026-11-13): #426 cannot merge while it fails an eval that passes on main, and the fix goes in the PR, never in the evals (no grader, fixture or case edits). The bar: every case main passes, passes with the provider bound, at main's rate. Design chosen: fix how a bound session reads the provider's text at runtime, with a realistic eval arm as the merge measure.
The model evals and four reviews found that a real bound session did not read what the eval's provider arm read.
run.pypre-assembled every vibe file with every capability bound, while a real session read the raw generic text and was told to runprovider.mjs assembleper file, which writes under the home folder and stops on a refused write. The setup-check case also failed because the start opened withplugin-version.mjs providerand the old--closedloop/--graphflags had become an unknown option. What changed:plugin-version.mjs checkwith--closedloop/--graph, accepted again as aliases of--connection, as on main. Otherwiseplugin-version.mjs providerruns first; it now writes nothing. The skill list never decides "no provider": a check with no connection states while a provider is installed recordsunprobed, names the calls, binds nothing, and every provider read andvibe-sessions.mjs new/adoptstop until it runs again with the states. In Claude Code the provider counts as loaded when its skill name is in the list.checkalways exits 0, prints the setup block in every state (a broken provider's reason and fix included, and with no provider at all), and carries the install offer. Fixed on the way:plugin-version.mjs providerthrew whenever an install offer stood (a constant read before its declaration).missing, and the setup worker restores it, as main did (8a858bb SKILL.md:416-428). A stub naming several capabilities is served when any of them is bound, so its ClosedLoop text stays; graph-only stubs keep their generic text until the graph is back. Before this, one unanswered connection made the whole session generic (launcher grants, live-ticket slugs, PR evidence rules, the unit-status and e2e-slot guard rules).binding.json(repo root, provider, versions, vibe root, capabilities) to~/.codex/vibe/provider-text/<key>/, keyed by the repository's main checkout (or the working folder outside a checkout), replaced whole, withindex.jsonnaming each folder. A reader opens files there, byprovider.mjs treeor by readingindex.json, only whenbinding.jsonnames its repository and its vibe install; otherwise it runs the check again, andassembleis the last resort. Codex's default and workspace-write sandboxes can read that folder (checked withcodex sandboxon codex-cli 0.167.2); only the escalated check writes it. In a bound session an exit 3 fromassemble,blockorpathis a stop, not a generic fallback.Provider:line inherits the lead's binding instead of being refused (main refused nothing here); only a line naming another binding is refused.vibe-preflight.shfinds the checkout exactly as main did (8a858bb vibe-preflight.sh:205-238):--repo(another repository is refused, a claude-plugins checkout is used for that run only), the remembered checkout, then the home-folder search, withchoose-repofor several clones. The remotes come from provider data. A session with no provider also accepts the checkout it runs in. No preflight difference from main remains.--skill-listed); its old flags work again.provider-installedcopies the raw vibe text, installs the provider and runs the real check in each case folder before the model starts (HOME set to the run's own folder, the release read from a loopback copy of the eval marketplace). Theproviderarm still pre-assembles every capability, so it never exercises a partial binding; the new arm is the merge measure. The old arms are kept.Breaking changes
vibe@closedloop-ainow installs the built ClosedLoop folder (plugins/vibe-closedloop); ClosedLoop sessions read main's text. Generic vibe is a new plugin,vibe-generic@closedloop-ai, whose skills arevibe-generic:*. There is no separate provider plugin to install or disable.provider.mjs tree|assemble|block|path(exit 4) andplugin-version.mjs provider|provider-install|provider-match;--skill-listedand--expectare ignored.board.mjsrefuses writes to an orchestration directory that is not a program in a fleet home (fleet-home.mjs migratemoves one). Session records gain an optionalproviderfield;environmentOrgIdis written beside the earlierclerkOrgId, which is still read and written.Test plan
This head (e316b80). The merges of #432, #436, #434 and #435 and the layout fix are verified on laptop 2's heavy slot unless noted:
pytest plugins/(at 5d4a82ac);Test timed outand spawn ETIMEDOUT, even run alone. Load was 18 to 24, with another fleet holding the heavy slot. tools/vibe-workers/src is unchanged since 22c726c, whose CI vibe-workers job passed; main-sync-input-boundary passed 63/63 locally. Left to CI.At 22c726c: 73ad772's CI had two red tests, both fixed:
main-sync-report-closure.test.tsplan-folder privacy (the behavior is restored and the expectation unchanged).pytest plugins/): 2822 passed, 3 skipped.At 73ad772: targeted tests through the local heavy slot.
vibealone binds all 5 capabilities from its bundled provider in both harnesses.vibe-genericalone binds none and listsvibe-generic:*.$viberesolves tovibe-generic:vibe(one codex exec).Earlier heads
provider.mjs(new, so not in the test-selection index) is imported by nearly every vibe and vibe-core test. code_tests_for_changes on the last round's 61 files selected 102 unit test files (hooks, fleet, handoff and vibe scripts, claude-worker); the full lanes cover them all.test_run.py) and vibe-workers typecheck, vitest and dist freshness all pass.e2e-lock.test.mjshung once under a loaded full run (load average about 40 from other sessions). Its signal cases then passed 3 of 3 in isolation, and its one change (the top-level catch calls failScript) is not on the signal paths. It passed in the final full run.main-sync.test.tsandmain-sync-input-boundary.test.tstimed out (16 to 44 s against 15 s) at load average 37 to 45. They passed 122/122 on one sequential rerun.--blocksorder and labels; exit 2, 3 and 4; an unreadable record is broken; a script exits 4 (local-plans); a guard refuses while generic checks still run, and grep/cat of e2e paths pass (pre-tool-use); a hook warns and still runs (program-change); PROVIDER_BROKEN mapping and CLI exit 4 (claude-worker).Test timed outat 5 s, 2spawnSync node ETIMEDOUT), with no assertion failure: claude-worker.test.ts 8, main-sync.test.ts 7, main-sync-ci, main-sync-input-references and main-sync-report-admission 1 each, at load average 50 to 65 on 10 cores from other sessions. After the ISS-14039: Accept a Fable review for a Claude cloud import #427 merge the same claude-worker file passed 67/67 and main-sync 122/122 in a sequential run; they are left to CI on clean runners rather than rerun here.test_run.py, vibe-bench (typecheck, validate, tests), vibe-workers (typecheck, vitest 860/863, committed bundle fresh), the Node Tests lane the CI way (201 files, 2143 pass, 0 fail, 1 skipped),claude-worker.test.tsplusmain-sync.test.tsalone 128/128 (their 3 timeouts in the full vitest run were at load), the whole Python lane (2817 passed, 3 skipped), the changelog word count andinstruction-words.test.mjs. Every new behavior has a test that failed when the change it covers was reverted.e2e-lock.test.mjshung in the full node run at laptop 2's load (itse2e-lock.mjs runchildren never finished). This fix does not touch e2e-lock or anything it imports, and the same hang under load is recorded above at an earlier head; CI runs it. The node lane above is every other file./update-documentation(the vibe README's eval count 121 to 125; the vibe-core and provider READMEs were accurate).