docs(mos): format Option 2 qualification report

docs/tess/qualification/2026-07-14-option2-runtime-portability.md

@@ -39,7 +39,7 @@ Primary blockers:
 ### AC disposition
 
 | AC  | Result            | Evidence                                                                        |
-|---|---|---|
+| --- | ----------------- | ------------------------------------------------------------------------------- |
 | 01  | **Fail**          | No `mosaic tess`; no bidirectional same-session chat/stream E2E                 |
 | 02  | **Fail**          | Generic CLI exists, but fleet/Matrix providers are unreachable in production    |
 | 03  | Pass              | Pi profile/model/reasoning/effective-policy tests passed                        |
@@ -208,7 +208,7 @@ Missing pieces:
 # 5. Minimal follow-up issue decomposition
 
 | Order | Issue                                       | Minimum acceptance criteria                                                                                                                                                                                                                                          |
-|---|---|---|
+| ----- | ------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | 1     | **Logical identity and security fencing**   | Server-derived `{tenant, logicalAgentId, connectorId, harness, leaseEpoch, scopes, expiry}`; signed/fenced execution grant; stale/forged/cross-tenant grants denied and audited; no connector credential in handoffs                                                 |
 | 2     | **Durable connector lease**                 | PostgreSQL-backed exclusive lease with CAS, monotonic epoch, TTL/heartbeat, explicit takeover, and gateway rejection of stale holders; connectors for Claude Code, Pi, and Codex                                                                                     |
 | 3     | **Canonical handoff/checkpoint**            | Versioned, sealed schema containing canonical mission/task/git references, checkpoint digest, causal sequence, required capabilities, pending/ambiguous operation references, and source/destination acknowledgement; no raw secrets or mandatory harness transcript |