chore: prepare loops 0.4.14 release line

[andrei-hasna]

Summary

• Bump @hasna/loops to 0.4.14 and add the changelog entry for the post-0.4.13 mainline.
• Harden release validation by making the PR-fingerprint CLI fixture hermetic with pr_state=OPEN.
• Raise the freshness-close drain integration timeout above the observed todos CLI mutation duration while preserving the auto:route removal assertion.

Release blocker evidence

• Source task: 41b7cd06-92c6-49bb-8d40-803a55bed8c9.
• origin/main remains 84488ee; commit time 2026-07-05T18:17:29-07:00. Quiet-window recheck at 2026-07-06T02:23:42Z is clear.
• npm registry check: @hasna/loops latest is 0.4.13; 0.4.13 exists; 0.4.14 does not exist.
• GitHub release/tag drift remains historical: releases/tags are visible only through v0.4.5. This PR does not create or push tags, create releases, publish npm packages, merge PRs, or dispatch release workflows.
• Open PR queue remains a residual release risk: 25 open PRs total, 20 targeting main; release-like open PRs include chore: prepare loops 0.4.10 release line #24 and docs: sync goal-wrapper migration and changelog for 0.3.58–0.3.60 #41. Review/close/merge policy still belongs to the release lane before an actual publish.

Validation

• TMPDIR=/tmp bun install --frozen-lockfile --cache-dir .bun-install-cache: passed, no lockfile changes.
• TMPDIR=/tmp bun run typecheck: passed.
• TMPDIR=/tmp bun test: passed, 643 pass / 0 fail.
• TMPDIR=/tmp bun run test:boundary: passed.
• TMPDIR=/tmp bun run build: passed.
• git diff --cached --check: passed.
• Staged credential-pattern scan: passed.

Notes

No release tag, GitHub release, npm publish, merge, or workflow dispatch was performed by this worker.