Repository navigation
[obvious-fleet] Faster, more robust src/app/app: benchmark harness, measured optimizations, hardened inputs - #14
Draft
obvious-autobuild[bot] wants to merge 1 commit into
Draft
obvious-autobuild[bot] wants to merge 1 commit into
obvious-autobuild[bot] wants to merge 1 commit into
Conversation
Adds src/app/app/_lib: a Next.js private folder with a before/after benchmark harness (npm run bench:app), suite stubs for every part of src/app/app/, protocol docs, and jsdom for the frontend vitest project.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This branch had an error being deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fleet-packet: genp-connvo-src-app-app
Status: IN PROGRESS — benchmark harness scaffolded, part branches landing
What changed and why
src/app/app/(the authenticated app shell: layout/providers, dashboard, profile form, settings, meeting summary, match queue, professional queue pages) is being made measurably faster and more robust without changing normal-path behavior.This first commit adds the measurement infrastructure:
src/app/app/_lib/(Next.js private folder, never routed): a before/after benchmark harness.npm run bench:appruns every suite, printing medians over interleaved repeated samples plus the machine load average;--jsonfor machine-readable output.src/app/app/_lib/README.md): every optimization is extracted into a pure helper that is equivalence-tested against a frozen verbatim copy of the original inline code, and benchmarked original-vs-optimized on the same machine.jsdomadded as a devDependency so the vitestfrontendproject can run tests forsrc/code (task-permitted toolchain install).Part branches (
obv/genp-connvo-src-app-app--<part>) add per-page optimizations and robustness fixes; the lead merges them into this branch and reruns the full verification.How verified
main:npx tsc --noEmit= 29 pre-existing errors, 0 insrc/app/app/(errors live in src/hooks/, src/components/ui/chart.tsx, src/app/videocall/, test/convex/*);npx vitest run= 240/240 tests pass with 1 pre-existing teardown error inconvex/prompts/prompts.test.tsafter tests complete (vitest exit 1 on main for that reason alone);npm run lintis broken onmain(next lintwas removed in Next 16 and the legacy.eslintrc.jsonpath fails under eslint-config-next 16) — pre-existing, untouched per scope.npm run bench:appprints load average and an empty table (all suites stubbed).Not verified yet
Assumptions
jsdom(devDependency) and thebench:appnpm script count as permitted toolchain/install, not dependency upgrades.openspec/AGENTS.md) asks for proposals on "optimize performance (changes behavior)" work; this run is explicitly behavior-preserving and autonomous, so no OpenSpec change proposal is filed.