The project SQLite preview in fork draft114 requires selecting a known file in the directory tree. Club also has a recursive database finder. I am preparing a separate incremental adoption draft on exact114 that adds an explicit Find SQLite files action for the selected project.
The proposed scan uses the existing server-owned project root, hidden/generated/sensitive-name and link exclusions, bounded directory/entry/depth/header-probe/result budgets, and the existing admission/deadline path. It checks only the fixed SQLite header through a nonblocking regular-file descriptor; it does not open databases or execute SQL during discovery. Results stay bound to the exact connection and project; selection opens the existing explicit table/row viewer.
This is a bounded partial scan, not guaranteed exhaustive discovery or a hostile-writer sandbox. It does not expose the application's global state database, run automatically, or add polling. Primary-key row comparisons remain another separate slice. Synthetic tests and actual component media will accompany the draft; no user database will be accessed.
The project SQLite preview in fork draft114 requires selecting a known file in the directory tree. Club also has a recursive database finder. I am preparing a separate incremental adoption draft on exact114 that adds an explicit Find SQLite files action for the selected project.
The proposed scan uses the existing server-owned project root, hidden/generated/sensitive-name and link exclusions, bounded directory/entry/depth/header-probe/result budgets, and the existing admission/deadline path. It checks only the fixed SQLite header through a nonblocking regular-file descriptor; it does not open databases or execute SQL during discovery. Results stay bound to the exact connection and project; selection opens the existing explicit table/row viewer.
This is a bounded partial scan, not guaranteed exhaustive discovery or a hostile-writer sandbox. It does not expose the application's global state database, run automatically, or add polling. Primary-key row comparisons remain another separate slice. Synthetic tests and actual component media will accompany the draft; no user database will be accessed.