Skip to content

chore(requirements): sync with GitHub project board 2026-07-18 - #865

Merged
SarahLittlejohn merged 3 commits into
masterfrom
chore/requirements-sync-2026-07-18
Jul 21, 2026
Merged

chore(requirements): sync with GitHub project board 2026-07-18#865
SarahLittlejohn merged 3 commits into
masterfrom
chore/requirements-sync-2026-07-18

Conversation

@hmctsclaudecode

Copy link
Copy Markdown

Summary

Nightly requirements database sync — reconciles the baseline with the live state of GitHub Project #43 (CaTH Kanban) as of 2026-07-18.

12 NEW requirements (REQ-0140 → REQ-0151)

REQ Issue Title
REQ-0140 #645 Style Guide: Implement PHT Weekly Hearing List
REQ-0141 #771 Style Guide: Implement Magistrates Standard List
REQ-0142 #778 Fix Verified User Journey on STG env
REQ-0143 #779 Fix non-strategic lists on STG env
REQ-0144 #789 Cookies pop up is broken
REQ-0145 #790 Style Guide: Magistrates Public Adult Court List
REQ-0146 #794 Fix non-strategic lists Sensitivity issue
REQ-0147 #795 Fix Page Titles
REQ-0148 #797 Store source artefact ID and add flat file upload
REQ-0149 #815 Schema validation is missing for some list types
REQ-0150 #816 Make list date format consistent
REQ-0151 #857 Align home page with legacy CaTH service

3 STATUS + IMPL changes (→ verified)

REQ Issue Old Status PR
REQ-0103 #410 implemented #680
REQ-0117 #484 implemented #661
REQ-0120 #514 approved #825

⚠️ Human review required

The GitHub App token does not have read:project permission, so board column status cannot be read directly from ProjectV2. Issue closure + merged closing PR is used as a proxy for Done=verified. Please confirm these issues are in the "Done" column on the CaTH Kanban before merging.

Verification

  • yarn requirements:build succeeds (151 requirements)
  • PRAGMA integrity_check → ok
  • PRAGMA foreign_key_check → empty (no violations)

🤖 Generated with Claude Code

Delta:
- 12 NEW requirements (REQ-0140..REQ-0151): #645, #771, #778, #779,
  #789, #790, #794, #795, #797, #815, #816, #857
- 3 STATUS+IMPL changes (-> verified): REQ-0103 (#410), REQ-0117
  (#484), REQ-0120 (#514)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Jul 18, 2026

Copy link
Copy Markdown
Contributor

🎭 Playwright E2E Test Results

84 tests   52 ✅  2m 52s ⏱️
33 suites  32 💤
 1 files     0 ❌

Results for commit 5a8ac35.

♻️ This comment has been updated with latest results.

SarahLittlejohn and others added 2 commits July 21, 2026 09:57
…0120

PR #861 (007_sync_github_2026_07_16.sql) merged after this branch was
generated and already applies REQ-0120 (#514) -> verified. Merging this
sync unchanged would:
  - collide on the 007_ filename, and
  - re-apply the REQ-0120 UPDATE + requirement_change rows, double-bumping
    version to 3 and inserting duplicate (120, 2, ...) change-log rows
    (requirement_change has no unique constraint, so this corrupts the
    audit trail silently rather than failing the build).

Renames the migration to 008_ and removes the now-redundant REQ-0120 block.
REQ-0103 and REQ-0117 status changes and the 12 new requirements are
unaffected. `yarn requirements:build` succeeds (151 requirements),
PRAGMA integrity_check = ok, foreign_key_check clean, REQ-0120 at version 2.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@SarahLittlejohn
SarahLittlejohn merged commit 3dd3609 into master Jul 21, 2026
11 checks passed
@SarahLittlejohn
SarahLittlejohn deleted the chore/requirements-sync-2026-07-18 branch July 21, 2026 10:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant