Repository navigation
Conversation
RESULT.json was an agent run artifact committed by accident, and PERF_REPORT.md is a database performance audit that belongs with the other design docs. Nothing references either path. MACRO-4954
|
Note Some coding-guideline sources were skipped or only partly applied; the reason is listed next to each one. On a public repository, this repository's guideline files are counted without their names. Skipped guideline sources
No actionable comments were generated in the recent review. Summary
Merge Risk:
|
|
Folded into the single reorg PR #10111 (one PR for the whole reorganization). Its commits are there; closing this one. |
Why
First step of the repository reorganization: clear stray files out of the
repository root before the crate layout changes.
RESULT.jsonis an agent run artifact that was committed by accident.Nothing reads it.
PERF_REPORT.mdis the database performance audit from perf(databases): page large tables on the server and store formula values #7539. It belongswith the other audits in
docs/design/, whichdocs/README.mdalreadylists as the home for proposals, plans and audits.
MACRO-4954
How it works
RESULT.json.PERF_REPORT.mdtodocs/design/databases-performance-audit.mdandmakes its two links to
apps/web/scripts/database-profile/relative to thenew location. No other file referenced either path.