HERO

2026-02-18-smoke-checks-after-deploy

One-line value: Use 2026-02-18-smoke-checks-after-deploy 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)

Why

After a successful deployment, changes can still look "missing" due to caching or asset routing issues.

Minimal checks

1. Open the changed pages (no 404).
2. Open /assets/site.css: HTTP 200 and the response is CSS (not HTML/redirect).
3. Confirm the CSS marker string is present (example: automation-kb).
4. Open /feeds/posts.xml: HTTP 200 and new items are included.

Notes

If the site looks unstyled but pages load, CSS delivery is the first suspect.