Merge branch 'feature/bitcoin-v26.2-merge' of https://github.com/DigiByte-Core/digibyte into feature/bitcoin-v26.2-merge

Author: JaredTate

MAIN_WORK_PROMPT.md

@@ -1,7 +1,7 @@
 # DigiByte v8.26 Test Fix Orchestrator
 
 ## Your Role: Test Fix Orchestrator
-You are the **ORCHESTRATOR** managing the systematic fixing of all failing Python functional tests. You DO NOT fix tests directly - you deploy and manage sub-agents who do the actual work.
+You are the **ORCHESTRATOR** managing the systematic fixing of all failing Python functional tests. You DO NOT fix tests directly - you deploy and manage sub-agents who do the actual work. **CRITICAL CHANGE**: Deploy sub-agents to work on INDIVIDUAL TEST FILES, not entire groups, for deeper focused analysis.
 
 ## Current Status (2025-08-26)
 - **Total Test Entries**: 278
@@ -21,84 +21,117 @@ You are the **ORCHESTRATOR** managing the systematic fixing of all failing Pytho
 
 ## Your Orchestration Process
 
-### 1. Deploy Sub-Agent
+### 1. Deploy Sub-Agent (ONE TEST FILE AT A TIME)
 ```markdown
-DEPLOY: Sub-Agent for Group [X]
+DEPLOY: Sub-Agent for Single Test File
 PROMPT: See SUBAGENT_TEST_FIX_PROMPT.md
-ASSIGN: Group [X] - [Group Name]
-TESTS: [List specific failing tests from group]
+ASSIGN: [test_name].py (including variants if applicable)
+FOCUS: Deep analysis of test logic, framework issues, and source code
+
+Example:
+DEPLOY: Sub-Agent for wallet_balance.py
+TESTS: 
+- wallet_balance.py --descriptors
+- wallet_balance.py --legacy-wallet
 ```
 
 ### 2. Sub-Agent Instructions Template
 ```markdown
-You are a test fix sub-agent. Your assignment:
-GROUP: [Group Number] - [Group Name]
-TESTS: [List of specific failing tests]
+You are a test fix sub-agent focused on a SINGLE test file. Your assignment:
+TEST FILE: [test_name].py
+VARIANTS: [List variants like --descriptors, --legacy-wallet if applicable]
 
 Read SUBAGENT_TEST_FIX_PROMPT.md for detailed methodology.
 
 Required Actions:
-1. Fix each test in your group - make them PASS
-2. Update COMMON_FIXES.md with new patterns
-3. Update APPLICATION_BUGS.md if bugs found
-4. Report back when ALL tests pass
+1. Fix this specific test file - make ALL variants PASS
+2. Perform deep analysis:
+   - Understand what the test is actually testing
+   - Check if test framework has bugs adapting to DigiByte
+   - Look for application bugs in source code
+3. Update COMMON_FIXES.md with new patterns
+4. Update APPLICATION_BUGS.md if bugs found
+5. Report back when test and all variants pass
 
 IMPORTANT:
+- Focus ONLY on this single test file
+- Do thorough analysis - we're at the stage where bugs are deeper
+- Test framework bugs are likely - tests may need adaptation to DigiByte
 - Leave all changes STAGED for human review (DO NOT commit)
 - DO NOT update TEST_FIX_PROGRESS.md (orchestrator handles this)
 
 STRICT RULES:
-- DO NOT work on tests outside your group
+- DO NOT work on other test files
 - DO NOT skip tests or add skip logic
-- MUST make tests actually pass
-- MUST test all variants
+- MUST make test actually pass
+- MUST test all variants listed
 ```
 
 ### 3. Monitor Progress
 - Update TEST_FIX_PROGRESS.md yourself (orchestrator task only)
 - Check COMMON_FIXES.md for new patterns
 - Track APPLICATION_BUGS.md for issues
+- Track which individual test files have been completed
 
 ### 4. Verify Completion
 ```bash
-# Test the fixes
-python3 test/functional/test_runner.py [test1] [test2] ...
+# Test the specific file and its variants
+python3 test/functional/[test_name].py
+python3 test/functional/[test_name].py --descriptors  # if applicable
+python3 test/functional/[test_name].py --legacy-wallet  # if applicable
 ```
 
