Fix strict spec lint transport overflow for large corpora

[chrisdpurcell]

Summary

project-standards spec lint --strict fails before it can report lint findings when the repository contains the full agent-configs specification corpus.

Reproduction

1. Use project-standards v5.29.0 in L3DigitalNet/agent-configs at commit 2b1c295a.
2. Run project-standards spec validate; it succeeds for every discovered spec.
3. Run project-standards spec lint --strict; it exits 2 with error: provider result exceeded the transport limit.

The same command in the reusable validate-specs workflow fails identically. Linting one spec at a time returns its findings, indicating the aggregate provider response exceeds the bounded transport frame.

Expected behavior

The strict lint command should either return all corpus findings without exceeding its internal transport limit, or stream/chunk its result so CI can surface actionable lint diagnostics.

Acceptance criteria

• project-standards spec lint --strict can lint a corpus with the agent-configs specification volume without a transport-limit failure.
• The reusable validate-specs workflow reports actual lint findings and exits according to strict-lint policy.