docs: update schema documentation

[kubrickcode]

Automated update of schema documentation from specvital-infra.

Generated by tbls - includes:

• Table details with columns, types, constraints
• Indexes and unique keys
• ER diagram (Mermaid)

Triggered by: feat(db): add classification_caches table for Phase 1 incremental caching

Cache Phase 1 test classification results to support incremental diff calculation.
Corresponds to behavior_caches (Phase 2) as the Phase 1 cache layer.

• content_hash: SHA-256 hash of test file set
• phase1_output: Classification result with Domain → Feature → TestIndices structure
• test_index_map: TestIdentity → index mapping for diff calculation

[gemini-code-assist]

Summary of Changes

Hello @kubrickcode, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request automates the update of the project's database schema documentation. It integrates the newly introduced public.classification_caches table, which is essential for implementing Phase 1 incremental caching of test classification results. The updated documentation, generated by tbls, now accurately reflects the database structure, including the new table's detailed column definitions, primary keys, unique constraints, and indexes, ensuring consistency between the code and its documentation.

Highlights

• New classification_caches table documentation: Documentation for the public.classification_caches table has been added, detailing its columns, constraints, and indexes. This table is designed to cache Phase 1 test classification results for incremental diff calculation.
• Automated Schema Documentation Update: The README.md and schema.json files have been automatically updated to reflect the inclusion of the new public.classification_caches table, ensuring the documentation remains current with the database schema.
• Support for Incremental Caching: The introduction of the classification_caches table provides the necessary structure to cache test classification results, enabling Phase 1 incremental caching for improved performance and efficiency.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request automatically updates the database schema documentation to include the new classification_caches table. The changes are consistent with the existing documentation structure. I've provided suggestions to add descriptions for the new table and its columns, using information from the pull request description. This will improve the clarity and usefulness of the documentation for other developers.

[gemini-code-assist]

The description for this new table is missing. Adding a description will help others understand its purpose. Based on the pull request description, you could add the following:

"Caches Phase 1 test classification results to support incremental diff calculation. Corresponds to behavior_caches (Phase 2) as the Phase 1 cache layer."

Suggested change

	Cache Phase 1 test classification results to support incremental diff calculation. Corresponds to `behavior_caches` (Phase 2) as the Phase 1 cache layer.

[gemini-code-assist]

The Comment field for several columns is empty, which makes it harder to understand their purpose. Adding comments would improve schema clarity. Based on the pull request description and the table structure, here are some suggested comments:

• content_hash: SHA-256 hash of test file set
• language: The programming language of the test files being classified.
• model_id: The identifier of the model used for classification.
• phase1_output: Classification result with Domain → Feature → TestIndices structure
• test_index_map: TestIdentity → index mapping for diff calculation

Suggested change

	| content_hash | bytea | | false | | | |
	| language | varchar(10) | | false | | | |
	| model_id | varchar(100) | | false | | | |
	| phase1_output | jsonb | | false | | | |
	| test_index_map | jsonb | | false | | | |
	| content_hash | bytea | | false | | | SHA-256 hash of test file set |
	| language | varchar(10) | | false | | | The programming language of the test files being classified. |
	| model_id | varchar(100) | | false | | | The identifier of the model used for classification. |
	| phase1_output | jsonb | | false | | | Classification result with Domain → Feature → TestIndices structure |
	| test_index_map | jsonb | | false | | | TestIdentity → index mapping for diff calculation |