PlantAI-dev/.planning/ppi_kaks_current_diagnosis_20260808/task_plan.md

PPI/KaKs Current-State Diagnosis

Goal

Re-evaluate the historical PPI/KaKs findings against the current main-project source, tests, deployment paths, and existing real-job evidence. Diagnose only; do not edit product code.

Success Criteria

• Every reported issue has current source or runtime evidence.
• Historical-only or already-fixed findings are explicitly separated.
• Each issue is traced to its owning layer and root cause.
• PPI and KaKs are assessed independently so one stage is not used as evidence for the other.

Phases

• [complete] Phase 1: Establish current Git/code/deployment baseline.
• [complete] Phase 2: Trace PPI planning -> preflight -> backend -> skill -> manifest/status.
• [complete] Phase 3: Trace KaKs planning -> preflight -> backend -> CLI/skill -> manifest/status.
• [complete] Phase 4: Run focused tests and inspect existing real-job evidence.
• [complete] Phase 5: Classify confirmed, fixed, environmental, and unverified findings.

Constraints

• No production code edits.
• No service restart or new real analysis task unless separately authorized.
• Do not infer current defects solely from the July/August records.

Errors Encountered

Error	Attempt	Resolution
codegraph explore returned no output for both PPI and KaKs traces	1	Treat the mounted index as unavailable; fall back to targeted rg and symbol reads without rebuilding it.