feat: build an auditable A-share research workbench - #175
Open
xiaoming032097 wants to merge 26 commits into
Open
feat: build an auditable A-share research workbench#175xiaoming032097 wants to merge 26 commits into
xiaoming032097 wants to merge 26 commits into
Conversation
xiaoming032097
marked this pull request as ready for review
August 12, 2026 14:30
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.
What changed
main, preserving upstream regime, composite-strategy, index, monitor, and UI work.Why
The previous workflow could publish an end-of-day recommendation snapshot and then let the realtime quote service rewrite the same source partitions. That invalidated otherwise valid research evidence after restarts or later refreshes. Historical candidate health also compared archived snapshots against mutable current partitions, which could collapse the model-health window to a misleading result. The simulated account did not explain portfolio concentration, and deployment/data-provider/backup boundaries were not sufficiently explicit for a reliable personal research system.
This change makes the application fail closed when evidence is incomplete, preserves historical decision evidence, and explains what a beginner may research or simulate without connecting to a broker or placing orders.
User and developer impact
Validation
uv run pytest -q: 874 passed after synchronizing upstreammainpnpm.cmd test: 52 passedpnpm.cmd build: production build passedgit diff --check origin/main...HEAD: passed.env, authentication file, private key, or token committedhealthybefore publication8/10historical model-health window, portfolio-risk panel, and a newly published same-day research snapshotSafety boundary
This remains a personal research and simulation application. It does not connect to a brokerage account, submit orders, or promise returns.