task-observer: qa-test updates from 2026-05-11

[divad12]

Target

skill: .agents/skills/qa-test/SKILL.md

Observations addressed

• Observation 011 (journology/log.md): Shakedown Fixes Need Persisted-Data Invariant Checks → changed: added "Persisted-Data Invariant Checks" section with guidance to run a focused DB/store check after browser flows that write or generate data
• Observation 014 (journology/log.md): Shakedown Triage Should Treat Optimistic Flicker As A Bug Class → changed: added "Bug Severity Triage" section ranking interaction timing bugs (flicker, stale cache, revert-then-correct) as highest priority FAILs
• Observation 018 (journology/log.md): Product Shakedown Needs Realistic Scale And Neglected Surfaces → changed: added "Scale and Coverage" section advising periodic scale scenarios and neglected-surface audits

---

Generated by Claude Code

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 777a1accac

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Remove DB invariant checks from browser-only subagent prompt

This new instruction asks the QA subagent to verify persisted data invariants in the DB, but this skill defines the subagent as Playwright-only with no source or backend access (see earlier constraints in this same file). As written, the subagent cannot execute these checks, so runs will either silently skip required verification or report unverifiable FAILs, which makes the workflow unreliable for exactly the scenarios this section targets.

Useful? React with 👍 / 👎.