arch-cleanup

原文涵盖的主题

• Carve one boundary slice
• Procedure
• When is full compliance needed?

Preflight: run la-doctor --plugin --require-config once per session before using any la- or dr- command. If it reports the missing-config finding (the one naming /la:init), run the fast path of the la:init skill, then re-run this preflight; stop and show the user its output on anything it still reports, or on any other failure. A slice moves code until a batch of grandfathered edges dies, with a deterministic gate proving nothing dangles. It is behaviour-preserving: no new behaviour, no new tests, no OpenSpec spec deltas. The legacy-arrow ratchet plus the green suite ARE the spec, so the /la:pr stage flow does not apply — but each slice still gets its own branch and PR, and its own issue when the repo has a tracker. 1. Pick the slice. List the model's #legacy arrows (their count is legacyarrows.baseline in index.yaml); propose a coherent batch — one importer module, one edge family (e.g. python.core -> python.sql.render), or one node extraction. Arrows live inside their language root, so a slice stays within one language. Keep it ≤ 10 edges. Confirm the choice with the user. 2. Read the touched elements' arc42 (and their ancestors') + LikeC4 view. The principles decide the resoluti

这里只展示节选，请以完整原文和当前要求为准。