tooling+plan: harness SX_SERVING_JIT=1 fix, conformance timeout bump, specialised editors

- live-check.sh + run-picker-check.sh now set SX_SERVING_JIT=1 to MATCH THE CONTAINER:
  that env gates the http-listen IO resolver, so without it perform-heavy paths (the is-a/
  tags picker's reach-down BFS) falsely raise VmSuspended -> 500 in the harness while the
  live site is fine (confirmed live is-a picker = 200). Harness must mirror what the
  container runs.
- conformance.sh: 600s -> 1200s cap (overridable via SX_CONF_TIMEOUT). A sibling loop at
  load ~6 pushed the Datalog-heavy blog suite past 600s -> false 'no suite results parsed'.
- plan: types can specify SPECIALISED EDITORS — a type's :editor slot = a content-addressed
  editor component (WYSIWYG, map picker) shipped to the client like ~relate-picker. Generic
  form is the default, not the ceiling; spectrum = generic -> per-field widget -> :editor.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

lib/host/conformance.sh

@@ -142,10 +142,11 @@ emit_eval () { echo "(epoch $EPOCH)"; echo "(eval \"$1\")"; EPOCH=$((EPOCH+1));
   done
 } > "$TMPFILE"
 
-# 600s: the blog suite drives the relations graph hard (every is-a/types-of/
-# instances-of query re-saturates the Datalog db), so it's CPU-bound and slower
-# under shared-box contention. 300s was tripping a false truncation.
-OUTPUT=$(timeout 600 "$SX_SERVER" < "$TMPFILE" 2>&1 || true)
+# 1200s: the blog suite drives the relations graph hard (every is-a/types-of/
+# instances-of query re-saturates the Datalog db), so it's CPU-bound and much slower
+# under shared-box contention (a sibling loop at load ~6 pushed it past 600s -> false
+# "no suite results parsed" truncation). Override with SX_CONF_TIMEOUT for a tighter cap.
+OUTPUT=$(timeout "${SX_CONF_TIMEOUT:-1200}" "$SX_SERVER" < "$TMPFILE" 2>&1 || true)
 
 # Fail LOUD on any load/eval error. A test file that errors mid-load silently
 # truncates its suite — the runner returns only the tests that ran before the