Skip to content

Commit 467dae0

Browse files
committed
chore: point capture-domain source-of-truth comments at the relocated capture-kit modules
1 parent e919570 commit 467dae0

6 files changed

Lines changed: 6 additions & 6 deletions

File tree

‎packages/contracts/src/android-system-chrome.ts‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ import type { SnapshotNode } from '@agent-device/kernel/snapshot';
22

33
/**
44
* Android status-bar/navigation-bar chrome identity, shared by the settle-chrome
5-
* classifier (`core/snapshot-chrome.ts`) and the helper content classifier
5+
* classifier (`packages/capture-kit/src/snapshot-chrome.ts`) and the helper content classifier
66
* (`packages/platform-android/src/snapshot-content-recovery.ts`). SystemUI also hosts actionable
77
* overlays — volume panel, media pickers, the shade itself — so chrome is never a
88
* package-level fact: only the status/nav-bar container's subtree is chrome.

‎packages/selectors/src/internal/parse.ts‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ export const SELECTOR_KEY_NAMES: readonly SelectorKey[] = [...ALL_KEYS];
5656

5757
// Role/element-type words that show up as accessibility roles, not selector keys (e.g. the
5858
// `button` in `button="Push Article"`). Superset of the ROLE_LABELS vocabulary in
59-
// src/snapshot/snapshot-lines.ts (plus a few common role words like list/tab/alert/dialog/header,
59+
// packages/capture-kit/src/snapshot/snapshot-lines.ts (plus a few common role words like list/tab/alert/dialog/header,
6060
// minus valid selector keys such as `text`, which ALL_KEYS short-circuits before this set is
6161
// consulted), kept locally to avoid a selectors -> snapshot layering dependency. Drifts silently
6262
// if ROLE_LABELS grows; that's fine here since this only sharpens a hint, not validates anything.

‎src/daemon/__tests__/interaction-outcome-policy.test.ts‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -195,7 +195,7 @@ test('classifyBaselineSurfaceEvidence excludes the keyboard container from discr
195195
// #1563 review, finding 2: a container-only exclusion still misses keyboard
196196
// DESCENDANTS (individual keys) and SIBLINGS (assistant buttons like "Next
197197
// keyboard"/"Dictate", which live outside the container per
198-
// src/core/snapshot-chrome.ts's collectKeyboardChrome doc comment — a
198+
// packages/capture-kit/src/snapshot-chrome.ts's collectKeyboardChrome doc comment — a
199199
// container-descendant walk alone provably misses them, hence the whole-
200200
// window classification that module reuses here via collectKeyboardChromeRefs).
201201
test('classifyBaselineSurfaceEvidence excludes keyboard DESCENDANTS and window SIBLINGS, not just the container, from discriminating overlap', () => {

‎src/daemon/__tests__/post-gesture-stabilization-fixtures.ts‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -118,7 +118,7 @@ export function applicationRootNode() {
118118
* `[Keyboard]` container PLUS a sibling "Next keyboard" assistant button
119119
* under the SAME window — a container-descendant-only walk provably misses
120120
* the sibling (see `collectKeyboardChrome`'s doc comment in
121-
* src/core/snapshot-chrome.ts, the source of truth this fixture's shape is
121+
* packages/capture-kit/src/snapshot-chrome.ts, the source of truth this fixture's shape is
122122
* drawn from: "a SIBLING subtree holding the 'Next keyboard' and 'Dictate'
123123
* buttons — siblings of the container, so a container-descendant walk alone
124124
* provably misses them"). Neither entry is the container itself, so sharing

‎src/daemon/android-snapshot-timeout-evidence.ts‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ import {
2727
*
2828
* The two things that are not daemon assembly moved out: whether a failure is the
2929
* accessibility-timeout shape is a policy
30-
* (`src/snapshot/snapshot-timeout-policy.ts`), and the published evidence shape is
30+
* (`packages/capture-kit/src/snapshot/snapshot-timeout-policy.ts`), and the published evidence shape is
3131
* vocabulary (`src/daemon/snapshot-timeout-evidence.ts`, whose only consumer is this
3232
* module). What remains here is the ordering that
3333
* genuinely needs the daemon: resolving a bound screenshot runtime, writing the artifact,

‎src/daemon/session-snapshot-freshness.ts‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ import type { SessionState } from './session-state.ts';
1717
* Session binding for the neutral snapshot-freshness facet (#1983).
1818
*
1919
* The staleness policy, its thresholds and the recovery loop live in
20-
* `src/snapshot/snapshot-freshness/`. What stays here is the part that is genuinely daemon
20+
* `packages/capture-kit/src/snapshot/snapshot-freshness/`. What stays here is the part that is genuinely daemon
2121
* assembly: reading and retiring the window that hangs off store-owned `SessionState`, and
2222
* choosing the comparison baseline from session snapshot lineage. This module is the declared
2323
* R7 owner of `SessionState.androidSnapshotFreshness`.

0 commit comments

Comments
 (0)