Current Status
State: reproducible preparation remains open; it no longer blocks the mail-runtime revision's inspection evidence. In the exact worktree, assigning the existing Python 3.13.7 interpreter to the root odoo-devkit module fixed the readiness failure. The earlier attempt had assigned only the nested runtime-support module. No new environment, dependency install, suppression, or inspection profile was introduced by that assignment.
The full six-file assessment produced RED with all 174 findings retrieved and verified project closure. Six new dataclass/type warnings were fixed with the fixture's actual StartupSettings type. A fresh scoped assessment confirmed those findings gone (14 existing startup-test findings remain). Other new diagnostics are missing SQL schema metadata or references on dynamic test fixtures; the runtime behavior and SQL are exercised by the passing tests. The remaining baseline includes dynamic module references, absent runtime-only psycopg2 metadata, SQL resolution, and existing Python/style warnings. No GREEN claim is made.
Incidental IDE changes were reviewed, preserved outside git, and reversed after helper-owned project closure. PR #110 merged at d79283d with all five checks passing on the final PR head; post-merge CI also passed. Its manual local repair is evidence for that revision, not a completed automatic preparation contract. This issue still owns removing dependence on primary-checkout SDK names and sibling project mappings through reproducible setup.
The same SDK assignment gap recurred during #113 in the idempotent-admin-startup worktree. The helper registered the correct Python 3.13 environment but left it unassigned and reported UNKNOWN / project_analysis_not_ready. Selecting that exact worktree environment in PyCharm enabled a complete final changed-file result: RED with 13 baseline findings outside changed lines and verified project closure. Restoring incidental tracked IDE changes after an earlier inspection reset that assignment, so preparation still depends on manual repair. #113 and the CM consumer rollout are complete (#112); this preparation issue remains open. Last verified 2026-09-24.
Finish Line
- The repository's declared preparation covers its root and runtime Python sources in a linked worktree.
- A current inspection produces complete GREEN or RED evidence, with findings triaged and helper-owned lifecycle cleanup verified.
- Preparation does not change tracked source/IDE files or depend on sibling checkout locations.
Relationships
Blocks inspection readiness for #110; delivery work remains tracked by cbusillo/launchplane#2485. Tests for the mail behavior pass independently, and UNKNOWN is not a clean inspection result.
Current Status
State: reproducible preparation remains open; it no longer blocks the mail-runtime revision's inspection evidence. In the exact worktree, assigning the existing Python 3.13.7 interpreter to the root odoo-devkit module fixed the readiness failure. The earlier attempt had assigned only the nested runtime-support module. No new environment, dependency install, suppression, or inspection profile was introduced by that assignment.
The full six-file assessment produced RED with all 174 findings retrieved and verified project closure. Six new dataclass/type warnings were fixed with the fixture's actual StartupSettings type. A fresh scoped assessment confirmed those findings gone (14 existing startup-test findings remain). Other new diagnostics are missing SQL schema metadata or references on dynamic test fixtures; the runtime behavior and SQL are exercised by the passing tests. The remaining baseline includes dynamic module references, absent runtime-only psycopg2 metadata, SQL resolution, and existing Python/style warnings. No GREEN claim is made.
Incidental IDE changes were reviewed, preserved outside git, and reversed after helper-owned project closure. PR #110 merged at d79283d with all five checks passing on the final PR head; post-merge CI also passed. Its manual local repair is evidence for that revision, not a completed automatic preparation contract. This issue still owns removing dependence on primary-checkout SDK names and sibling project mappings through reproducible setup.
The same SDK assignment gap recurred during #113 in the idempotent-admin-startup worktree. The helper registered the correct Python 3.13 environment but left it unassigned and reported UNKNOWN / project_analysis_not_ready. Selecting that exact worktree environment in PyCharm enabled a complete final changed-file result: RED with 13 baseline findings outside changed lines and verified project closure. Restoring incidental tracked IDE changes after an earlier inspection reset that assignment, so preparation still depends on manual repair. #113 and the CM consumer rollout are complete (#112); this preparation issue remains open. Last verified 2026-09-24.
Finish Line
Relationships
Blocks inspection readiness for #110; delivery work remains tracked by cbusillo/launchplane#2485. Tests for the mail behavior pass independently, and UNKNOWN is not a clean inspection result.