docs(phase4.5f): Phase 4.5 cluster ✅ DONE + add Live UI spot-check (Section I) rule#101
Merged
Merged
Conversation
… UI spot-check requirement PHASE_STATUS.md: row 4.5 → ✅ DONE (PRs #89/#90/#91 + #93 + #95 + #97 + #100). 4.5f ✅ DONE block added with production verified snapshot (run #51, commit e57f09c, warm-cache 5m14s), 5 schema field inventory, rank-source contract restatement, and live UI Section I spot-check results. Phase 4.5 timeline summary table 4.5f row flipped ⚪ → ✅; 4.5e marked deferred-until-after-tag. SKILL.md: schema versions table appended with 0.8.0-phase4.5f row covering the minor-bump rationale (5 new fields + new UI surface + semver-coupled tag), the FLAG_WEIGHTS additive design, and the Rule-16 rank-source contract. WORKFLOW.md: 4.5f task list [ ] → [x] for all sub-tasks. Captures module-location decision (manipulation_index.py kept separate from composite.py to keep compute_composite pure-pillar), 4.5e reserved-slot weights, and the new Section I spot-check result. Tag v1.2.0-phase4.5 is the only [ ] remaining — cut after this docs PR merges. CLAUDE.md: Phase status section refreshed for 4.5f complete. Schema 0.7.1-phase4g → 0.8.0-phase4.5f; defense layer 16 → 17; next deliverable: tag v1.2.0-phase4.5 → then 4.5e. Verification ladder amended with the new "after workflow_dispatch green" rule pointing at the Section I spot-check (REQUIRED 2026-05-17). .claude/skills/verify-production-output/SKILL.md: new Section I (Live UI visual spot-check via Playwright) added to the A-H table + a long-form section covering the 4-ticker matrix (worst- case stack, mid-band, boundary, top-clean), per-ticker capture template (card-present, headline, band-label, components, penalty, screenshot), the design-system regression mode this catches (the PR #70 invisible-dark-text-on-forced-light-bg class), and the sandbox / browser-version caveats (executable_path override + ignore_https_errors=True). Production verified: commit e57f09c / run #51 (workflow 25983422610) / 502 stocks / 856 offline tests / warm-cache 5m14s. Phase 4.5 cluster (4.5a-4.5f) complete; 6 sub-PRs landed in 1 calendar day after the cluster kickoff on 2026-05-16. Tag v1.2.0-phase4.5 is the next action after this merges. https://claude.ai/code/session_015649aRyi2bvciQYZVNACd2
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
Summary
Triple-doc lockstep bump for Phase 4.5f + Phase 4.5 cluster completion plus a new workflow rule formalizing the Playwright live-UI spot-check that surfaced during 4.5f verification.
e57f09cb/ 5m14s), 5-field schema inventory, rank-source contract restatement, and live UI Section I results. Phase 4.5 timeline summary table 4.5f row flipped ⚪ → ✅.0.8.0-phase4.5frow covering the minor-bump rationale (5 fields + new UI surface + semver-coupled tag), the additiveFLAG_WEIGHTSdesign, and the Rule 16 rank-source contract.[ ]→[x]for all sub-tasks; tagv1.2.0-phase4.5is the only[ ]left, cut after this merges.0.7.1-phase4g→0.8.0-phase4.5f; defense layer 16 → 17). Verification ladder amended with the new "afterworkflow_dispatchgreen" rule..claude/skills/verify-production-output/SKILL.md— new Section I (Live UI visual spot-check via Playwright) added to the A-H table + long-form section: 4-ticker matrix, capture template, design-system regression mode this catches (PR ui(badge): unify recommendation badge with sector/MoS outlined-light pattern #70 invisible-dark-text class), sandbox / browser-version caveats (executable_pathoverride +ignore_https_errors=True).Why Section I
The static A-H scan reads JSON only. Whenever a schema bump or new UI surface lands, the JSON contract can still pass A-H while the live page fails to render — wrong type binding, missed
== nullvs=== nullguard for legacy fields, or a class typo. PR 4.5f's user-requested visual verification surfaced this gap. Going forward, everyworkflow_dispatchthat lands a schema bump or new component onmainruns both the existing A-H scan and Section I.Production-verified snapshot (Phase 4.5f)
e57f09cb(chore: update rankings 2026-05-17)25983422610)0.8.0-phase4.5f✅manipulation_indexpopulatedmanipulation_indexrollup)@networkLive UI spot-check results (Section I — first run of the new rule)
Playwright against
https://quantrank.vercel.app:All match backend predictions exactly. No design-system regressions; outlined-light Pattern B holds across all 3 bands.
Test plan
ruff check .— cleanmetadata.json::git_commit(e57f09cb... actuallyb1588b2ab32361db19f7efe8bed6e6e535275eeeis what compute ran against;e57f09cbis the chore-commit landed on main)compute/config.SCHEMA_VERSION(0.8.0-phase4.5f)pytest --collect-only -q(856)compute/,frontend/,tests/changed — pure docs + workflow-rule PRNext action after merge
Cut tag
v1.2.0-phase4.5+ GitHub Release annotation pointing at the post-docs-bump commit. Then loop back to 4.5e (Form 4 insider clustering — reserved-slot weights already in place; integration is a one-line uncomment inFLAG_WEIGHTS+ the parser + 2 new annotates).https://claude.ai/code/session_015649aRyi2bvciQYZVNACd2
Generated by Claude Code