verify-ui: multi-session markers and scoped Stop hook

aurelien.ciemniewski commented

2026-08-24 18:22:21 +02:00

Collaborator

Two commits: the July marker-path fix (.claude/ui-verify → .claude/verify-ui, 4.0.1) and the multi-session rework (4.1.0): per-file content-hashed markers under .claude/verify-ui/verified/, Stop hook scoped to the session's own edited files via transcript scan, legacy last-run.json still read as migration fallback, stdlib test suite incl. concurrent-write test (23 checks).

aurelien.ciemniewski added 2 commits

2026-08-24 18:22:21 +02:00

fix(linkweb-ui-verify): read the marker from the documented path cc07e345b0

- Stop hook looked in `.claude/ui-verify/` while the skill writes
  `.claude/verify-ui/`, so the marker was never seen and every Stop
  re-asked for a verification that had just run
- toolkit README pointed at a config example filename that never shipped
  and claimed the plugin needs config, stale since v4 auto-detection

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

feat(linkweb-ui-verify): multi-session markers and scoped Stop hook 6d7f3c9820

- Up to 9 parallel sessions on one tree: each got nagged to verify the
  others' in-progress files (moving target) and worked around the hook.
- The single shared last-run.json was clobbered across sessions; now one
  content-hashed marker per verified file, written atomically.
- Stop hook scopes its demand to files edited by the session (transcript
  scan); legacy last-run.json still read as a migration fallback.
- --untracked-files=all: git collapsed untracked dirs to "inertia/",
  which could never match a marker or transcript path.

olivier.drieux closed this pull request

2026-08-25 11:43:55 +02:00

Pull request closed

Please reopen this pull request to perform a merge.

Rows
Columns

verify-ui: multi-session markers and scoped Stop hook #15

Pull request closed