Skip to content

build: refresh v8-runner master snapshot - #419

Merged
zeegin merged 6 commits into
mainfrom
codex/v8-runner-master-refresh
Aug 10, 2026
Merged

build: refresh v8-runner master snapshot#419
zeegin merged 6 commits into
mainfrom
codex/v8-runner-master-refresh

Conversation

@zeegin

@zeegin zeegin commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Результат

  • Unica переключена на immutable release v8-runner-nightly-master-build.2, собранный из upstream commit 7ce1b062843d86644fe55741dbe0ee79f7ca767d.
  • Toolchain source PR: IngvarConsulting/unica-toolchain#8.
  • Трёхплатформенный build/provenance run: 31372368557.
  • Публичная MCP-поверхность и версия Unica не меняются.

Проверенные assets

Target SHA-256
darwin-arm64 2a92802edf5a73d5fdcc42cc61b1abbbc95226cd75bdfe3c50407b13eb8da590
linux-x64 70690845033ab41abe4ed0a6af206f7022cd1481ae408748b7de03c56ced0b6b
win-x64 191a3d7c930007377238dda0543d1e42cc1a1bd4b209736d54fd41c0ffaac32e

Release скачан повторно: все 10 ожидаемых файлов присутствуют, checksum-файлы совпадают, provenance каждого target указывает на тот же commit и Rust 1.95.0. Native macOS --version и build --help прошли.

Рассмотренный upstream delta

В 36-коммитном диапазоне применены как часть бинарного refresh:

  • IBCMD data isolation;
  • prepared-infobase test --no-build availability без нового MCP-аргумента;
  • strict platform resolution, документированный как v8project.yaml config;
  • Windows directory publication/fsync repair;
  • Windows detached stdio isolation.

Отложены отдельными контрактами:

  • public noBuild в unica.runtime.execute;
  • private CDFI/shadow publication: issue #30, PR #39;
  • source-set dependency graph: issue #32, PR #50;
  • удаление full-only source-sync guard.

Applied mode=incremental|partial остаётся fail-closed.

Проверка

  • python -m unittest discover -s tests/ci: 615 passed, 3 skipped;
  • cargo fmt --all -- --check;
  • cargo clippy --workspace --all-targets --locked -- -D warnings;
  • cargo test --workspace --locked;
  • exact guard tests applied incremental/full-only;
  • build.2 consumer download and v8-runner contracts: version/help, partial-load BOM+CRLF+Cyrillic path, bounded external EPF — passed.

Локальный общий check-tool-contracts.py дважды упёрся в 120-секундный timeout неизменённого rlm-bsl-index index build. RLM lock и bytes не менялись относительно main; v8-runner-specific subset из того же скрипта прошёл отдельно. GitHub checks остаются обязательным финальным gate.

Summary by CodeRabbit

  • Documentation

    • Documented strict platform tooling configuration, fail-closed version validation, and bounded utility discovery.
    • Added approved refresh plans and recorded provenance, supported platforms, integration decisions, and deferred items.
  • Updates

    • Refreshed locked runner releases for Darwin, Linux, and Windows with updated source metadata and integrity checks.
  • Tests

    • Updated provenance expectations and expanded documentation contract checks for strict platform configuration and fail-closed behavior.

@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@zeegin, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 24 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 9a3f7c43-229e-4c60-945f-4bdb34913b3b

📥 Commits

Reviewing files that changed from the base of the PR and between 2f4421a and 23f2277.

📒 Files selected for processing (1)
  • tests/ci/test_unica_skills.py
📝 Walkthrough

Walkthrough

The PR documents a v8-runner refresh to upstream commit 7ce1b062..., updates the locked three-platform build.2 release metadata and provenance, adds strict platform-resolution documentation, and extends related CI contract expectations.

Changes

v8-runner master refresh

Layer / File(s) Summary
Refresh scope and delivery plan
docs/design/..., docs/plans/...
Defines the target commit, immutable build.2 release, platform matrix, preserved contracts, toolchain preparation, and delivery constraints.
Release evidence and lock integration
docs/plans/..., plugins/unica/third-party/tools.lock.json, docs/provenance/reviews/..., tests/ci/test_skill_provenance.py
Specifies release verification and records the refreshed source commit, asset tag, platform checksums, and provenance evidence.
Strict platform resolution contracts
docs/plans/..., plugins/unica/references/..., plugins/unica/skills/..., tests/ci/test_unica_skills.py
Documents tools.platform.strict, path and version behavior, canonical utility selection, and fail-closed resolution. Updates documentation contract tests.
Validation and publication workflow
docs/plans/...
Defines packaged-consumer checks, repository validation, source-sync safeguards, and pull-request publication steps.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the main change: refreshing the v8-runner master snapshot.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches 💡 1
📝 Generate docstrings 💡
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/v8-runner-master-refresh

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai 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.

Actionable comments posted: 5

🧹 Nitpick comments (1)
tests/ci/test_unica_skills.py (1)

