task-observer: qa-test updates from 2026-05-25#35
Open
divad12 wants to merge 1 commit into
Open
Conversation
Two additions from shakedown observations: - Treat optimistic-update flicker / revert-then-correct as FAILs, not CONCERNs - After browser PASS, run a focused data integrity check for features that generate or persist data (browser success does not prove data quality)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Target\nskill: .agents/skills/qa-test/SKILL.md\n\n## Observations addressed\n- Observation 11 (journology/log.md): Shakedown fixes need persisted-data invariant checks → changed: added step 4 "Verify persisted state" — for features that generate or persist data, browser PASS does not guarantee data quality; run a focused integrity check (DB query, API read, file check) after the flow\n- Observation 14 (journology/log.md): Shakedown triage should treat optimistic flicker as a bug class → changed: added severity note in step 3 — treat optimistic-update freshness, visible flicker, stale cache, and revert-then-correct behavior as FAILs (not CONCERNs) because they break user trust in saved work
Generated by Claude Code