Feature: SOP — Validation-to-Done pipeline [DUPLICATE — sop-validation already exists] #233

New issue

Open

opened 2026-03-28 19:48:42 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-03-28 19:48:42 +00:00

Contributor

Type

Feature

Lineage

Standalone — gap discovered during session where board items were moved to done before validation, then corrected. The dual Chrome DevTools + Playwright approach proved effective and should be standardized.

Repo

forgejo_admin/pal-e-platform (SOP note created via pal-e-docs MCP tools)

User Story

As a superadmin
I want a documented validation-to-done pipeline
So that no board item reaches done without verified deployment evidence

Context

Current gap: board items can be moved to done after merge without validation. This session proved a dual-browser approach:

Chrome DevTools MCP: Better for network debugging (request IDs, detailed headers, performance)
Playwright MCP: Better for DOM/accessibility tree inspection, JS evaluation, automated assertions

Both caught the same pre-existing CORS bug that manual review would have missed. Running both provides redundancy and catches different classes of issues.

Proposed pipeline (codify as SOP):

PR merged → CI pipeline passes (test/build/push)
ArgoCD syncs → new pod Running + Ready
Endpoint smoke test (curl for APIs, browser for UIs)
Dual browser validation for frontend changes:
- Chrome DevTools: console errors, network failures, screenshots
- Playwright: DOM snapshot, accessibility tree, JS evaluation, screenshots
Evidence collected → board item moved to done
If validation fails → board item stays in_progress, new bug ticket created

Column flow enforcement:

in_progress → needs_approval (QA review)
needs_approval → qa (merge approved)
qa → done (validation passes — NEVER skip this)

File Targets

New SOP note: sop-validation-pipeline in pal-e-docs
Update sop-index to include the new SOP
Consider: hook enforcement preventing done column without validation evidence

Acceptance Criteria

SOP note documents the full validation-to-done pipeline
Dual browser approach documented with tool comparison
Column flow rules documented (no skipping qa → done)
SOP linked from sop-index

Test Expectations

SOP note queryable via get_note(slug="sop-validation-pipeline")

Constraints

Documentation + convention only — no hook enforcement in this ticket
Hook enforcement for column gating is a separate follow-up

Checklist

SOP note created
No unrelated changes

project-pal-e-platform — platform infrastructure
project-pal-e-agency — agency workflows and conventions

### Type Feature ### Lineage Standalone — gap discovered during session where board items were moved to done before validation, then corrected. The dual Chrome DevTools + Playwright approach proved effective and should be standardized. ### Repo `forgejo_admin/pal-e-platform` (SOP note created via pal-e-docs MCP tools) ### User Story As a superadmin I want a documented validation-to-done pipeline So that no board item reaches done without verified deployment evidence ### Context Current gap: board items can be moved to done after merge without validation. This session proved a dual-browser approach: **Chrome DevTools MCP:** Better for network debugging (request IDs, detailed headers, performance) **Playwright MCP:** Better for DOM/accessibility tree inspection, JS evaluation, automated assertions Both caught the same pre-existing CORS bug that manual review would have missed. Running both provides redundancy and catches different classes of issues. **Proposed pipeline (codify as SOP):** 1. PR merged → CI pipeline passes (test/build/push) 2. ArgoCD syncs → new pod Running + Ready 3. Endpoint smoke test (curl for APIs, browser for UIs) 4. Dual browser validation for frontend changes: - Chrome DevTools: console errors, network failures, screenshots - Playwright: DOM snapshot, accessibility tree, JS evaluation, screenshots 5. Evidence collected → board item moved to done 6. If validation fails → board item stays in_progress, new bug ticket created **Column flow enforcement:** - `in_progress` → `needs_approval` (QA review) - `needs_approval` → `qa` (merge approved) - `qa` → `done` (validation passes — NEVER skip this) ### File Targets - New SOP note: `sop-validation-pipeline` in pal-e-docs - Update `sop-index` to include the new SOP - Consider: hook enforcement preventing `done` column without validation evidence ### Acceptance Criteria - [ ] SOP note documents the full validation-to-done pipeline - [ ] Dual browser approach documented with tool comparison - [ ] Column flow rules documented (no skipping qa → done) - [ ] SOP linked from sop-index ### Test Expectations - [ ] SOP note queryable via `get_note(slug="sop-validation-pipeline")` ### Constraints - Documentation + convention only — no hook enforcement in this ticket - Hook enforcement for column gating is a separate follow-up ### Checklist - [ ] SOP note created - [ ] No unrelated changes ### Related - `project-pal-e-platform` — platform infrastructure - `project-pal-e-agency` — agency workflows and conventions

forgejo_admin changed title from ~~Feature: SOP — Validation-to-Done pipeline with dual browser verification~~ to Feature: SOP — Validation-to-Done pipeline [DUPLICATE — sop-validation already exists]

2026-03-28 20:08:12 +00:00