fix(ci): green main-red — stale nativeRetrial assertion + triggers fmt drift

[rickylabs]

Green main-red — two test-only reconciliations

main's CI was red on both lanes (surfaced via PR #81, whose only changes are CI YAML + bookkeeping). Root-caused both against the exact failures observed on Linux CI (PR #81 ci run, head 7ed56049):

Lane	Linux CI result	Cause	Fix
check-test	660 passed | 1 failed	typed-queue_test.ts asserted nativeRetrial === false for a Postgres queue, but #71 made the Postgres adapter natively retrial-capable (getNativeRetrial → true for Postgres/Redis/RabbitMQ)	flip assertion to true
quality (fmt:check)	failedBatches:1, findings:1	one over-long assertStringIncludes line in trigger-runtime-processor_test.ts	deno fmt wraps it

Scope

• Test-only. No packages//plugins/ source logic changed.
• deno.lock untouched — lock hygiene is a separate, approval-gated slice.
• The Postgres native-retrial behaviour itself shipped in feat(queue): implement PostgreSQL queue adapter (S5) #71; this only reconciles the stale test expectation.

Local verification (Windows)

• lint ✅, fmt:check ✅ (0 findings), check:scaffold-versions ✅ (E-12 OK), publish:dry-run ✅, audit:critical ✅ (0 critical)
• queue test 2/2 pass; repo-wide check ✅

Note: two scaffold/template tests fail under Windows local runs due to path-separator/CRLF artifacts (join() yields \ on Windows); both pass on Linux CI (660 passed). Not addressed here — environmental, not real.

Once green, this unblocks #81 (e2e-cli-gate rollout) to merge clean, after which scaffold-static + scaffold-runtime can be promoted to required checks.

🤖 Generated with Claude Code