Phase 5 — v0.1.0 release with sample-data demo#6
Merged
Conversation
backtest still declared 0.0.1 while engine and dashboard already carried 0.1.0; the release tags the three layers at the same version. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014dzQV8Kvwy24YnhFtLSbEG
scripts/demo.sh boots the whole stack on the synthetic sample data — tape -> engine -> metrics.db -> journal seed -> API (:8000) -> dashboard (:3000) — and serves it until Ctrl-C. Toolchain and busy-port pre-flights, readiness polls with log tails on failure, .venv and node_modules installed only when missing, METRICS_DB recreated per run so re-runs never duplicate journal seeds. The cleanup trap tears both servers down and drops next dev's generated-type scratch: a kill landing mid-write leaves it half-formed, and dashboard/tsconfig.json includes it, so a stale one breaks npm run typecheck. The Makefile is an index over the commands the README already documents (setup/demo/verify/build/test/lint/clean) — CI keeps invoking the underlying commands directly, so the two cannot drift. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014dzQV8Kvwy24YnhFtLSbEG
CHANGELOG.md (Keep a Changelog) reconstructs what Phases 0-4 delivered under [0.1.0]. The README now opens with a quick start (make demo) and screenshots of both dashboard views in docs/images/, captured from the demo running against the real pipeline; Phase 5 is checked off in the roadmap and the demo/Makefile decisions join Design decisions. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014dzQV8Kvwy24YnhFtLSbEG
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
2 participants
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.
Summary
Phase 5 closes the roadmap: the repo is now a demo-able v0.1.0.
scripts/demo.sh— one command boots the whole stack on the synthetic sample data: tape → engine →metrics.db→ journal seed → FastAPI (:8000) → Next.js dashboard (:3000), served until Ctrl-C. Toolchain + busy-port pre-flights, readiness polls that tail the server log on failure,.venv/node_modulesinstalled only when missing,METRICS_DBrecreated per run so re-runs never duplicate journal seeds. The cleanup trap tears both servers down and dropsnext dev's generated-type scratch — a kill landing mid-write leaves it half-formed wheredashboard/tsconfig.jsonincludes it, breakingnpm run typecheck(found and reproduced while verifying this PR).Makefile— a root index over the commands the README already documents:setup/demo/verify/build/test/lint/clean. CI keeps invoking the underlying commands directly, so the two cannot drift.backtest0.0.1 → 0.1.0 (engine and dashboard already declared 0.1.0).CHANGELOG.md— Keep-a-Changelog format;[0.1.0]reconstructs what Phases 0–4 delivered.make demo) and screenshots of both dashboard views (docs/images/), captured from this demo running against the real pipeline; Phase 5 checked off; three new Design-decisions entries (demo as plain bash, committed screenshots, Makefile-as-index).No engine/backtest/dashboard code changes beyond the version bump.
Verification (all in a fresh container)
make verify— green: 5000 ticks → 501 buckets, 12/12 journal entries joined to a regime.bash scripts/demo.sh— run end to end twice:/metrics/ofi,/metrics/volatility,/metrics/volumeand/journalall served real data; second run reused the installed envs and re-seeded exactly 12 entries (no duplicates); SIGTERM teardown left zero orphan processes.make lint,make test,make build— green: rustfmt/clippy clean, 12 Rust + 71 Python + 27 dashboard tests passing,tscclean, productionnext buildOK.Post-merge
Tag
v0.1.0on the merge commit and publish the GitHub Release with the[0.1.0]CHANGELOG section as notes.