Update Python version requirements and fix compatibility issues

- Bump minimum Python version from 3.11 to 3.13 across all apps
- Add Python 3.11-3.13 test matrix to CLI workflow
- Document Python 3.11+ requirement in .env.example
- Fix Starlette Broadcast removal with in-process fallback implementation
- Add _InProcessBroadcast class for tests when Starlette Broadcast is unavailable
- Refactor API key validators to read live settings instead of cached values
- Update database models with explicit
This commit is contained in:
oib
2026-02-24 18:41:08 +01:00
parent 24b3a37733
commit 825f157749
270 changed files with 66674 additions and 2027 deletions

31
docs/10_plan/README.md Normal file
View File

@@ -0,0 +1,31 @@
# Planning Index (docs/10_plan)
Quick index of planning documents for the current and upcoming milestones.
## Weekly Plan (Current)
- **00_nextMileston.md** — Week plan (2026-02-23 to 2026-03-01) with success metrics and risks
- **99_currentissue.md** — Current issues, progress, and status tracker for this milestone
## Detailed Task Breakdowns
- **01_js_sdk_enhancement.md** — JS SDK receipt verification parity (Day 1-2)
- **02_edge_gpu_implementation.md** — Consumer GPU optimization and edge features (Day 3-4)
- **03_zk_circuits_foundation.md** — ML ZK circuits + FHE foundations (Day 5)
- **04_integration_documentation.md** — API integration, E2E coverage, documentation updates (Day 6-7)
## Operational Strategies
- **05_testing_strategy.md** — Testing pyramid, coverage targets, CI/CD, risk-based testing
- **06_deployment_strategy.md** — Blue-green/canary deployment, monitoring, rollback plan
- **07_preflight_checklist.md** — Preflight checks before implementation (tools, env, baselines)
## Reference / Future Initiatives
- **Edge_Consumer_GPU_Focus.md** — Deep-dive plan for edge/consumer GPUs
- **Full_zkML_FHE_Integration.md** — Plan for full zkML + FHE integration
- **On-Chain_Model_Marketplace.md** — Model marketplace strategy
- **Verifiable_AI_Agent_Orchestration.md** — Agent orchestration plan
- **openclaw.md** — Additional planning notes
## How to Use
1. Start with **00_nextMileston.md** for the week scope.
2. Jump to the detailed task file for the days work (01-04).
3. Consult **05_testing_strategy.md** and **06_deployment_strategy.md** before merging/releasing.
4. Use the reference plans for deeper context or future phases.