Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
20 commits
Select commit Hold shift + click to select a range
ac33c48
ISS-13446: Run vibe and fleet in any repository
shafty023 Nov 11, 2026
3794f94
ISS-13446: Close review findings and bind writers to the lead
shafty023 Nov 11, 2026
47c858b
ISS-13446: Run every validation lane in the foreground and name its f…
shafty023 Nov 11, 2026
c55eaa0
ISS-13446: Fix the node lane under generic defaults
shafty023 Nov 11, 2026
66f7b2c
ISS-13446: Close the adversarial review findings
shafty023 Nov 11, 2026
6c6ad98
Merge remote-tracking branch 'origin/main' into feat/iss-13446-generi…
shafty023 Nov 11, 2026
de622fa
ISS-13446: Read provider text once per file and stop on a broken prov…
shafty023 Nov 11, 2026
c252ec8
ISS-13446: Merge origin/main and move to vibe 1.1.83, vibe-core 1.0.6
shafty023 Nov 12, 2026
5fa5f12
ISS-13446: Merge origin/main and move to vibe 1.1.85, vibe-core 1.0.8
shafty023 Nov 12, 2026
72a2a7c
ISS-13446: Merge origin/main and move to vibe 1.1.88, vibe-core 1.0.10
shafty023 Nov 13, 2026
f1d1e02
ISS-13446: Bind the provider per capability and read its text from th…
shafty023 Nov 14, 2026
73ad772
ISS-13446: Build the ClosedLoop vibe at release time and publish vibe…
shafty023 Nov 15, 2026
22c726c
ISS-13446: Keep every bundled provider's plan folder private and fix …
shafty023 Nov 16, 2026
e39b39a
ISS-13446: Merge origin/main (#432)
shafty023 Nov 16, 2026
f503675
ISS-13446: Merge origin/main (#436)
shafty023 Nov 16, 2026
060793c
ISS-13446: Merge origin/main (#434, #435)
shafty023 Nov 16, 2026
e316b80
ISS-13446: Place provider references at main's paths and move to vibe…
shafty023 Nov 16, 2026
a383f92
ISS-13446: Give the ClosedLoop build main's version check command
shafty023 Nov 17, 2026
cef57dc
ISS-14162: Fix the quarantined vibe eval cases
shafty023 Nov 17, 2026
e6d23ba
Merge main into vibe/iss-14162-eval-quarantine
shafty023 Nov 17, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
43 changes: 43 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,49 @@ All notable changes to the claude-plugins project will be documented in this fil

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). Entries are listed newest-first; each plugin section is treated as released when merged to `main`.

### vibe v1.1.100

#### Changed
- The vibe skill description no longer names one host. It says vibe runs in Codex Desktop or Claude Code and applies to every turn of a session, mid-session build turns included. The published `vibe` carries the same description through `build.json`.
- Missing test entries name the uncovered host, the acceptance criterion IDs each covers and the owning test lane by name, in the change worker, quality loop, handoff skill and ticket template. Handoff states this once and points to it rather than repeating it.
- A pull request body or evidence that the handoff gate refuses (`blocking.prBody` or `blocking.prEvidence`) creates nothing. The environment worker returns `NEEDS_CHANGE` with the problems, and the same writer fixes them before the gate runs again. Any other failed gate is still `BLOCKED`.
- The requirements worker reports each overlapping open pull request with one line per shared path, `open pull request #<n> touches the same file: <path>`.
- The ready message gives each link as the `url` that `vibe-sessions.mjs link` printed. With no URL, it names the page in words and gives no link, placeholder, or script or command name. `plain-words.md` adds the matching rows.
- Reference image checks:
- Each visual property and each visible state (hover, selected, disabled) is its own criterion, delivered by a design token, with a catalog component alone only when no token can deliver it.
- A Reference check line names each touched element and is written only after viewing a render of the last edit, because any edit after a comparison voids it.
- A property the render cannot show is reported as not verified yet. The person is never asked to look at it.
- A question to the person is sent only after `session-questions.mjs ask` has run for it and returned `"ask": true`. Publishing or reconciling the local plan never pauses the build.
- Story play checks fail without a real-browser run of each touched story's play. An unawaited `storybook/test` interaction, a jsdom result or a successful build is not play evidence. Touch checks use real touch on WebKit iPhone and Chromium Pixel, and an iOS tap is judged by its result.
- A human-only blocker's next action is the handover itself. The person is asked who picks the work up only when no one is named.
- The precedent check brief names the product the bound provider gives (`live <product>`). It falls back to an established app with the same flow only when the provider names none.
- Measured by `plugins/vibe/skills/fleet-orchestrator/scripts/instruction-words.mjs` against 1.1.97 (origin/main at this update, 7d5bacfc): `plugins/vibe` is about 591 words longer, and the vibe-closedloop-provider folder adds 208 words. Across all plugin Markdown, including eval prompts and graders, under `plugins`, with every file under the generated `plugins/vibe-closedloop` left out, this change is 799 words longer.

#### Fixed
- The handoff diff rules no longer stall on a large changed code file such as a bundled script (ISS-14325). The guarded-constant check in `comment-rules.mjs` used to split the file's whole prefix for every line lookup, search the whole file again for every definition, and test a 200-character window with a regex for every use. It now makes one line index per file (the new `line-index.mjs`: newline offsets found once, then a binary search), one pass over the file's identifiers that gives the reads of every name, and a backward scan for the object-key test. The import and transaction line lookups in `diff-rules.mjs` use the same line index. The findings, files, lines and messages are unchanged.
- The duplicate-helper rule no longer flags a helper against its own built copy, a new sighting of the ISS-14136 class: #426's built mirror, the ClosedLoop `vibe` that `tools/vibe-closedloop-build` copies from `plugins/vibe`. The build now writes a generated `.vibe-build.json` at the built plugin's root, `{"builtFrom": "plugins/vibe"}`, computed from its source path. `checkDuplicateHelpers` in `review-gap-rules.mjs` treats a file under such a marker and the file at the same relative path under `builtFrom` as one definition, but only when that source exists at head or base. A missing or malformed marker, a marker naming a missing source, or a copy at any other path is still flagged.
- Eval cases and graders now agree with vibe's written rules:
- The `pm-prd-children-are-scope` prompt states each line's allowed status values separately.
- The reply-format checker accepts the optional status field.
- The missing-tests, lockfile, handover, touch, play, light-and-dark and plan graders match the current rules.
- `exec-asana-lacks-flow-checks-another-app` asks its open question through `session-questions.mjs ask`.
- The described-change stand-in relays the writer's result as the orchestrator, with a deployed live copy to link to.
- The `ref-card` and `return-page` reference images are re-rendered.

#### Removed
- The `exec-precedent-answer-recorded-not-asked` eval case.

### vibe-closedloop-provider v1.0.3

#### Changed
- The provider's precedent block checks live Asana only and records `Asana, observed <date>` as the source.
- The provider's requirements worker lists matched `EXECUTED` PRDs before open tickets, one `EXECUTED PRD <slug>: DONE child <slug>: shipped rule: <rule>` line per `DONE` child. The graph reference points to that rule.
- The handoff Workers table keeps its running app checks row and adds a Desktop row:
- Run `pnpm -C apps/desktop build` first, then check that `apps/desktop/dist` holds the documented Electron entry.
- If the build fails or the entry is missing, abort the Desktop check without any Electron launch and return the limitation.
- `handoff-ui.md` points to that row.
- The provider ticket template's missing tests list carries acceptance criterion IDs and the owning test lane. The provider's environment worker carries the same `NEEDS_CHANGE` gate rule as the generic one.

### vibe-closedloop-provider v1.0.0

#### Added
Expand Down
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "vibe-closedloop-provider",
"description": "ClosedLoop and symphony-alpha knowledge for vibe and fleet-orchestrator: tickets, plans, the code graph, repository memory and the symphony-alpha recipes. Build input for the vibe plugin: tools/vibe-closedloop-build assembles it into plugins/vibe-closedloop",
"version": "1.0.0",
"version": "1.0.3",
"author": {"name": "ClosedLoop", "email": "support@closedloop.ai"}
}
2 changes: 1 addition & 1 deletion plugins/vibe-closedloop-provider/.codex-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "vibe-closedloop-provider",
"version": "1.0.0",
"version": "1.0.3",
"description": "ClosedLoop and symphony-alpha knowledge for vibe and fleet-orchestrator: tickets, plans, the code graph, repository memory and the symphony-alpha recipes. Build input for the vibe plugin: tools/vibe-closedloop-build assembles it into plugins/vibe-closedloop",
"author": {"name": "ClosedLoop", "email": "support@closedloop.ai"},
"homepage": "https://github.com/closedloop-ai/claude-plugins",
Expand Down
2 changes: 1 addition & 1 deletion plugins/vibe-closedloop-provider/build.json
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@
"agents/vibe-requirements-worker.md": "Turns a ClosedLoop ticket or a plain description into vibe-session requirements for the target repository. Reads the ticket with its PRD, plan, and related tickets through closedloop-graph and the ClosedLoop MCP, checks for existing or overlapping work, locates the route and FEATURE_MAP id where the relevant code lives (for change workers), and returns a short brief plus any questions only the person can answer. In reference mode, researches an outside product the person named or showed in a reference screenshot, reads the image itself, and returns the behaviors plus the visual and UX requirements to build, mapped to the design system. In precedent mode, obtains live Asana evidence through whichever actor has the operator's signed-in browser, never public help centers. Read-only.",
"agents/vibe-ticket-worker.md": "Owns a vibe session's live ClosedLoop ticket in the target repository for the vibe and handoff orchestrators. Create mode makes the ticket when the session starts (assigned to the person running the session, In Progress) from the live ticket template, records its slug on the session and links the document the session started from to it. Plan mode publishes the session's local plans as one implementation plan document (PLN) linked from the ticket, keeps it current and sets its status as the work moves, recording the PLN on the session. Lookup mode finds the ClosedLoop user the person named as the next owner (every page of list-users, matched by the match-assignee script) and changes nothing. Handoff mode refreshes the record sections, fills the Handoff and Grading sections, reconciles the backend sections, attaches decision tables, verifies and repairs the source link, the PLN and its link, leaves the PLN Approved, and checks the ticket is complete. Assign mode hands the ticket and its PLN to the next owner the lookup resolved, with the ticket status left In Progress. Cancel mode moves only a discarded session's own created ticket to Canceled. Returns a short status.",
"agents/vibe-verify-worker.md": "Read-only validation and coverage advisor for a vibe session. Runs existing checks and Storybook footprint, reports failures and the missing tests engineering must write, drives the running web app and Desktop with the repo's control skill at handoff, and returns evidence to the same persistent implementation writer. Never writes or fixes source or tests.",
"skills/vibe/SKILL.md": "Start or resume a vibe-coding session in symphony-alpha for anyone (an executive, designer, product manager or engineer) working in the Codex Desktop in-app browser. For a pure mockup or fake-data exploration, invokes the repository's canonical prototype skill itself in an owned prototype session, always shares on Vercel, and returns the immutable preview URL, full deployed commit SHA, and slug; handoff preserves the same live ticket and next-owner assignment, opening a PR only when the person asks for one. Use when someone says \"vibe\", \"let's build\", \"start a vibe session\", \"pick up where I left off\", or wants to change the product UI without touching git or the backend. Hand the finished work off with the handoff skill."
"skills/vibe/SKILL.md": "Start or resume a vibe-coding session in symphony-alpha for anyone (an executive, designer, product manager or engineer) working in Codex Desktop or Claude Code; it applies to every turn of a vibe session, including mid-session build turns. For a pure mockup or fake-data exploration, invokes the repository's canonical prototype skill itself in an owned prototype session, always shares on Vercel, and returns the immutable preview URL, full deployed commit SHA, and slug; handoff preserves the same live ticket and next-owner assignment, opening a PR only when the person asks for one. Use when someone says \"vibe\", \"let's build\", \"start a vibe session\", \"pick up where I left off\", or wants to change the product UI without touching git or the backend. Hand the finished work off with the handoff skill."
},
"cold": {
"vibe-skill.md": [
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -47,12 +47,11 @@ Apply a settled ruling, never ask it again; settled means traced to a human
statement (`quality-loop.md`, "Communication and product questions"). Only an
absolutely necessary unresolved product question returns `NEEDS_PERSON`, with
sources checked and full context; before asking, the orchestrator checks how
Asana or another established app handles it (`quality-loop.md`, "Precedent
before asking"). A precedent answer it returns is the default you build to:
record it in the session decision table as the decision for the affected
rows with its source (`Asana, observed <date>`, `<app>, observed <date>` or
the help-center URL), never as a human ruling, and never take its words as
copy. Resolve technical ownership/backend/adapter
live Asana handles it (`quality-loop.md`, "Precedent before asking"). A
precedent answer it returns is the default you build to: record it in the
session decision table as the decision for the affected rows with its source
(`Asana, observed <date>`), never as a human ruling, and never take its words
as copy. Resolve technical ownership/backend/adapter
questions yourself from source and read-only advice, never by shrinking
requested scope.
<!-- end: precedent -->
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -493,8 +493,10 @@ changes and gates fields.
<verifier receipt> --ticket
<ticket body file> --audit <criteria audit file> --matrix <coverage matrix
file>` (plus `--member <slug>=<body file>` for each `memberTickets` entry and `--title "<title>"`, which with members must name each one, as must the body, and `--rulings <program rulings file>` when the evidence cites a targeted-tests ruling recorded there) immediately before creation. Use the paths step 9 of handoff passed;
when there is no ticket, omit the ticket/audit/matrix arguments. A failed
gate is `BLOCKED`, not a reason to bypass the hook, except through the
when there is no ticket, omit the ticket/audit/matrix arguments. A gate
that fails on `blocking.prBody` or `blocking.prEvidence` creates nothing
and returns `NEEDS_CHANGE` with those problems; any other failed gate is
`BLOCKED`. Neither is a reason to bypass the hook, except through the
exception the hook's refusal names. Create it with
`gh pr create --repo closedloop-ai/symphony-alpha --base main --head <branch> --title "<title>" --body-file <file>`,
the body file in the session's private git directory and named for the
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,9 @@ must not be written as if it had been made. Without the script, work as below.
title and request text, then `search_nodes` and `fts_search` on its key
terms. Inspect every matching PRD even when it is `EXECUTED`: report its
`DONE` children and the shipped rules they established so the session does
not reclaim delivered work. For every overlapping live child whose stated
not reclaim delivered work, one line per `DONE` child in this shape:
`EXECUTED PRD <slug>: DONE child <slug>: shipped rule: <the rule it
established>`. For every overlapping live child whose stated
outcome matches the request, return the required reconciliation: include
it, cite a human supersession ruling, or leave it uncovered with its current
status and owner. Discovery alone is incomplete.
Expand All @@ -102,7 +104,10 @@ must not be written as if it had been made. Without the script, work as below.
4. Note in-flight work on that code: run `blast_radius_tickets` on its route
and main component files. List open GitHub pull requests and inspect their
changed files, reporting every open pull request that touches any of those
same files or a module they import; resolve each named dependency ("Roadmap
same files or a module they import, after the lineage lines, one line for
each shared path of each such pull request:
`open pull request #<n> touches the same file: <path>`. Whoever picks the
work up needs the number and the shared path. Resolve each named dependency ("Roadmap
N", "Dependencies:") to its PRD and open pull requests. A ticket-only
collision result is incomplete.
<!-- end: in-flight -->
Expand Down Expand Up @@ -143,9 +148,11 @@ data direction flagged `data direction (new)`; the Newest ruling and Prior remov
acceptance criterion of the ticket and its PRD, quoted exactly with its source
slug, or "none stated"; the route and FEATURE_MAP id where the relevant code lives and the
`likelyFiles` (each `path` with its `source`, or none), for change workers (not
shown to the person); overlapping or in-flight tickets
(slug and title), open pull requests touching the same files, and each matched
`EXECUTED` PRD with its `DONE` children and shipped rules; for a source PRD,
shown to the person); the overlap report, which leads with each matched
`EXECUTED` PRD with its `DONE` children and shipped rules, one line per child
in step 2's shape, then overlapping or in-flight tickets (slug and title) and
open pull requests touching the same files, one line each in step 4's shape;
for a source PRD,
every child with its scope classification, current status, owner and activity
evidence; and whether this is a change to an existing screen or a
net-new screen. Or
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -252,7 +252,8 @@ Three more rules:
- For every new or changed story with a `play` function, and every story
file with a `play` on a component whose layout, position or scrolling the
diff changes, inspect every
`storybook/test` interaction and report any call that is not awaited. Then
`storybook/test` interaction and report any call that is not awaited as a
failing play. Then
execute the touched stories' plays in a real browser with the repository's
Storybook test runner or Playwright against its containerized Storybook
service. A jsdom result, source inspection or successful build is not play
Expand All @@ -276,9 +277,9 @@ Three more rules:
comment exposes them.
- When cards or a narrow layout have any interaction, run the relevant flow
with real touch through Playwright's WebKit iPhone descriptor and Chromium
Pixel descriptor. Keyboard input and Chromium with `hasTouch` alone do not
count, and neither do a Storybook fixture standing in for the consumed
surface or synthetic `dispatchEvent` pointer events for the gesture under
Pixel descriptor. Keyboard input and Chromium with `hasTouch` alone are
insufficient evidence, and so are a Storybook fixture standing in for the
consumed surface or synthetic `dispatchEvent` pointer events for the gesture under
test. Judge an iOS tap by its user-visible result in both device runs, even
when its click reports `pointerType` as `mouse`.
Record runs of the inventory's `requiredLanes` (with `webkit-iphone` and
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -106,7 +106,9 @@ Never send a technical question or re-ask a settled decision
screen.
- Before building a net-new screen or capability, run `query_collisions` and
`search_nodes` on the request. Include matched `EXECUTED` PRDs, their `DONE`
children and shipped rules, because delivered work still constrains scope.
children and shipped rules, because delivered work still constrains scope;
report them before open tickets, one line per `DONE` child
(`../../../agents/vibe-requirements-worker.md`, step 2).
If an open ticket already covers it, report that ticket so the person can
decide whether to build on it.
- Before editing a file, run `blast_radius_tickets` on it. An in-progress
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,7 @@ follows `provider:ticket-template.md`. You and every worker leave

<!-- block: control-row -->
| Running app checks with `pnpm control` | read-only `vibe-verify-worker` (control mode) |
| Desktop running app checks, before any launch | the same worker runs `pnpm -C apps/desktop build` first, then checks that `apps/desktop/dist` holds the documented Electron entry; if the build fails or that entry is missing, it aborts the Desktop check without any Electron or `control up desktop` launch and returns the limitation |
<!-- end: control-row -->

<!-- block: pick-session -->
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,9 @@ Every new story follows the repo's `apps/storybook/TAXONOMY.md`, a v1.0
<!-- block: control-verification -->
diff/tree hashes. Use the repository's control skill
(`<repo-root>/.claude/skills/control/SKILL.md`, `pnpm control`): hidden browser
and displayless Desktop only, never `--headed` or `--allow-write`. Close owned
and displayless Desktop only, never `--headed` or `--allow-write`. Desktop
follows the build-first rule on the "Desktop running app checks" row of the
Workers table in `SKILL.md`. Close owned
sessions with `pnpm control down`; its throwaway Desktop profile stays separate
from the session's stopped profile. Relocate captures with
`../vibe/scripts/control-evidence.mjs` into private Git storage. Return captures,
Expand Down
Loading
Loading