Skip to content

test: rehearse full v4 release intake - #31

Merged
fomin-dima merged 1 commit into
mainfrom
test/v4-intake-rehearsal
Aug 12, 2026
Merged

fomin-dima merged 1 commit into
mainfrom
test/v4-intake-rehearsal

Conversation

@fomin-dima

Copy link
Copy Markdown
Contributor

Summary

  • add a complete synthetic v4 immutable release fixture with 20 version contexts, JSON/CSV/schema/checksum parity, and deterministic A/B rebuild verification
  • exercise the actual release validator, Astro portal, resolution artifact, route/link budgets, WCAG and no-JS browser path
  • remove a redundant v3-only validator assumption, regenerate static equivalents with the v4 identity, and expose stable context IDs in component profiles
  • document receiver-rehearsed status without changing the production v3 release or beta/not-accepted classification

Verification

  • npm run check: PASS in 648.2 s
  • Astro: 171 files, 0 diagnostics
  • Vitest: 153/153
  • v4 fixture: 20 contexts, full release validation PASS
  • v4 portal: 297 pages, 9,329 local references, 4/4 browser contracts

Boundaries

This fixture is synthetic and is not an AgroTool production fact. No private checkout, GitLab, private corpus, GitHub App, production pointer, release tag, or Pages deployment is used. Production v4 data, owner D-48/D-49 acceptance, and stable UI activation remain external gates.

@fomin-dima

Copy link
Copy Markdown
Contributor Author

Exact-head verification for 2f8f9e9:

  • local npm run check: PASS, 648.2 s; 153/153 Vitest; 171 Astro files, 0 diagnostics
  • push workflow 31588631791: SUCCESS on Ubuntu and Windows
  • pull_request workflow 31588657092: SUCCESS on Ubuntu and Windows
  • PR state: OPEN and MERGEABLE

Evidence:

No merge, Pages deployment, production v4 activation, owner acceptance, or stable UI classification was performed.

@fomin-dima
fomin-dima merged commit 032ffb9 into main Aug 12, 2026
4 checks passed
@fomin-dima

Copy link
Copy Markdown
Contributor Author

Post-merge beta verification for merge commit 032ffb9:

  • Pages workflow 31592614440: build SUCCESS (9m38s), deploy SUCCESS (41s)
  • 19/19 production routes returned HTTP 200 across RU/EN/ES/ZH and core UI/data artifacts
  • live portal-build.json: UI 3.1.0-beta.1, beta/not_accepted, source_commit exact 032ffb9
  • live data pointer remains stable 3.0.0+20260808
  • live release manifest SHA-256 b2cfd540e6d8ad7d163838dd093b365ae183440890ccc35fc7d90f4d91fd061c matches current.json
  • 20/20 production resolutions remain explicit unknown/version_context_unavailable because production v4 contexts are absent
  • synthetic v4 fixture release URL returns HTTP 404 and was not published
  • accepted_candidate_commit and acceptance_report_path remain null

Evidence: https://github.com/AgroDT/agrotool-knowledge-portal/actions/runs/31592614440
Live: https://agrodt.github.io/agrotool-knowledge-portal/ru/

No production v4 activation, owner D-48/D-49 acceptance, stable UI tag, or stable UI Release was performed.

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