Skip to content

Publish AWF multi-subject provenance bundle - #11342

Merged
lpcox merged 3 commits into
mainfrom
copilot/investigate-awf-install-acceleration
Nov 9, 2026
Merged

lpcox merged 3 commits into
mainfrom
copilot/investigate-awf-install-acceleration

Conversation

Copilot AI commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

This investigation asks whether repeated online attestation lookups can be reduced without weakening AWF’s release identity, checksum, subject, signer, issuer, or runner checks. This change publishes the release workflow’s existing multi-subject provenance bundle as an input for downstream verification.

  • Release asset: Export the attestation action’s bundle and include it in the GitHub Release:
    cp "$BUNDLE_PATH" release/awf-release-provenance.sigstore.jsonl
    It is generated after checksums and attestation, so it is not included in its own checksums or subject set.
  • Trust contract: Document that consumers must retain the independently pinned manifest digest, expected tag binding, required subject digests, and existing signer, issuer, and runner restrictions.
  • Consumer follow-up: The measured installer lives in github/gh-aw; it must adopt bundle-based verification before installation latency can improve. This change leaves its verification order unchanged and makes no latency claim.

Co-authored-by: lpcox <15877973+lpcox@users.noreply.github.com>
Copilot AI changed the title [WIP] Investigate accelerating authenticated AWF installation without weakening provenance checks Publish AWF multi-subject provenance bundle Nov 9, 2026
Copilot AI requested a review from lpcox November 9, 2026 03:11
@lpcox
lpcox marked this pull request as ready for review November 9, 2026 03:14
Copilot AI dynamic review requested due to automatic review settings November 9, 2026 03:14

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟡 Changes recommended

The local Step type lacks id and env fields, causing TS2339 errors that prevent the provenance test suite from running under the repository’s ts-jest configuration.

1 open issue
What changed in this PR

Publishes AWF’s existing multi-subject provenance bundle as a release asset for downstream verification. Consumer adoption remains separate; this PR does not change installer verification order or claim latency improvements.

Changes:

  • Exports and uploads the attestation bundle after checksum generation and attestation.
  • Adds assertions for bundle wiring, publication order, and release inclusion.
  • Documents the bundle’s trust requirements and exclusion from its own checksums and subjects.
File Description
scripts/​ci/​release-bootstrap-provenance.test.ts Adds assertions for provenance bundle publication.
docs/​releasing.md Documents the new asset and consumer verification requirements.
.github/​workflows/​release.yml Copies the attestation bundle and includes it in the GitHub Release.

Review effort: Max (auto)

Comment on lines +418 to +419
expect(steps[attest].id).toBe('attest_awf_release');
expect(steps[bundle].env?.BUNDLE_PATH).toBe('${{ steps.attest_awf_release.outputs.bundle-path }}');

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Added optional id and env fields to the local Step type in 873f37d.

@lpcox

lpcox commented Nov 9, 2026

Copy link
Copy Markdown
Collaborator

@copilot address review feedback

Co-authored-by: lpcox <15877973+lpcox@users.noreply.github.com>

Copilot AI commented Nov 9, 2026

Copy link
Copy Markdown
Contributor Author

@copilot address review feedback

Addressed the review feedback in 873f37d by adding optional id and env fields to the test's local workflow Step type.

@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

⏳ Copilot review left inline comments.

@copilot To proceed:

  1. Ask @copilot to address the review feedback (reply to this comment or the review thread)
  2. Once the fix is pushed, add the ready-for-aw label to trigger agentic CI smoke tests

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Documentation Preview

Documentation has been built for this PR.

Download preview artifact

To view locally:

  1. Download the docs-preview-pr-11342 artifact from the workflow run
  2. Unzip and open index.html in your browser

Built from commit 83bca16

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

⚠️ Coverage Regression Detected

This PR decreases test coverage. Please add tests to maintain coverage levels.

Overall Coverage

