Core: introduce RunContext + define-by-run tracing, contracts, and Sequential/Baseline flow foundation (0.3.0-dev) #208
+2,422
−1
Conversation
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
- add inputs/artifacts/outputs storage with metadata - provide alias properties (query, schema, sql, validation) - add schema_* convenience accessors and metadata helpers
- cover query/schema/sql/validation aliases - verify schema normalization behavior - test metadata helpers (push_meta, get_meta_list)
- validate run_query() populates RunContext.query - cover ctx-mutate vs functional step contracts - ensure invalid return types raise TypeError - verify step execution order and override behavior
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
#️⃣ Issue Number
📝 요약(Summary)
RunContextstate carrier와BaseFlow.run_querysugar API를 제공하고, 전반에 테스트/문서/타입 주석을 보강했습니다.💬 To Reviewers (선택)
RunContext -> RunContext계약(ContractError) 의 강제 수준이 적절한지 확인 부탁드립니다.input_summary/output_summary/data)이 과하지 않은지, 추후 확장에 무리 없는지 의견 부탁드립니다.BaseFlow.run_query를 Base 레벨에 둔 결정(모든 Flow에서 동일 UX 보장)이 적절한지 리뷰 부탁드립니다.PR Checklist
python -m pytest)