Skip to content

test: verify consistent Action reporting with registry contract 0.0.6 - #3

Merged
anilkreddy merged 6 commits into
mainfrom
feat/consistent-action-reporting
Nov 15, 2026
Merged

anilkreddy merged 6 commits into
mainfrom
feat/consistent-action-reporting

Conversation

@anilkreddy

@anilkreddy anilkreddy commented Nov 15, 2026 •

Copy link
Copy Markdown
Contributor

The integration harness now consumes published notification-contract 0.0.6 and pins all five Actions to their final reviewed main commits. Actual bundled Actions verify consistent status icons, tables, complete input snapshots, confidential-value masking, warning/error detail and event/result parity.

The bounded opt-in validator proves real registry package bytes/SRI/public exports and exact source/tree/bundle/input/runner hashes before starting a local HTTPS Sandbox. Production transport and rendering are reused. External child requests are denied; Slack/Teams delivery is mocked. Existing manual workflow origin, approval, concurrency and dry-run guards remain enforced.

Validation:

  • Final exact-head hosted CI 43681104502: completed/success on a0f4c9dcb582370f8362a2610751a0e5d05dbad2.
  • Normal frozen registry install and full pnpm quality: PASS, 76 tests, zero skips; format/lint/workflow policy/public scan/audit pass, no known vulnerabilities. Actionlint and exact public input metadata checks pass.
  • Final actual five-bundle replay: PASS, 24 records in 55,745 ms from clean committed harness a4224df787c277b88deb1458eaa9162e6838967c, all producer sources clean and bound to final main refs.
  • Four isolated Sandbox runs created and removed with absence verified; both Cleanup passes: zero target mutations; Setup invalid-input case: zero network calls; 16 provider requests: mock-only.
  • Source/runner/input-metadata hashes match the retained proof. Earlier candidate and early/initial-main evidence remain explicitly historical.
  • pnpm 12 multi-document lock parsing is covered by a focused graph-selection regression. Public input-name fixtures are bound to each adopted immutable Action ref and runtime validation checks full input/masking/parity.

Final immutable Action refs:

Action Main commit
Setup 52a5a098d89f9ef2c42a234b4c3baa5d60a7a896
Build fc65ee281f39b98d2cecad36ff93d40cf055fbc2
Deploy 1af852b9a00e981da4ea13565bb18c7ce7fda27f
Cleanup 8b1786b731be8d2d3fac137cd358d2ee5488bd58
Notify abc752ead104a6e5153c5f166d04ee5e595e0ca6

Final validation report and sanitized machine evidence record the published package provenance, commands, all six final main validation/CodeQL runs and zero-result/open-alert processed analyses. Initial Build/Deploy green jobs had two/three test-generated-code findings; final test-only follow-ups resolved them. Setup used its existing OrganizationAdmin merge exception after all checks passed; no protection changed or approval was fabricated.

Implementation companions: action-kit #13, Build #8, Deploy #10, Cleanup #8, Setup #14, Notify #19. Additional test-only security PRs: Build #10, Deploy #11.

Remaining gates: new hosted workflows and live provider/SAP validation NOT RUN; production SAP eligibility evidence, operational approval, separately authorized non-production SAP testing and future Action release approval remain required. Sandbox success does not prove SAP deletion guarantees. The separately authorized package-only 0.0.6 publication is complete; no Action release, Git tag, deployment, real provider send, real SAP operation or production cleanup enablement occurred. Cleanup remains dry-run.

Final coordinated registry validation

All seven original PRs are merged. The dependency-publication/adoption blocker is resolved. Each Action uses actual registry notification-contract 0.0.6 with a frozen reproducible lockfile and regenerated committed bundle. No candidate flag or local package link is required.

Final merged harness main ebc443e4f7b07f17a2a219c0b7214d25d4ad0d46 passed CI 43681200918.

Final registry-installed validation report and sanitized exact-source/bundle evidence: 76 harness tests and the final 24-record five-action integration replay PASS. Four isolated local Sandbox runs were removed with absence verified; Cleanup performed zero target mutations. All 16 provider requests were strict mocks.

The final processed security review found five generated-code alerts in new Build/Deploy test preloads despite green workflow jobs. Narrow test-only follow-ups Build #10 and Deploy #11 removed data-to-code interpolation, passed full validation, and resolved all findings. Production source and bundle hashes are unchanged. Setup used its existing OrganizationAdmin merge exception after all six native jobs, quality and CodeQL passed; no branch rules were changed.

Only the requested shared package was published. No Git tags, Action releases, deployments, hosted Sandbox dispatches, live notifications or real SAP operations occurred. Production cleanup eligibility and separately authorized live/release validation gates remain closed.

Companions: action-kit #13, notify #19, ccv2-build #8, ccv2-deploy #10, setup-commercekit #14, ccv2-build-cleanup #8, action-integration-tests #3.

@anilkreddy anilkreddy changed the title test: validate consistent reporting across candidate Actions test: verify consistent Action reporting with registry contract 0.0.6 Nov 15, 2026
@anilkreddy
anilkreddy marked this pull request as ready for review November 15, 2026 05:27
@anilkreddy
anilkreddy merged commit ebc443e into main Nov 15, 2026
1 check passed
@anilkreddy
anilkreddy deleted the feat/consistent-action-reporting branch November 15, 2026 05:28
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