Skip to content

parts-verdict: read the issue-list verdict (act@5, /4) and publish draft panels - #378

Merged
firejune merged 4 commits into
mainfrom
jinni/377-parts-verdict-read-the-issue-list-verdic
Nov 9, 2026
Merged

firejune merged 4 commits into
mainfrom
jinni/377-parts-verdict-read-the-issue-list-verdic

Conversation

@firejune

@firejune firejune commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Closes #377.

What changes

  • decodeReviewAct accepts rig-review/act@5 for parts-verdict: {verdict, issues[], words}. Each issue's parts are bound to source.parts.images (role part, parts/<name>.png, matching sha256). Ids and part names must be unique, and approved holds exactly when there are zero issues. act@2 is unchanged.
  • assertPartsActSource: for act@5, every issue part name must be in the bound manifest (inclusion). The act@2 equality check is unchanged.
  • CLI route: decodePartsRead reads rig-review-parts-verdict/4 (issues, no per-part rows). For /4, partsVerdictNames returns the issue part names de-duplicated in issue order. An act receipt's evidence spec is the act's own schema.
  • prepareDraftManifest writes panels: rig-review/panels@1 (parts.list / parts.canvas / parts.layers / parts.issues + act.submit).

Out of scope

Review-side writers, fix-ledger and next.

Verification

Command Exit Result
bun test tests/parts-verdict-v2.test.ts tests/parts-act.test.ts 0 24 pass, 0 fail
bun run typecheck 0 0 errors
bun run lint 0 0 errors

🤖 Generated with Claude Code

Co-Authored-By: Jinni <342598851+fj-jinni[bot]@users.noreply.github.com>
@firejune

firejune commented Nov 9, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-09T16:09:16.649053Z bba716b Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: bba716bc44

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/job-publication.ts
animations: [], checkpoints: [], authoring: files.filter(file => /\/(rig|motion|mesh_report)\.json$/.test(String(file.path)))
.map(file => ({ label: String(file.path).split('/').at(-1), path: file.path })) };
.map(file => ({ label: String(file.path).split('/').at(-1), path: file.path })),
panels: { schema: 'rig-review/panels@1', left: ['parts.list'], stage: ['parts.canvas'], toolbar: ['parts.layers'], side: ['parts.issues', 'act.submit'] } };

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Preserve compatibility with retained draft manifests

For a project whose draft was published before this change, reopening it in a new job or reconciling a pending publication now fails: adding panels changes the generated manifest bytes, while the existing-file comparison below refuses the original review-draft-<id>.json with JOB_PUBLICATION_INVALID. Both openDraftPublication and publishPending in src/job-host.ts reach this preparation path, so an otherwise unchanged retained draft becomes unpublishable, and restoring its original bytes cannot resolve the refusal. Accept the previous manifest format or provide a migration that preserves existing publication bindings rather than unconditionally requiring the new bytes. The repository's contract-date rule also requires earlier records to remain usable rather than acquiring a new refusal.

AGENTS.md reference: AGENTS.md:L72-L78

Useful? React with 👍 / 👎.

firejune and others added 2 commits November 10, 2026 01:09
Co-Authored-By: Jinni <342598851+fj-jinni[bot]@users.noreply.github.com>
…377)

Co-Authored-By: Jinni <342598851+fj-jinni[bot]@users.noreply.github.com>
@firejune

firejune commented Nov 9, 2026

Copy link
Copy Markdown
Contributor Author

Codex P1 (retained draft manifests without panels) adopted: a retained legacy manifest will be accepted unchanged, and new publications write panels. The fix follows on this branch.

Co-Authored-By: Jinni <342598851+fj-jinni[bot]@users.noreply.github.com>
@firejune
firejune merged commit f16c954 into main Nov 9, 2026
1 check passed
@firejune
firejune deleted the jinni/377-parts-verdict-read-the-issue-list-verdic branch November 9, 2026 16:29
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.

parts-verdict: read the issue-list verdict (act@5) and publish the parts panel composition

1 participant