Skip to content

Codex/backtesting adaptive sizing cleanup#7

Merged
david30907d merged 25 commits into
mainfrom
codex/backtesting-adaptive-sizing-cleanup
May 11, 2026
Merged

Codex/backtesting adaptive sizing cleanup#7
david30907d merged 25 commits into
mainfrom
codex/backtesting-adaptive-sizing-cleanup

Conversation

@david30907d
Copy link
Copy Markdown
Member

No description provided.

@vercel
Copy link
Copy Markdown

vercel Bot commented May 10, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
zap-engine-frontend Ready Ready Preview, Comment May 11, 2026 11:11am
zap-engine-landing-page Ready Ready Preview, Comment May 11, 2026 11:11am

@openzeppelin-code
Copy link
Copy Markdown

Codex/backtesting adaptive sizing cleanup

Generated at commit: 9b3e359d2f43a8d32d0481ceb9023f9a49ebadd9

🚨 Report Summary

Severity Level Results
Contracts Critical
High
Medium
Low
Note
Total
0
0
0
0
0
0
Dependencies Critical
High
Medium
Low
Note
Total
0
0
0
0
0
0

For more details view the full report in OpenZeppelin Code Inspector

david30907d and others added 5 commits May 10, 2026 20:07
…on default config_id

The /api/v3/strategy/daily-suggestion/{user_id} endpoint already declares config_id as optional and resolves the is_default=TRUE preset internally when omitted. The response echoes the resolved id back, and every downstream consumer in account-engine (telegram callback button, DB write) reads from the response field — not from this constant.

Hardcoding the preset id here forced lockstep updates whenever the analytics team changed the production default. Removing it makes analytics-engine the sole source of truth for "which preset is current."

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@david30907d david30907d merged commit e03813d into main May 11, 2026
16 of 21 checks passed
@david30907d david30907d deleted the codex/backtesting-adaptive-sizing-cleanup branch May 11, 2026 12:31
taiiiiiiiiiiii pushed a commit that referenced this pull request May 24, 2026
Plan Tier 3 #7 (partial). Adds `pnpm lint:dead-env` wrapping
scripts/check-dead-env.sh so the dead-env scan joins the `pnpm` script
namespace and is discoverable alongside the other drift checkers.
`check:local` now invokes the pnpm script instead of the raw bash path.

Considered and rejected as not actually applicable:
- "Absorb drift patterns into stronger presets" — the drift checkers
  catch outlier overrides (rootDir!=./src, non-standard types, jscpd
  local-key bleed), NOT common patterns. The presets already cover the
  common case; the lints are defensive backstops against weird overrides.
  Lifting outliers into presets is incoherent.
- "Replace scripts-drift with turbo validation" — scripts-drift enforces
  herd consistency (>50% have script X → flag those without). Turbo has
  no equivalent; the existing checker is the only enforcement.
- "Rewrite check-dead-env in TS" — purely cosmetic, no behavioral win.

The 4 drift checkers (config-drift, scripts-drift, snapshot-sync,
check-dead-env) stay as-is. They are working defensive infrastructure,
not the "treatment failure" the plan framed them as.

https://claude.ai/code/session_01VCU2uisRq7X58rrnWA2Ckd
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant