Fill Scan Detection Gaps
The database dependency map, framework hint patterns, and payment package table are incomplete. Missing entries cause false negatives — real stack components go undetected. The user wants to fill every known gap from a 70-repo validation and independent agent review, bringing the lookup tables to vocabulary completeness for the modern TS startup customer.
verdict PASSscore 24 / 24findings 4 (0 risk · 1 debt · 3 obs)duration 44mrejection cycles 0shipped May 22, 2026surface cli
Pipeline timeline
Intent to proven code in 44m across Think, Plan, Build, and Verify.
Think21m
Plan9m
Build6m
Verify4m
Assertion ledger
24 claims, each independently verified. Showing 8 — show all →
| ID | Says | Matcher | |
|---|---|---|---|
| A001 | Kysely projects are detected as using a database | verified | ok |
| A002 | MikroORM projects are detected as using a database | verified | ok |
| A003 | Slonik projects are detected as using PostgreSQL | verified | ok |
| A004 | Silverhand slonik fork is detected as PostgreSQL | verified | ok |
| A005 | Vercel Postgres projects are detected as using Vercel Postgres | verified | ok |
| A006 | MongoDB native driver projects are detected as using MongoDB | verified | ok |
| A007 | Postgres.js projects are detected as using PostgreSQL | verified | ok |
| A008 | sqlite3 projects are detected as using SQLite | verified | ok |
Findings 4 total
debtpackages/cli/tests/engine/detectors/surfaces.test.ts→ monitor
Svelte/Nuxt ordering test (A020) constructs hints with Svelte first — passes regardless of actual FRAMEWORK_HINTS array order in census.ts
obs→ closed
vue.config.ts missing from both FRAMEWORK_HINTS and STRONG_FRAMEWORK_CONFIGS — pre-existing gap, not introduced by this build
obspackages/cli/src/engine/census.ts→ monitor
FRAMEWORK_HINTS is not exported — no direct unit test can verify array ordering invariants without integration-level testing
obspackages/cli/tests/engine/detectors/surfaces.test.ts→ closed
@ana tag collision — A015-A020 IDs reused from scan-surface-detection contract in same test file. Machines parsing @ana tags will match wrong tests for older contracts.
Integrity seal
scopesha256:1c961f3dcbfa8...
contractsha256:d76bd2582ce02...
plansha256:714e1978db65f...
specsha256:b08d518b15c71...
build-reportsha256:18045f79967ae...
build-datasha256:b72810e7b4806...
verify-reportsha256:2376d0b9787a7...
verify-datasha256:980b2d76e8f8f...
audit cmd$ ana proof audit fill-scan-detection-gaps → all hashes match