You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 5134f53
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: CONTEXT.md
+1-5Lines changed: 1 addition & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,11 +54,7 @@
54
54
- Parity table: golden JSON fixture under `contracts/fixtures/` consumed by both vitest and the runner's gated Swift tests, so a cross-language rule (e.g. tap-point policy) cannot drift silently. Change the rule only via the table.
55
55
- Coverage manifest: `CONTRACT_COVERAGE` export beside each interaction contract test file claiming which matrix cells it proves; the coverage gate requires every enforced/delegated cell to be claimed and rejects overclaims of waived cells.
56
56
- Delegation-on-error: a fast path falling back to the runtime path on semantic failure shapes. It closes failure-side guarantee cells only — never success-path parity.
57
-
- Ref frame: session-scoped authorization namespace containing the accessibility refs that a caller may use for mutation. It is distinct from operational observations used internally for selector matching, settling, freshness, and diagnostics.
58
-
- Ref-frame epoch: seeded monotonic version of the current ref frame, exposed once per issuing response as `refsGeneration`. It advances when a frame is published, superseded, or expired; it does not make refs stable across frames.
59
-
- Ref-frame activation: session transition that makes a captured namespace current for subsequent mutation admission. Complete activation authorizes its plain-ref namespace; partial activation authorizes only the explicitly issued generation-pinned refs. An explicit snapshot leaf may activate a frame for later predeclared batch/replay steps even when the outer response elides the tree.
60
-
- Ref issuance: client- or workflow-visible publication of refs with their ref-frame epoch. Internal freshness, recovery, diagnostic, and cached captures do not issue refs.
61
-
- Ref generation pin: optional `~s<n>` suffix on an @ref carrying the ref-frame epoch that issued it. Accepted as input everywhere; daemon tree payloads carry the epoch once at response level rather than per node, MCP may render or forward pinned refs, and durable replay scripts strip pins because epochs are session-specific.
57
+
- Ref generation pin: optional `~s<n>` suffix on an @ref carrying the snapshot generation it was minted from. Accepted as input everywhere, emitted by no tree output (snapshot token budget), auto-appended by the MCP layer, stripped and ignored by replay.
62
58
- Settled observation: opt-in (`--settle`) post-action payload on press/click/fill/longpress — the quiet-window stable loop re-captures until the UI settles, and the response carries the diff vs the pre-action tree (changed lines only, added lines with fresh refs, `refsGeneration` when the settled tree was stored). Best-effort: never fails the action; `settled: false` plus a hint on never-quiet content.
63
59
- Snapshot capture plan: per-strategy ordered chain of iOS snapshot capture backends (recursive tree, query sweep, private AX) run by one plan runner under a shared wall-clock budget; recovery ordering is declared data, never a per-call-site branch.
64
60
- Snapshot quality verdict: structured outcome (state, backend, reason code, effective depth, collapsed leaves) computed once by the plan runner and shipped with every planned snapshot payload; the daemon and CLI render it instead of re-deriving degradation from node shapes.
0 commit comments