test(inventory): report boundary projection timeout state (#157)

[smiggleworth]

Summary

• Add failure-only diagnostics to the existing split API/restarted-worker Application Inventory broker test. If the linked boundary still is not readable after the existing 45-second gate, the assertion reports the last GET status and expected error body, source boundary revision, minimum-revision read, earlier boundary view presence, BoundaryDirectoryV2 checkpoint start/change flags, and bounded worker fault metadata.
• Keep the test sequence and timeout unchanged. The output omits unexpected response bodies and prints only worker error category, event, runner, stage, and type metadata.
• This distinguishes projection startup/catch-up from missing source or worker faults if the intermittent failure recurs. It does not assert a root cause or change runtime behavior. The same existing assertion failed in hosted CI on runs 35910032416, 35911891833, and 35914953984.

Validation

• Client check — exact-head Validate passed.
• Format check — dotnet format Compliance.slnx --verify-no-changes --no-restore --include test/Compliance.Tests/E2E/ApplicationInventoryE2ETests.cs passed on local head 292bf91.
• Release test build — dotnet build test/Compliance.Tests/Compliance.Tests.csproj -c Release --no-restore --no-dependencies passed with zero warnings.
• Focused broker test — ./scripts/check-backend.sh focused 'FullyQualifiedName~ApplicationInventoryE2ETests.ShouldProjectDeclarationsGivenSplitApiAndRestartedWorker' passed 1/1 on 292bf91bd78923686a8c41c43cd3e8144e883a34.
• Exact-head CI run 35917266316 passed Validate (including full broker), dependency review, and native AMD64/ARM64 at 292bf91bd78923686a8c41c43cd3e8144e883a34.

Contracts and operations

• Authentication and authorization effects considered — no policy or request behavior changed.
• API, persistence, scheduling, and wire compatibility considered — test-only change; no runtime contract, event, projection, schema, or worker scheduling change.
• Deployment, health, logging, and rollback effects described — no deployment or configuration change. The extra diagnostic reads and worker log capture run in this isolated test only.