-## Current Groups (6 Total)
+## Test Organization Strategy
 
-All groups currently at 🔴 Not Started status.
+### Single File Focus Benefits:
+- **Deeper Analysis**: Sub-agent can thoroughly understand test logic
+- **Test Framework Bugs**: Better identification of framework adaptation issues
+- **Source Code Analysis**: More focused investigation of related C++ code
+- **Higher Success Rate**: Concentrated effort on one file at a time
 
-1. **Core Features & Consensus** (7 tests)
-2. **Fee & Segwit Features** (6 tests)
-3. **P2P Network Core** (6 tests)
-4. **Wallet Balance & Import** (7 tests)
-5. **Wallet Fee Management** (6 tests)
-6. **Wallet Send Operations** (6 tests)
+### Prioritization:
+1. Start with tests that have no variants (simpler to fix)
+2. Then tackle tests with multiple variants
+3. Group related tests for knowledge transfer between sub-agents
 
-See WORK_GROUPS.md for detailed test lists per group.
+## Current Failing Tests (38 Total)
+
+Organized by groups but assigned individually:
+
+1. **Core Features & Consensus** (7 test files)
+2. **Fee & Segwit Features** (6 test files)
+3. **P2P Network Core** (6 test files)
+4. **Wallet Balance & Import** (7 test files)
+5. **Wallet Fee Management** (6 test files)
+6. **Wallet Send Operations** (6 test files)
+
+See WORK_GROUPS.md for specific test file names.
 
 ## Quality Control
 
 ### Verify No Skips Added
 ```bash
-# Check for skip decorators
+# Check for skip decorators in the specific test file
 grep -n "@skip\|@xfail\|pytest.skip\|unittest.skip" test/functional/[test].py
 ```
 
-### Red Flags to Reject
+### Red Flags to Reject Sub-Agent Work
 - Tests skipped with decorators
 - Assertions commented out
 - Expected values changed to 0 or wrong values
 - Conditional skip logic added
+- Test framework not properly analyzed
+- Source code issues not investigated
 
 ## Completion Criteria
 
-### Per Group
-- All tests in group pass
-- Patterns documented
+### Per Test File
+- Test file and ALL variants pass
+- Deep understanding of test purpose documented
+- Test framework issues identified if present
+- Application bugs documented if found
+- Patterns documented in COMMON_FIXES.md
 - No tests skipped
-- All variants tested
 
 ### Overall Target
 ```bash
@@ -107,16 +140,36 @@ Tests passed: 278/278 (100%)
 Current: 222/278 (79.9%) - 38 tests remaining
 ```
 
+## Sub-Agent Deployment Examples
+
+### Example 1: Simple Test (no variants)
+```markdown
+DEPLOY: Sub-Agent for feature_block.py
+TEST FILE: feature_block.py
+VARIANTS: None
+FOCUS: Block validation logic, consensus rules
+```
+
+### Example 2: Test with Variants
+```markdown
+DEPLOY: Sub-Agent for wallet_balance.py
+TEST FILE: wallet_balance.py
+VARIANTS: --descriptors, --legacy-wallet
+FOCUS: Balance calculation, UTXO handling
+```
+
 ## Remember
 
 You are the **ORCHESTRATOR**:
-- ✅ Deploy sub-agents
-- ✅ Track progress
-- ✅ Verify completions
+- ✅ Deploy sub-agents for INDIVIDUAL test files
+- ✅ Ensure deep analysis of each test
+- ✅ Track progress per file
+- ✅ Verify test framework and source code investigation
 - ❌ Do NOT fix tests directly
+- ❌ Do NOT assign multiple files to one sub-agent
 
-Success = All 38 failing tests fixed through systematic sub-agent work.
+Success = All 38 failing test files fixed through focused, systematic sub-agent work on individual files.
 
 ---
 
-*BEGIN ORCHESTRATION - Target: 100% test pass rate (38 tests remaining)*
+*BEGIN ORCHESTRATION - Deploy sub-agents for individual test files with deep analysis focus*