2131-2133: 🎯 Functional Correctness | 🔵 Trivial | ⚡ Quick win

Check the strict-platform contract in each required document.

The test concatenates five documents before checking three independent substrings. Strict guidance can be removed from one required reference while another document keeps the test passing. Assert the complete strict-platform contract separately for plugins/unica/references/tooling/v8project.md and plugins/unica/skills/v8-runner/references/config-and-backends.md.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@tests/ci/test_unica_skills.py` around lines 2131 - 2133, Update the test
around the combined v8_runner_docs assertions to validate the complete
strict-platform contract independently in both required documents:
plugins/unica/references/tooling/v8project.md and
plugins/unica/skills/v8-runner/references/config-and-backends.md. Assert
tools.platform.strict, strict: true, and fail-closed for each document rather
than relying on concatenated content.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/design/2026-08-10-v8-runner-master-refresh-design.md`:
- Around line 35-37: В разделе, описывающем порядок публикации, замените
формулировку «Порядок не обращается» на «Порядок не меняется» и явно
сформулируйте правило: Unica не должна ссылаться на ещё не существующие или
непроверенные байты. Сохраните утверждения о неизменности опубликованных
release/tag и использовании следующей build revision при ошибке выпуска.

In `@docs/plans/2026-08-10-v8-runner-master-refresh.md`:
- Around line 132-158: Use a single verified workflow run identity throughout
Step 2 instead of selecting the first result from gh run list. Dispatch the
workflow with immutable ref "$merge_sha" or capture the exact dispatched run ID,
verify its headSha equals merge_sha, then pass that run ID directly to gh run
watch.
- Around line 16-18: Separate package and tool version references in
docs/plans/2026-08-10-v8-runner-master-refresh.md lines 16-18 by identifying
0.5.1 as the v8-runner version and stating Unica’s package version separately,
using package metadata as authoritative. In
docs/design/2026-08-10-v8-runner-master-refresh-design.md lines 9-13, replace
Unica v0.11.0 with the current package version or explicitly label v0.11.0 as
historical context.
- Around line 180-189: Update the release verification commands in the
documented shell flow so every check fails closed: enable fail-fast behavior for
the checksum loop and validate each provenance file independently with jq,
stopping immediately on the first checksum or provenance mismatch rather than
allowing a later successful command to determine the final status.

In `@plugins/unica/skills/v8-runner/references/config-and-backends.md`:
- Line 37: Update the host-specific sentence in the skill prose to use
mcp__plugin_unica_unica__unica_runtime_execute instead of unica.runtime.execute.
Preserve canonical unica.runtime.execute references in JSON-RPC examples and
public contract statements.

---

Nitpick comments:
In `@tests/ci/test_unica_skills.py`:
- Around line 2131-2133: Update the test around the combined v8_runner_docs
assertions to validate the complete strict-platform contract independently in
both required documents: plugins/unica/references/tooling/v8project.md and
plugins/unica/skills/v8-runner/references/config-and-backends.md. Assert
tools.platform.strict, strict: true, and fail-closed for each document rather
than relying on concatenated content.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 948d4138-ad3b-4958-8520-4b774cd70bcd

📥 Commits

Reviewing files that changed from the base of the PR and between 282dd98 and ec9ff78.

📒 Files selected for processing (8)
  • docs/design/2026-08-10-v8-runner-master-refresh-design.md
  • docs/plans/2026-08-10-v8-runner-master-refresh.md
  • docs/provenance/reviews/2026-08-10-v8-runner-master-refresh.json
  • plugins/unica/references/tooling/v8project.md
  • plugins/unica/skills/v8-runner/references/config-and-backends.md
  • plugins/unica/third-party/tools.lock.json
  • tests/ci/test_skill_provenance.py
  • tests/ci/test_unica_skills.py

Comment thread docs/design/2026-08-10-v8-runner-master-refresh-design.md Outdated
Comment thread docs/plans/2026-08-10-v8-runner-master-refresh.md
Comment thread docs/plans/2026-08-10-v8-runner-master-refresh.md
Comment thread docs/plans/2026-08-10-v8-runner-master-refresh.md Outdated
Comment thread plugins/unica/skills/v8-runner/references/config-and-backends.md
@zeegin

zeegin commented Aug 10, 2026

Copy link
Copy Markdown
Contributor Author

Review follow-up in 2f4421a4: test_v8_runner_docs_track_current_v8project_contract now asserts the complete strict-platform contract independently in both required documents. The current documents already satisfied the stronger assertions, so this is regression-coverage hardening rather than a reproduced content defect.

@zeegin zeegin added this to the v0.12 milestone Aug 10, 2026
@zeegin
zeegin merged commit d7818b5 into main Aug 10, 2026
21 checks passed
@zeegin
zeegin deleted the codex/v8-runner-master-refresh branch August 10, 2026 10:09
@coderabbitai coderabbitai Bot mentioned this pull request Aug 12, 2026
3 tasks
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.

1 participant