Prune stale editor and Wayland surface area

Stop shipping code that implied Aman supported a two-pass editor, external API cleanup, or a Wayland scaffold when the runtime only exercises single-pass local cleanup on X11.\n\nCollapse aiprocess to the active single-pass Llama contract, delete desktop_wayland and the empty wayland extra, and make model_eval reject pass1_/pass2_ tuning keys while keeping pass1_ms/pass2_ms as report compatibility fields.\n\nRemove the unused pillow dependency, switch to SPDX-style license metadata, and clean setuptools build state before packaging so deleted modules do not leak into wheels. Update the methodology and repo guidance docs, and add focused tests for desktop adapter selection, stale param rejection, and portable wheel contents.\n\nValidate with uv lock, python3 -m unittest discover -s tests -p 'test_*.py', python3 -m py_compile src/*.py tests/*.py, and python3 -m build --wheel --sdist --no-isolation.

docs/model-eval-methodology.md

@@ -8,17 +8,14 @@ Find a local model + generation parameter set that significantly reduces latency
 
 All model candidates must run with the same prompt framing:
 
-- XML-tagged system contract for pass 1 (draft) and pass 2 (audit)
+- A single cleanup system prompt shared across all local model candidates
 - XML-tagged user messages (`<request>`, `<language>`, `<transcript>`, `<dictionary>`, output contract tags)
-- Strict JSON output contracts:
-  - pass 1: `{"candidate_text":"...","decision_spans":[...]}`
-  - pass 2: `{"cleaned_text":"..."}`
+- Strict JSON output contract: `{"cleaned_text":"..."}`
 
 Pipeline:
 
-1. Draft pass: produce candidate cleaned text + ambiguity decisions
-2. Audit pass: validate ambiguous corrections conservatively and emit final text
-3. Optional heuristic alignment eval: run deterministic alignment against
+1. Single local cleanup pass emits final text JSON
+2. Optional heuristic alignment eval: run deterministic alignment against
    timed-word fixtures (`heuristics_dataset.jsonl`)
 
 ## Scoring
@@ -37,6 +34,13 @@ Per-run latency metrics:
 
 - `pass1_ms`, `pass2_ms`, `total_ms`
 
+Compatibility note:
+
+- The runtime editor is single-pass today.
+- Reports keep `pass1_ms` and `pass2_ms` for schema stability.
+- In current runs, `pass1_ms` should remain `0.0` and `pass2_ms` carries the
+  full editor latency.
+
 Hybrid score:
 
 `0.40*parse_valid + 0.20*exact_match + 0.30*similarity + 0.10*contract_compliance`