top-cs-polishinglisted

# Top CS Paper Polishing ## Route the request 1. Read `manifest.yaml` and every `always_load` path. 2. Detect and state venue, paper type, section, language, revision mode, artifact scope, evidence state, submission stage, citation verification, and figure handoff. 3. Load only the static fragments mapped to those values. 4. Open deeper references only when an `on_demand` condition applies. 5. Use `generic` for unsupported venue/year combinations and warn that official rules require verification. ## Execute 1. Extract immutable facts: quantities, comparison direction, conditions, citations, equations, uncertainty, and explicit boundaries. 2. Build or update the terminology ledger for multi-paragraph work. 3. Diagnose in this order: framing, rhetorical structure, evidence connection, terminology, and sentence form. 4. Respect the selected revision mode: keep `light-edit` local, permit reordering in `structural-revision`, and prove information preservation in `compression`. 5. Revise in the order `paper role -> section job -> paragraph logic -> claim/evidence/boundary -> sentence form`. 6. Record every material change and any claim-strength, citation, or figure-reference shift in the revision ledger. 7. Verify preserved facts, citations, LaTeX, terminology, and reader workflow; report what was compiled, rendered, structurally checked, or not verified. Preserve scientific meaning and never silently strengthen novelty, causality, generality, or significance. Preserve LaTeX c