Conversation
- Add dev:lean workflow with temporary Cargo and Vite cache locations - Add clean:heavy and clean:all scripts for targeted and full cleanup - Document normal vs lean dev tradeoffs and cleanup usage in README - Update npm scripts to call local tool binaries reliably in this environment Tests: ./scripts/verify.sh (fails in tauri smoke due ':' in workspace path)
- install global git and performance baseline payload - add codex-os manifest and verification contracts - align repo with global policies under /Users/d/.codex/policies Tests: not run (bootstrap scaffolding only)
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fe5030d718
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| with: | ||
| node-version: 20 | ||
| cache: pnpm | ||
| - run: pnpm install --frozen-lockfile |
There was a problem hiding this comment.
Checked perf-foundation.yml and perf-enforced.yml: these jobs run pnpm install --frozen-lockfile, but this repo tracks package-lock.json and no pnpm-lock.yaml. pnpm install --help documents that frozen-lockfile mode fails if lockfile state is not usable, and in this repo it returns ERR_PNPM_NO_LOCKFILE, so the perf jobs fail before any checks can run.
Useful? React with 👍 / 👎.
| cache: pnpm | ||
| - run: pnpm install --frozen-lockfile | ||
| - run: pnpm build || pnpm build:ui | ||
| - run: pnpm perf:lhci:prod || pnpm perf:lhci |
There was a problem hiding this comment.
The enforced Lighthouse step invokes pnpm perf:lhci:prod || pnpm perf:lhci, but neither script exists in package.json (only perf:bundle, perf:build, perf:assets, perf:memory, perf:summary are defined). When PERF_PROFILE=production, this job fails with Command "perf:lhci" not found, so the workflow cannot pass regardless of code changes.
Useful? React with 👍 / 👎.
| process.exit(2); | ||
| } | ||
|
|
||
| const ratio = (c - b) / b; |
There was a problem hiding this comment.
This comparison divides by the baseline value ((c - b) / b) without guarding b === 0; the same commit seeds .perf-baselines/build-time.json and .perf-baselines/bundle.json with zero values, so first enforced runs produce infinite regressions and fail unconditionally instead of reflecting real threshold drift.
Useful? React with 👍 / 👎.
Codacy's Analysis Summary100 new issues (≤ 0 issue) Review Pull Request in Codacy →
|
![codacy-production[bot]](https://avatars.githubusercontent.com/in/56611?s=60&v=4){kind=small}
| else if (lower.some((f) => f.startsWith(".github/"))) scope = "ci"; | ||
|
|
||
| const summary = `${type}(${scope}): update ${staged.length} file${staged.length === 1 ? "" : "s"}`; | ||
| const out = `.git/CODEX_COMMIT_MSG_PROPOSAL`; |
There was a problem hiding this comment.
Codacy has a fix for the issue: ES2015 template literals are forbidden.
| const out = `.git/CODEX_COMMIT_MSG_PROPOSAL`; | |
| const out = ".git/CODEX_COMMIT_MSG_PROPOSAL"; |
1 participant
What
Why
Testing
Risk / Notes
.codex/bootstrap-conflicts/*.newfiles and merge intentionally