phase 6 review done for now
This commit is contained in:
@@ -278,5 +278,9 @@
|
||||
"C:\\Users\\Ed\\AppData\\Local\\Temp\\pytest-of-Ed\\pytest-1100\\test_auto_aggregate_skip0\\file1.txt": {
|
||||
"hash": "d0b425e00e15a0d36b9b361f02bab63563aed6cb4665083905386c55d5b679fa",
|
||||
"summary": "This document, `file1.txt`, contains a single line of text: \"content1\". Its purpose appears to be to hold this specific piece of content.\n\n**Outline:**\n**TXT** \u2014 1 lines\npreview:\n```\ncontent1\n```"
|
||||
},
|
||||
"C:\\projects\\manual_slop\\docs\\guide_simulations.md": {
|
||||
"hash": "db8e299dafde778ef87ac7dfea11159dedc921c7e44410c94dac79a63625260e",
|
||||
"summary": "This document outlines the verification and simulation framework for structural testing, emphasizing the \"Puppeteer\" pattern for driving GUI simulations via an API Hook. Key takeaways include strict rules against arbitrary core mocking, the use of the `live_gui` fixture for integration tests, and a detailed breakdown of the simulation lifecycle stages, from mock provider setup to verifying worker output.\n\n**Outline:**\n**Markdown** \u2014 395 lines\nheadings:\n Structural Testing Contract\n Verification & Simulation Framework\n Infrastructure\n `--enable-test-hooks`\n The `live_gui` pytest Fixture\n Session Isolation\n Process Cleanup\n VerificationLogger\n Simulation Lifecycle: The \"Puppeteer\" Pattern\n Stage 1: Mock Provider Setup\n Stage 2: Epic Planning\n Stage 3: Poll for Proposed Tracks (60s timeout)\n Stage 4: Accept Tracks\n Stage 5: Poll for Tracks Populated (30s timeout)\n Stage 6: Load Track and Verify Tickets (60s timeout)\n Stage 7: Verify MMA Status Transitions (120s timeout)\n Stage 8: Verify Worker Output in Streams (60s timeout)\n Assertions Summary\n Mock Provider Strategy\n `tests/mock_gemini_cli.py`\n Visual Verification Patterns\n DAG Integrity\n Stream Telemetry\n Modal State\n or\n Performance Monitoring\n Supporting Analysis Modules\n `file_cache.py` \u2014 ASTParser (tree-sitter)\n `summarize.py` \u2014 Heuristic File Summaries\n `outline_tool.py` \u2014 Hierarchical Code Outline\n Two Parallel Code Analysis Implementations"
|
||||
}
|
||||
}
|
||||
Reference in New Issue
Block a user