Document current verification baseline
This commit is contained in:
@@ -1,6 +1,6 @@
|
|||||||
# SFERA Completion Plan
|
# SFERA Completion Plan
|
||||||
|
|
||||||
Дата аудита: 2026-05-10.
|
Дата аудита: 2026-05-16.
|
||||||
|
|
||||||
Этот план фиксирует путь к завершению SFERA как продукта. Он не подменяет
|
Этот план фиксирует путь к завершению SFERA как продукта. Он не подменяет
|
||||||
`IMPLEMENTATION_ORDER.md`, а добавляет проверяемые критерии готовности и текущий статус.
|
`IMPLEMENTATION_ORDER.md`, а добавляет проверяемые критерии готовности и текущий статус.
|
||||||
@@ -12,12 +12,14 @@ projection/incremental контур, runtime/governance/knowledge/collaboration
|
|||||||
|
|
||||||
Текущая проверенная база:
|
Текущая проверенная база:
|
||||||
|
|
||||||
- Python/API tests: `161 passed`.
|
- Python/API tests: `219 passed`.
|
||||||
- Rust tests: `14 passed`.
|
- Rust tests: `15 passed`.
|
||||||
- Frontend `typecheck`: passed.
|
- Frontend `typecheck`: passed.
|
||||||
- Frontend production `next build`: passed.
|
- Frontend production `next build`: passed.
|
||||||
- Editor smoke: passed.
|
- Editor smoke: passed.
|
||||||
- Editor runtime smoke: passed.
|
- Editor runtime smoke: passed.
|
||||||
|
- Shared Docker host smoke: passed for API, web, PostgreSQL, Neo4j, Qdrant, Redis and object storage on `test-docker`.
|
||||||
|
- Local Git baseline: initialized on branch `main`, first commit `3b845c8`.
|
||||||
|
|
||||||
## Definition Of Done
|
## Definition Of Done
|
||||||
|
|
||||||
@@ -142,13 +144,15 @@ Remaining:
|
|||||||
|
|
||||||
## Execution Order From Here
|
## Execution Order From Here
|
||||||
|
|
||||||
1. Keep all current green checks green with `scripts/check_all.ps1`.
|
1. Connect the local Git baseline to the canonical Gitea repository on `git.cin.su` after the exact repository path is available.
|
||||||
2. Finish Phase 1 hardening fixtures and diagnostics.
|
2. Keep all current green checks green with `scripts/check_all.ps1`.
|
||||||
3. Expand Phase 2/3 fixtures around metadata, impact, query and runtime topology.
|
3. Reduce API test/runtime latency so the full Python suite stays comfortably below CI timeout budgets.
|
||||||
4. Finish guarded apply and object-level authoring API.
|
4. Finish Phase 1 hardening fixtures and diagnostics.
|
||||||
5. Finish IDE authoring UI and smoke coverage.
|
5. Expand Phase 2/3 fixtures around metadata, impact, query and runtime topology.
|
||||||
6. Add AI pair-programmer only after guarded apply is deterministic.
|
6. Finish guarded apply and object-level authoring API.
|
||||||
7. Verify full stand on local/NAS and shared Docker host.
|
7. Finish IDE authoring UI and smoke coverage.
|
||||||
|
8. Add AI pair-programmer only after guarded apply is deterministic.
|
||||||
|
9. Verify full stand on local/NAS and shared Docker host.
|
||||||
|
|
||||||
## Verification
|
## Verification
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user