Automated release verification is recorded
Automated release checks exist and have passed for recent Slop Filter work, while live signed-in checks remain separate.
Depends on: E1-M2
Epic E3
Verified continuous delivery
Software changes are not treated as delivered until the right automated and browser checks have run and their limits are stated.
Purpose
The factory can combine source changes, run validation and record where synthetic tests stop short of live compatibility.
Current status
Partial. Slop Filter has strong automated checks, but PR #121 explicitly left installed signed-in Brave verification undone.
Milestones
Browser verification is required before delivery claims
The process distinguishes synthetic checks, temporary Chromium release checks and installed signed-in Brave checks.
Depends on: E3-M1
Evidence
PR #116: explicit usage-counter reset
Merged on 2026-10-11 with release verification, background tests and experience UI tests recorded in the PR body.
Open sourcePR #121: feedback personalisation stack
Merged on 2026-10-11 with automated verification. The PR body states signed-in Brave and live provider checks were not performed for this delivery.
Open sourceLinkedIn Slop Filter main at 8984c80
Local main and GitHub main matched after cleanup. README, AGENTS.md and recent pull requests were inspected.
Open sourceRisks and open questions
Risks
- A passing build can hide broken navigation, inaccessible maps or missing assets.
- Synthetic browser fixtures can be mistaken for live product evidence.
Open questions
- Which checks should be mandatory for each class of change?
- How should live checks be recorded without leaking private data?
Linked Wardley components
- Git
- GitHub coordination
- Testing frameworks
- Deployment infrastructure
Next steps
- Use Playwright, data validation and screenshots for this website MVP.