[TODO-MVP] Freeze migration scope and success criteria

[web2solutions]

Context

This issue was migrated from the internal backlog and is tracked under the todo-mvp stream.

• Backlog section: Phase 0 - Planning Guardrails (mandatory before code moves)
• Source: .agents/project-todos.md

Objective

Freeze migration scope and success criteria

Detailed Scope

• Define what is in-scope for Wave 1 (must-haves) vs Wave 2+ (enhancements).
• Lock naming decisions:
• product: JumentiX
• npm init CLI package naming strategy (jumentix@init request requires npm alias/registry validation).
• Define migration policy:
• no partial cutovers without complete functional parity in the same wave
• docs and agents update in same wave
• quality gates green before each merge.

Acceptance Criteria

• Implementation merged with required architecture constraints respected.
• Documentation and agents registry updated when scope changes contracts/architecture.
• CI gate and coverage threshold remain green.

Execution Notes

• Issue owned by @web2solutions.
• Label: todo-mvp.

[web2solutions]

Traceability Update (2026-07-01)

• PR: feat(jumentix): advance monorepo extraction, governance, and wave progress #112
• Commit Reference: dev@14e05b43
• Commit Range: main...dev
• Rule: every task update must reference explicit commit(s) and PR.