HERO

2026-02-18-qa-routine-after-merge

One-line value: Use 2026-02-18-qa-routine-after-merge as an execution-ready playbook, not a note.

When to use: Use this page when you need to execute this workflow in one focused session.

QUICK RESULT

If you only do one thing → complete the first checklist pass and publish one usable draft/output today.

ACTION CHECKLIST

• [ ] Clarify the exact output and success metric before starting.
• [ ] Gather required inputs from one trusted source only.
• [ ] Execute the workflow in sequence without adding side tasks.
• [ ] Run one quality check and fix the highest-risk issue first.
• [ ] Save the final result with a short reuse note.

EXAMPLE / DEMO

Before: Notes are scattered and decisions are unclear.

After: Inputs are structured, steps are executed, and the output is ready to use immediately.

WHY IT WORKS

• Converts vague intent into an explicit sequence.
• Emphasizes shipping one validated result fast.
• Creates repeatability for future runs.

NEXT ACTION

• Run this checklist on one live task now; keep scope to a single measurable outcome.

Source notes (kept for context)

Minimum checks

After merging a PR to main, verify:

1. Cloudflare Pages build status is Success

2. Open the changed URL(s)

3. Check CSS is loaded (if not, suspect asset path or cache)

4. Confirm Posts list includes new items

5. Confirm RSS includes new items (when applicable)

When to stop and fix

Stop adding new content if:

• Build fails

• A core page returns 404

• The Posts list or RSS is empty unexpectedly