Adoption: bounded read-only SQLite tables in the workspace observatory

[John-Ryan21337]

Club Code has an implemented SQLite database view in its workspace observatory. I am preparing a separate incremental adoption draft on current-dev file-observatory PR94 (67d19445cf880298585a31bdcb25cc6c30543920).

The port will preserve Cafe's server-resolved projectId/root and exact relative-path checks, add explicit database/table/row browsing, and use fixed read-only queries with bounded worker lifetime, output, rows and cells. It will not accept arbitrary SQL, load extensions or change provider versions. Database masking will be described as best effort, not as a secret-protection boundary.

The first runnable slice covers SQLite files inside the selected project. Club's global application-state database view requires a separate explicit access policy and will remain a documented gap unless that boundary can be safely included. Synthetic fixtures, independent review, visual evidence and the required full checks/forced desktop build will precede publication. No live database or account will be queried during development.

[John-Ryan21337]

The incremental SQLite preview is available as fork draft Club #114, exact head 4ae938a5021313e68a537d3a33ab59e285302486, based on file-observatory #94 (67d19445cf880298585a31bdcb25cc6c30543920). It adds explicit bounded table/row reads from private snapshots, without opening the original database in SQLite or accepting SQL. Independent review repaired project-root freshness and descriptor-open protection. Local validation passed: formatting/lint, typecheck 10/10, Chromium 330/330, repository graph 10/10 (4,096 passed, 6 existing skips), and forced desktop build 3/3. Actual bundles and synthetic 6.88-second UI capture were checked. No user database or account was accessed. The guide retains portable snapshot/race and masking limits. Recursive discovery, primary-key comparisons, and global application-state access remain separate work; this is not a completeness claim.