docs(shadow): Lior anti-entropy log on Vera narrative loop and Riven pagination

[AceHack]

Shadow lesson log documenting Vera's stale lock narrative momentum and Riven's pagination tool-blindness.

[Copilot]

Pull request overview

Adds a new shadow lesson log research note capturing two observed drift modes: Vera deferring work based on a stale .git/index.lock narrative, and Riven undercounting actionable PRs due to pagination/tooling limits.

Changes:

• Added a new research log with YAML frontmatter and structured sections (Observation, Drift Classification, Correction Required).
• Documented expected corrective behaviors for filesystem validation and paginated-result traversal.

[AceHack]

Vera recheck 2026-05-20T23:20Z: #4458 is owner-only at head 6f95034a2dde99c14f5c863b1851e0754f31d829, base 0cd4ee096d00f83b52b2cf0faabd70d0c1948dba, while current main is ef4f7052ecdfb0a58e34b9ba8afd326d96dfdfec. GraphQL reports mergeable=MERGEABLE, maintainerCanModify=false, and checks are green.

Blocking review state: one unresolved non-outdated Copilot P1 thread on docs/research/2026-05-20-shadow-lesson-log-vera-narrative-loop-riven-pagination.md line 10. The finding says the claim that gh pr list returned “over 200 open PRs” is ambiguous because gh pr list defaults to 30 items unless --limit or equivalent pagination is specified. The fix should record the exact command/evidence used or scope the claim to a paginated query.

Next toe-safe owner action: update that sentence, let checks refresh if needed, and resolve the thread. Vera did not write in the contested root checkout.

[AceHack]

Vera recheck 2026-05-20T23:39Z: #4458 has advanced from the prior handoff head to e92dd94d686324499a6553fb33fda24d9949e9e4; base remains 0cd4ee096d00f83b52b2cf0faabd70d0c1948dba while current main is ef4f7052ecdfb0a58e34b9ba8afd326d96dfdfec. REST metadata reports mergeable=true and maintainer_can_modify=false.

REST file diff shows the Copilot P1 ambiguity about the pagination evidence appears addressed in the current patch: the observation now names gh pr list --state open --limit 250 instead of leaving the >200-PR claim commandless. GraphQL review-thread state is currently blocked by API rate limit, so I did not mark or assume the thread resolved.

Checks are still in progress on the new head, including lint, path gate, CodeQL, submit-nuget, and related jobs. Next toe-safe action: wait for checks to complete, then inspect any failing job logs before rerun or further handoff; owner should resolve the Copilot thread if GitHub still shows it after CI settles.

[AceHack]

Vera recheck 2026-05-20T23:42Z: #4458 head e92dd94d686324499a6553fb33fda24d9949e9e4 now has green REST check-run state: build/test, lint, path gate, CodeQL, and submit-nuget all completed successfully; one matrix Analyze entry is skipped as expected from the path gate shape. REST metadata still reports mergeable=true and maintainer_can_modify=false.

The current REST diff still shows the Copilot P1 pagination-evidence issue appears addressed by naming gh pr list --state open --limit 250. GraphQL review-thread state remains rate-limited, so I cannot verify or resolve the thread from Vera. Next toe-safe owner action: resolve the Copilot thread if GitHub still shows it, then merge or rebase/update if branch protection requires current-main base.