chore(requirements): sync github 2026-08-01

[hmctsclaudecode]

Nightly requirements-sync for 2026-08-01. Adds requirements/migrations/011_sync_github_2026_08_01.sql (the only file changed).

Delta

New requirements: 0

Status changes: 1

Ref	Issue	Change
REQ-0110	#438 Style Guide: PCOL Daily List	approved → verified, impl_commit_sha/impl_paths populated from merged PR #863

Combined into a single UPDATE with one version bump (v1 → v2); the status and both impl requirement_change rows share version 2, as one logical edit.

Impl changes: 8 — all impl_paths-only; impl_commit_sha is unchanged on every one, so no merged PR moved.

Ref	Issue	PR	Paths
REQ-0007	#229	#338	45 → 46
REQ-0074	#297	#181	95 → 105
REQ-0078	#301	#458	114 → 115
REQ-0100	#346	#402	23 → 24
REQ-0101	#347	#662	18 → 19
REQ-0102	#357	#435	33 → 34
REQ-0124	#563	#782	3 → 4
REQ-0135	#569	#748	2 → 3

These are corrections to data earlier syncs recorded incompletely, with two distinct root causes:

• REQ-0074: the 10 missing paths are exactly raw indices 100–109 of PR VIBE-309 - Configure list type and get list information from database #181's 110-file list — an earlier run issued an unpaginated files(first: 100) and silently truncated the tail. This run pages all PR file lists to completion.
• The other 7: each regained a single dotfile (apps/web/.env.example, or .dockerignore for REQ-0124) that an earlier run's exclusion filter dropped. Dotfiles are in scope — .gitignore (REQ-0124) and .claude/hooks/post-write.sh (REQ-0078) were already recorded, so excluding them was inconsistent.

Every change is additive — no path is removed from any requirement. Their requirement_change.change_summary reads impl_paths corrected — earlier sync recorded an incomplete file list rather than merged PR(s) changed, so the audit trail does not claim a PR moved when none did.

Below-the-gate cases

None. Every issue backing an existing requirement is still present in the repo, and none was closed as NOT_PLANNED. No requirement is deleted, no status is lowered, and no ref is reused.

Verification

• yarn requirements:build succeeds (159 requirements)
• PRAGMA integrity_check → ok
• PRAGMA foreign_key_check → empty
• Every touched row's requirement.version equals its highest requirement_change.version

Reviewer notes

Board status could not be read. The GitHub App token lacks read:project: the ProjectV2 node query returns FORBIDDEN and issue.projectItems comes back empty. As in migrations 004–010, this run used the established proxy — issue closed as COMPLETED plus a merged closing PR ⇒ verified. Please confirm #438 is actually "Done" on the CaTH Kanban before merging. A consequence of the proxy is that genuinely new issues sitting in Refined Tickets/In Progress (not yet closed) cannot be detected, which is why this run reports 0 new requirements.

Overlap with open PR #911. PR #911 (chore/requirements-sync-2026-07-31) also sets REQ-0110 to verified with the same merge SHA 5421d745. I did not commit onto that branch, because:

1. chore(requirements): sync github 2026-07-31 #911 does not currently build cleanly. On top of master's baseline its 012 migration fails PRAGMA foreign_key_check — it writes requirement_change/requirement_link rows for requirements 239, 270 and 277, which do not exist in master (max id 159). Those three UPDATEs silently affect zero rows, leaving orphaned change rows. It appears authored against a different, larger baseline (it also inserts ids up to 288).
2. Stacking mine on top double-records REQ-0110, taking it to version 4 with two separate status_changed rows (approved → verified then implemented → verified) for one real-world transition.

This PR is therefore based on master and is self-contained. If #911 merges first, close this one or drop the REQ-0110 section and renumber — the 8 impl_paths corrections are independent of #911 and still apply either way. #911's failing foreign_key_check is pre-existing and needs a human decision regardless.

🤖 Generated with Claude Code

[github-actions]

🎭 Playwright E2E Test Results

82 tests   45 ✅  8m 32s ⏱️
31 suites  30 💤
 1 files     0 ❌  7 🔥

For more details on these errors, see this check.

Results for commit e01e9f2.