Metric Base PR Delta
Lines 93.81% 93.81% ➡️ +0.00%
Statements 92.36% 92.35% 📉 -0.01%
Functions 93.02% 93.02% ➡️ +0.00%
Branches 86.70% 86.69% 📉 -0.01%
📁 Per-file Coverage Changes (2 files)
File Lines (Before → After) Statements (Before → After)
src/nvx/one-shot-process.ts 84.0% → 81.5% (-2.47%) 76.8% → 74.7% (-2.11%)
src/commands/main-action.ts 91.7% → 92.0% (+0.25%) 91.4% → 91.7% (+0.24%)

Coverage comparison generated by scripts/ci/compare-coverage.ts

@lpcox
lpcox enabled auto-merge (squash) November 9, 2026 03:50
@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

🚀 Security Guard has started processing this pull request

@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

📡 Smoke OTel Tracing completed. All tracing scenarios validated. ✅

📡 OTel tracing validated by Smoke OTel Tracing

@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

✅ Smoke Copilot BYOK completed. Copilot BYOK mode operational. 🔓

🔑 BYOK report filed by Smoke Copilot BYOK

@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

🛡️ Smoke Copilot Network Isolation confirmed the egress allowlist is enforced. ✅

🛡️ Egress verdict from Smoke Copilot Network Isolation

@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

✅ Build Test Suite completed successfully!

Generated by Build Test Suite for #11342

@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Smoke Cloud Hypervisor completed. Cloud Hypervisor + Copilot passed.

Cloud Hypervisor + Copilot smoke test by Smoke Cloud Hypervisor

@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

✅ Smoke Claude passed

Generated by Smoke Claude for #11342

@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

✨ The prophecy is fulfilled... Smoke Codex has completed its mystical journey. The stars align. 🌟

🔮 The oracle has spoken through Smoke Codex

@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Chroot tests passed! Smoke Chroot - All security and functionality tests succeeded.

Tested by Smoke Chroot

@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

🔌 Smoke Services — All services reachable! ✅

🔌 Service connectivity validated by Smoke Services

@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

📰 VERDICT: Smoke Copilot has concluded. All systems operational. This is a developing story. 🎤

📰 BREAKING: Report filed by Smoke Copilot

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

🏗️ Build Test Suite Results

Ecosystem Project Build/Install Tests Status
Bun elysia ✅ 1/1 passed ✅ PASS
Bun hono ✅ 1/1 passed ✅ PASS
C++ fmt ✅ N/A ✅ PASS
C++ json ✅ N/A ✅ PASS
Deno oak N/A 1/1 passed ✅ PASS
Deno std N/A 1/1 passed ✅ PASS
.NET hello-world ✅ N/A ✅ PASS
.NET json-parse ✅ N/A ✅ PASS
Go color ✅ pass ✅ PASS
Go env ✅ pass ✅ PASS
Go uuid ✅ pass ✅ PASS
Java gson ❌ 0/0 ❌ FAIL
Java caffeine ❌ 0/0 ❌ FAIL
Node.js clsx ✅ pass ✅ PASS
Node.js execa ✅ pass ✅ PASS
Node.js p-limit ✅ pass ✅ PASS
Rust fd ✅ 1/1 passed ✅ PASS
Rust zoxide ✅ 1/1 passed ✅ PASS

Overall: 7/8 ecosystems passed — FAIL

Java failure: mvn compile failed. The default ~/.m2 repository was not accessible (LocalRepositoryNotAccessibleException). A retry with a temporary local repo failed with PluginResolutionException: it could not download maven-resources-plugin:pom:3.4.0 from Maven Central through the squid-proxy:3128 proxy (internal_error). The settings.xml proxy host squid-proxy does not appear to be reachable from this environment.

.NET note: the first attempt crashed on a missing /run/user/1001. It passed after I set XDG_RUNTIME_DIR to a temp directory.

Generated by Build Test Suite for #11342 · copilot · auto (Claude Sonnet 5.5) · ~26 AIC · ⊞ 5.9K · ◷
Add label ready-for-aw to run again

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Smoke (Copilot): PR "[WIP] Define trusted service-proxy support for LLM secret headers"

  • GitHub MCP ✅
  • GitHub.com connectivity ✅
  • File write/read ✅

Overall: PASS — @Copilot @lpcox

📰 BREAKING: Report filed by Smoke Copilot
Add label ready-for-aw to run again

@github-actions github-actions Bot added the smoke-copilot-network-isolation Copilot network-isolation egress smoke test label Nov 9, 2026
@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

EGRESS_RESULT allow=pass deny=pass

  • ✅ Allowed domain (api.github.com): HTTP 200
  • ✅ Blocked domain (example.com): blocked (SNI guard cert rejected)

Overall: PASS — cc @lpcox

🛡️ Egress verdict from Smoke Copilot Network Isolation
Add label ready-for-aw to run again

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

OTEL smoke test

  • ✅ S1 Module loading: otel.js exports startRequestSpan, setTokenAttributes, setBudgetAttributes, endSpan, endSpanError, routerCallTracing, shutdown, isEnabled, and others.
  • ✅ S2 Tests: 3 OTEL suites passed, 75/75 tests.
  • ✅ S3 Env forwarding: GITHUB_AW_OTEL_TRACE_ID and GITHUB_AW_OTEL_PARENT_SPAN_ID are forwarded in env-passthrough.ts and api-proxy-env-config.ts. The OTLP endpoint and headers are also forwarded to the api-proxy.
  • ✅ S4 Token tracker: the onUsage hook exists in token-tracker-http.js.
  • ✅ S5 Diagnostics: otel.jsonl exists with 1 line. I did not inspect the exported spans in detail.

📡 OTel tracing validated by Smoke OTel Tracing
Add label ready-for-aw to run again

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Smoke Test: Copilot BYOK (Direct) Mode ✅

Status: PASS

All tests verified:

  • ✅ GitHub MCP connectivity
  • ✅ GitHub.com HTTP 200
  • ✅ File write/read
  • ✅ BYOK inference via api-proxy → api.githubcopilot.com

Running in direct BYOK mode (COPILOT_PROVIDER_API_KEY).

🔑 BYOK report filed by Smoke Copilot BYOK
Add label ready-for-aw to run again

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Cloud Hypervisor + Copilot smoke test

  1. Merged PR lookup: PASS
  2. github.com connectivity: PASS (HTTP 200)
  3. File write/read: PASS
  4. example.com blocked: PASS (HTTP 000)

Overall: PASS

Cloud Hypervisor + Copilot smoke test by Smoke Cloud Hypervisor
Add label ready-for-aw to run again

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Chroot Version Comparison

Runtime Host Version Chroot Version Match?
Python Python 3.12.16 Python 3.12.16 ✅ YES
Node.js v24.22.2 v2.98.0 ❌ NO
Go go1.22.12 go1.22.12 ✅ YES

Node.js doesn't match: the chroot reported v2.98.0 against host v24.22.2. The smoke-chroot label was not added.

Tested by Smoke Chroot
Add label ready-for-aw to run again

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Smoke Test: Claude Engine Validation

  • API status: ✅ PASS
  • GitHub check: ✅ PASS
  • File status: ✅ PASS

Overall result: PASS

Generated by Smoke Claude for #11342 · claude · haiku45 · ~35 AIC · ⊞ 6.3K · ◷
Add label ready-for-aw to run again

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Smoke test:

  • ci: parallelize native release builds and packaging ✅
  • feat: maintain Decisions compatibility in the canonical model catalogue ✅
  • GitHub PR details ✅
  • Playwright title check ❌
  • File write/read ✅
  • Build AWF ✅

Overall status: FAIL

🔮 The oracle has spoken through Smoke Codex
Add label ready-for-aw to run again

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Services smoke test: ✅ Redis PONG, ✅ pg_isready accepting connections, ✅ SELECT 1 → 1. Overall: PASS

🔌 Service connectivity validated by Smoke Services
Add label ready-for-aw to run again

@lpcox
lpcox merged commit f30cc2a into main Nov 9, 2026
132 of 134 checks passed
@lpcox
lpcox deleted the copilot/investigate-awf-install-acceleration branch November 9, 2026 04:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Investigate accelerating authenticated AWF installation without weakening provenance checks

3 participants