On 9 September 2026, /Edu/SelfAssessment on cloud memex reported “Area not found”. Exact-path MCP searches found neither Edu/SelfAssessment nor Edu/LearningJourney visible, and the feature's PR #1567 was open (merged: false). The first established delivery gap was unreleased source. A renderer or dependency mismatch was not established by that error. The new diagnostic skill keeps these cases separate.

The CI run also explains why this feature incurred a broad build. The diff changed Edu, Feedback and Store. Selection reported all 33 rest-lane binary bundles reachable through package dependencies; the floor lane selected four more. Its log explicitly reported module build ledger: OFF. AI tests took about 14 minutes and the slowest of four portal-host shards about 36 minutes. These are observed job durations, not a prediction of the speedup.

The immediate delivery change is to separate Edu from the shared Store and feedback-triage work. The assessment should not wait for unrelated sales dispatch behavior. Its own NodeType, access, binding and browser checks still belong to its delivery.

The existing unified build already distinguishes selection from content-addressed reuse. Before adding separate heavy/light workflows, enable and verify that mechanism with the documented CI identity, ledger permission and artifact-read access. A cold key or a different platform must still build and test. Dependency content changes can also change package keys: binary build reuse and content-bake selection are different optimization boundaries and must be measured separately. The remaining unconditional portal-host shards require an independently reviewed dependency-selection change; enabling the module ledger does not remove those shards.

Runtime protection also requires the actual adoption contract. The current module-versioning manual states that minMeshVersion is advisory at runtime; it is not a sequencing barrier. Validate the published dependency set and actual loadability before attributing missing features to a floor. Keep platform/shared workflow changes out of the feature PR, and retain all required verification and publication receipts.