The ultimate harness for coding agents and beyond. All your agents. All your machines. One command center. Start with code, then follow your curiosity and build across disciplines: CAD, circuits, robots, games and music.
TypeScript 3d-modelingagent-frameworkagent-harnessai-agentscadclaude-codecodexcoding-agentsdeveloper-toolsesp32game-developmentmcp-servermulti-agentopen-hardwareopencodeopenharnesspcbroboticsterminaltmux
feat(usage): keep staff and TestFlight apart, add phone onboarding names
tonyfef49429a2cb
diff --git a/backend/src/analytics/productHealth.test.ts b/backend/src/analytics/productHealth.test.tsindex c5305529a..8d56505d1 100644--- a/backend/src/analytics/productHealth.test.ts+++ b/backend/src/analytics/productHealth.test.ts@@ -34,6 +34,12 @@ it('creates two independent margins with no joint dimensions or arbitrary labelsexpect(cleanUsageContext({ ...context, release: 'PRIVATE/custom-build', private: 'PRIVATE' })).toEqual({ ...context, release: 'unknown' })expect(cleanUsageContext({ ...context, platform: 'PRIVATE' })).toBeUndefined()})+it('takes a tester\'s build as its own channel, with no release or platform margins', () => {+ const phone = { surface: 'phone', release: '1.0.7', platform: 'ios', channel: 'testing' } as const+ expect(cleanUsageContext(phone)).toEqual(phone)+ expect(healthBreakdowns(phone, 'ui_phone_computer_wait_started')).toEqual([])+ expect(cleanUsageContext({ ...phone, channel: 'beta' })).toBeUndefined()+})it('splits phone onboarding counts by release and platform, and drops a development build', () => {const phone = { surface: 'phone', release: '1.0.3', platform: 'android', channel: 'production' } as constexpect(healthBreakdowns(phone, 'ui_phone_computer_wait_started')).toEqual([diff --git a/backend/src/lib/productUsage.test.ts b/backend/src/lib/productUsage.test.tsindex 34203c8ac..d169dd5e9 100644--- a/backend/src/lib/productUsage.test.ts+++ b/backend/src/lib/productUsage.test.ts@@ -19,7 +19,7 @@ const db = vi.hoisted(() => ({vi.mock('./prisma.js', () => ({ prisma: db }))// A configured key, so deletion through setProductUsageChoice and the legacy delete path is real.vi.mock('../config/env.js', () => ({ env: { PRODUCT_USAGE_SUBJECT_KEY: 'k'.repeat(32) } }))-import { activitySubject, deleteActivity, deleteLegacyProductUsage, ensureProductUsageExpiry, markActivity, resetActivityMarksForTests, ingestProductUsage, ingestSetupUsage, productUsageChoice, recordRelayUsage, setProductUsageChoice } from './productUsage.js'+import { activitySubject, deleteActivity, deleteLegacyProductUsage, ensureProductUsageExpiry, markActivity, resetActivityMarksForTests, resetStaffAccountsForTests, ingestProductUsage, ingestSetupUsage, productUsageChoice, recordRelayUsage, setProductUsageChoice } from './productUsage.js'import { LAUNCH_ERROR_CODES, LAUNCH_ERROR_FAMILIES, PRODUCT_USAGE_METRICS, type ProductUsageReport } from '../types/productUsage.js'it('commits release and platform margins under the same unlinked receipt and discards development reports', async () => {@@ -45,9 +45,48 @@ beforeEach(() => {db.productUsagePreference.findUnique.mockResolvedValue(null)db.analyticsMachineState.findFirst.mockResolvedValue(null)resetActivityMarksForTests()+ resetStaffAccountsForTests()db.user.findUnique.mockResolvedValue({ createdAt: new Date('2026-10-01T08:00:00Z'), email: '[email protected]' })})+describe('kept apart', () => {+ const stored = (): string[] => db.$runCommandRaw.mock.calls.flatMap(([command]) =>+ (command as { updates: Array<{ q: { metric: string } }> }).updates.map(update => update.q.metric))++ it('keeps the team\'s own accounts under staff:, with their margins and late marks', async () => {+ db.user.findUnique.mockResolvedValue({ createdAt: new Date('2026-10-01T08:00:00Z'), email: '[email protected]' })+ const context = { surface: 'phone', release: '1.0.7', platform: 'ios', channel: 'production' } as const+ expect(await ingestProductUsage('team-account', { ...report, day: '2026-10-12', context }, now)).toEqual({ accepted: true })+ expect(stored()).toEqual(expect.arrayContaining(['staff:turns_started', 'staff:breakdown:release:phone:1.0.7:turns_started',+ 'staff:health_phone_report_late']))+ expect(stored().every(metric => metric.startsWith('staff:'))).toBe(true)+ })++ it('keeps a tester\'s build under testing:, without margins, whoever signed in', async () => {+ const context = { surface: 'phone', release: '1.0.7', platform: 'ios', channel: 'testing' } as const+ expect(await ingestProductUsage('someone', { ...report, context }, now)).toEqual({ accepted: true })+ expect(stored()).toEqual(['testing:turns_started', 'testing:turns_ended'])+ // A build's channel decides it: no account is read for it.+ expect(db.user.findUnique).not.toHaveBeenCalled()+ })++ it('leaves everyone else\'s totals as they were, and asks for an account once', async () => {+ const context = { surface: 'phone', release: '1.0.7', platform: 'ios', channel: 'production' } as const+ await ingestProductUsage('person', { ...report, context }, now)+ await ingestProductUsage('person', { ...report, id: 'cf1c5a03-388c-4265-b5fb-a4c3d47e4080', context }, now)+ expect(stored().filter(metric => metric.includes(':') && !metric.startsWith('breakdown:'))).toEqual([])+ expect(stored()).toContain('turns_started')+ expect(db.user.findUnique).toHaveBeenCalledOnce()+ })++ it('reads no account for signed-out setup counts', async () => {+ expect(await ingestSetupUsage({ id: 'cf1c5a03-388c-4265-b5fb-a4c3d47e4081', day: '2026-10-13',+ counters: { setup_phone_first_open: 1 } }, now)).toEqual({ accepted: true })+ expect(stored()).toEqual(['setup_phone_first_open'])+ expect(db.user.findUnique).not.toHaveBeenCalled()+ })+})+it('keeps the client and server vocabulary identical', () => {expect(readFileSync(new URL('../../../cli/src/lib/productUsageContract.ts', import.meta.url), 'utf8')).toBe(readFileSync(new URL('../types/productUsage.ts', import.meta.url), 'utf8'))diff --git a/backend/src/lib/productUsage.ts b/backend/src/lib/productUsage.tsindex 57741c2d6..6240a035c 100644--- a/backend/src/lib/productUsage.ts+++ b/backend/src/lib/productUsage.ts@@ -53,6 +53,36 @@ export async function ingestSetupUsage(report: SetupUsageReport, now = new Date(return ingestCounters(report)}+// Which accounts are the team's, by id, as [apartPrefix] last read them: an email does not change under its+// id, and a report a minute from every app should not cost a lookup each. Bounded; cleared when full.+const staffAccounts = new Map<string, boolean>()+const STAFF_ACCOUNTS_MAX = 10_000++/**+ * The prefix a report's totals are kept under, apart from the ones every review reads (`usage:daily` asks for+ * none of these): `testing:` for a tester's build (the phone from TestFlight, `context.channel: 'testing'`),+ * `staff:` for the team's own accounts (`@autonomous.ai`, as activity marks already flag them). On 16–19 October+ * 2026 the team was 8–30% of the phone's people each day, and a TestFlight build's counts were the App Store's.+ * Kept, not dropped, so either can still be read on its own. Signed-out setup reports have no account to ask.+ *+ * Read inside the admitted transaction, beside the permission check: a lookup ahead of admission would put a+ * database read per report outside the bound that admission keeps on this process.+ */+async function apartPrefix(tx: Pick<Prisma.TransactionClient, 'user'>, context: ProductUsageContext | undefined,+ userId: string | undefined): Promise<string> {+ if (context?.channel === 'testing') return 'testing:'+ if (!userId) return ''+ let staff = staffAccounts.get(userId)+ if (staff === undefined) {+ const user = await tx.user.findUnique({ where: { id: userId }, select: { email: true } })+ staff = !!user?.email.toLowerCase().endsWith(STAFF_EMAIL)+ if (staffAccounts.size >= STAFF_ACCOUNTS_MAX) staffAccounts.clear()+ staffAccounts.set(userId, staff)+ }+ return staff ? 'staff:' : ''+}+export function resetStaffAccountsForTests(): void { staffAccounts.clear() }+async function ingestCounters(report: SetupUsageReport & { revision?: number; context?: ProductUsageContext }, userId?: string, now = new Date()) {if (report.context?.channel === 'development') return { accepted: true, reason: 'DEVELOPMENT' }const increments: UsageIncrement[] = []@@ -79,10 +109,11 @@ async function ingestCounters(report: SetupUsageReport & { revision?: number; coif (!choice.enabled || choice.revision !== report.revision) return { accepted: false, reason: 'CHOICE_CHANGED', ...choice }}// Receipt and increments commit together; a lost HTTP response can be retried with the same id.+ const apart = await apartPrefix(tx, report.context, userId)await tx.productUsageReceipt.create({ data: {id: report.id, expiresAt: new Date(Date.parse(report.day) + (PRODUCT_USAGE_DAYS + 1) * DAY),} })- await incrementUsageTotals(tx, increments)+ await incrementUsageTotals(tx, apart ? increments.map(i => ({ ...i, metric: apart + i.metric })) : increments)return { accepted: true }})} catch (error) {diff --git a/backend/src/routes/productUsage.test.ts b/backend/src/routes/productUsage.test.tsindex bd29c42cc..a626710db 100644--- a/backend/src/routes/productUsage.test.ts+++ b/backend/src/routes/productUsage.test.ts@@ -164,6 +164,13 @@ it('takes the Desktop\'s Add Phone card and each way into Add Phone, and no othe}})+it('takes a tester\'s build as its own channel, and the phone\'s new onboarding names, and no other channel', async () => {+ const context = { surface: 'phone', release: '1.0.7', platform: 'ios', channel: 'testing' }+ const counters = { ui_phone_first_open: 1, ui_phone_sign_in_new_account: 1, ui_phone_computer_wait_joined_after_leaving: 1 }+ expect((await submit({ ...good, context, counters })).statusCode).toBe(200)+ expect((await submit({ ...good, context: { ...context, channel: 'beta' } })).statusCode).toBe(400)+})+it('rejects extra context, custom versions and device fingerprints without echoing them', async () => {const context = { surface: 'desktop', release: '1.2.73', platform: 'macos', channel: 'production' }for (const c of [{ ...context, path: 'PRIVATE_CANARY' }, { ...context, release: 'PRIVATE_CANARY' },diff --git a/backend/src/routes/productUsage.ts b/backend/src/routes/productUsage.tsindex d3ceb1180..84426a6d2 100644--- a/backend/src/routes/productUsage.ts+++ b/backend/src/routes/productUsage.ts@@ -10,7 +10,7 @@ const contextSchema = z.strictObject({surface: z.enum(['cli', 'desktop', 'phone']),release: z.string().max(11).refine(v => v === 'unknown' || releaseBucket(v) === v),platform: z.enum(['macos', 'linux', 'windows', 'ios', 'android', 'other']),- channel: z.enum(['production', 'development']),+ channel: z.enum(['production', 'development', 'testing']),})const daySchema = z.string().regex(/^\d{4}-\d{2}-\d{2}$/)diff --git a/backend/src/types/productHealthContract.ts b/backend/src/types/productHealthContract.tsindex 66dc2e1b4..7fcfced03 100644--- a/backend/src/types/productHealthContract.ts+++ b/backend/src/types/productHealthContract.ts@@ -57,7 +57,8 @@ export interface ProductUsageContext {surface: 'cli' | 'desktop' | 'phone'release: stringplatform: 'macos' | 'linux' | 'windows' | 'ios' | 'android' | 'other'- channel: 'production' | 'development'+ // `testing`: a tester's build of a store release (the phone from TestFlight), kept apart from the totals.+ channel: 'production' | 'development' | 'testing'}/** Public numeric release only. Custom build names, hashes and suffixes cannot become labels. */export function releaseBucket(value: unknown): string {@@ -67,7 +68,7 @@ export function cleanUsageContext(value: unknown): ProductUsageContext | undefinif (!value || typeof value !== 'object') returnconst c = value as ProductUsageContextif (!['cli', 'desktop', 'phone'].includes(c.surface) || !['macos', 'linux', 'windows', 'ios', 'android', 'other'].includes(c.platform)- || !['production', 'development'].includes(c.channel)) return+ || !['production', 'development', 'testing'].includes(c.channel)) returnreturn { surface: c.surface, release: releaseBucket(c.release), platform: c.platform, channel: c.channel }}diff --git a/backend/src/types/productUsage.ts b/backend/src/types/productUsage.tsindex 245ef4185..a84601d60 100644--- a/backend/src/types/productUsage.ts+++ b/backend/src/types/productUsage.ts@@ -36,10 +36,16 @@ export const PRODUCT_USAGE_LONG_MEASURES = ['1m_to_5m', '5m_to_15m', '15m_to_1h'* `resumed`: the step started in an app run that did not sign in (reopened mid-step), so it is not a* new person; the rest are the step's own ways out or walls. The sign_in marks are counted with a* sign-in that went through: `retried`, an attempt before it in this app run failed or was- * cancelled; `switched`, it used another button than the first one tried. */+ * cancelled; `switched`, it used another button than the first one tried; `new_account`, the account+ * was created by this sign-in (minutes old: its first Harness sign-in anywhere), not one coming back.+ * `computer_wait_joined_after_leaving`: the computer the wait was for turned up after the app had left+ * that screen, which ends the wait in no `ok` of its own (16–19 October 2026: 5 `ok` in 49 fresh waits,+ * while 91% of the phone's people had a computer on the same account those days). */export const PRODUCT_USAGE_ONBOARDING_MARKS = ['ui_phone_sign_in_retried', 'ui_phone_sign_in_switched',+ 'ui_phone_sign_in_new_account','ui_phone_computer_wait_resumed', 'ui_phone_computer_wait_not_you',- 'ui_phone_computer_wait_link_shared', 'ui_phone_session_open_resumed', 'ui_phone_session_open_blocked_password',+ 'ui_phone_computer_wait_link_shared', 'ui_phone_computer_wait_joined_after_leaving',+ 'ui_phone_session_open_resumed', 'ui_phone_session_open_blocked_password','ui_phone_session_open_blocked_offline', 'ui_phone_first_message_resumed'] as constexport const PRODUCT_USAGE_ONBOARDING_METRICS = [...PRODUCT_USAGE_ONBOARDING_MARKS,...PRODUCT_USAGE_LONG_FLOWS.flatMap(flow => PRODUCT_USAGE_LONG_MEASURES.map(measure => `ui_phone_${flow}_${measure}` as const)),@@ -85,6 +91,9 @@ export const PRODUCT_USAGE_SETUP_METRICS = [...PRODUCT_USAGE_SURFACES.flatMap(su// download put its agent in place, and how long it took. Engine names only, never a path or log line....PRODUCT_USAGE_SETUP_DOWNLOADS.flatMap(engine => PRODUCT_USAGE_SETUP_DOWNLOAD_MEASURES.map(measure => `setup_desktop_agent_download_${engine}_${measure}` as const)),+ // The phone's first launch after an install, once (a local flag, never sent): the step between a store's+ // download and a sign-in, which nothing else counts. Signed in already at that launch, it is `ui_phone_first_open`.+ 'setup_phone_first_open',] as const/** A new-harness, create or resume refusal outside the four fixed kinds (setup, auth, unavailable,* invalid), by its code: the daemon's own fixed error names, lower-cased. On 2026-10-16 production counted@@ -166,6 +175,7 @@ export const PRODUCT_USAGE_METRICS = [...PRODUCT_USAGE_ONBOARDING_METRICS,...PRODUCT_USAGE_PHONE_SCREEN_METRICS,...PRODUCT_USAGE_ADD_PHONE_METRICS,+ 'ui_phone_first_open',// Written by the backend itself: a report that named counters this backend does not know yet, which// it kept without them (routes/productUsage.ts). One per report, never the names.'health_cli_report_unknown_metric', 'health_desktop_report_unknown_metric', 'health_phone_report_unknown_metric',diff --git a/cli/src/lib/productHealthContract.ts b/cli/src/lib/productHealthContract.tsindex 66dc2e1b4..7fcfced03 100644--- a/cli/src/lib/productHealthContract.ts+++ b/cli/src/lib/productHealthContract.ts@@ -57,7 +57,8 @@ export interface ProductUsageContext {surface: 'cli' | 'desktop' | 'phone'release: stringplatform: 'macos' | 'linux' | 'windows' | 'ios' | 'android' | 'other'- channel: 'production' | 'development'+ // `testing`: a tester's build of a store release (the phone from TestFlight), kept apart from the totals.+ channel: 'production' | 'development' | 'testing'}/** Public numeric release only. Custom build names, hashes and suffixes cannot become labels. */export function releaseBucket(value: unknown): string {@@ -67,7 +68,7 @@ export function cleanUsageContext(value: unknown): ProductUsageContext | undefinif (!value || typeof value !== 'object') returnconst c = value as ProductUsageContextif (!['cli', 'desktop', 'phone'].includes(c.surface) || !['macos', 'linux', 'windows', 'ios', 'android', 'other'].includes(c.platform)- || !['production', 'development'].includes(c.channel)) return+ || !['production', 'development', 'testing'].includes(c.channel)) returnreturn { surface: c.surface, release: releaseBucket(c.release), platform: c.platform, channel: c.channel }}diff --git a/cli/src/lib/productUsageContract.ts b/cli/src/lib/productUsageContract.tsindex 245ef4185..a84601d60 100644--- a/cli/src/lib/productUsageContract.ts+++ b/cli/src/lib/productUsageContract.ts@@ -36,10 +36,16 @@ export const PRODUCT_USAGE_LONG_MEASURES = ['1m_to_5m', '5m_to_15m', '15m_to_1h'* `resumed`: the step started in an app run that did not sign in (reopened mid-step), so it is not a* new person; the rest are the step's own ways out or walls. The sign_in marks are counted with a* sign-in that went through: `retried`, an attempt before it in this app run failed or was- * cancelled; `switched`, it used another button than the first one tried. */+ * cancelled; `switched`, it used another button than the first one tried; `new_account`, the account+ * was created by this sign-in (minutes old: its first Harness sign-in anywhere), not one coming back.+ * `computer_wait_joined_after_leaving`: the computer the wait was for turned up after the app had left+ * that screen, which ends the wait in no `ok` of its own (16–19 October 2026: 5 `ok` in 49 fresh waits,+ * while 91% of the phone's people had a computer on the same account those days). */export const PRODUCT_USAGE_ONBOARDING_MARKS = ['ui_phone_sign_in_retried', 'ui_phone_sign_in_switched',+ 'ui_phone_sign_in_new_account','ui_phone_computer_wait_resumed', 'ui_phone_computer_wait_not_you',- 'ui_phone_computer_wait_link_shared', 'ui_phone_session_open_resumed', 'ui_phone_session_open_blocked_password',+ 'ui_phone_computer_wait_link_shared', 'ui_phone_computer_wait_joined_after_leaving',+ 'ui_phone_session_open_resumed', 'ui_phone_session_open_blocked_password','ui_phone_session_open_blocked_offline', 'ui_phone_first_message_resumed'] as constexport const PRODUCT_USAGE_ONBOARDING_METRICS = [...PRODUCT_USAGE_ONBOARDING_MARKS,...PRODUCT_USAGE_LONG_FLOWS.flatMap(flow => PRODUCT_USAGE_LONG_MEASURES.map(measure => `ui_phone_${flow}_${measure}` as const)),@@ -85,6 +91,9 @@ export const PRODUCT_USAGE_SETUP_METRICS = [...PRODUCT_USAGE_SURFACES.flatMap(su// download put its agent in place, and how long it took. Engine names only, never a path or log line....PRODUCT_USAGE_SETUP_DOWNLOADS.flatMap(engine => PRODUCT_USAGE_SETUP_DOWNLOAD_MEASURES.map(measure => `setup_desktop_agent_download_${engine}_${measure}` as const)),+ // The phone's first launch after an install, once (a local flag, never sent): the step between a store's+ // download and a sign-in, which nothing else counts. Signed in already at that launch, it is `ui_phone_first_open`.+ 'setup_phone_first_open',] as const/** A new-harness, create or resume refusal outside the four fixed kinds (setup, auth, unavailable,* invalid), by its code: the daemon's own fixed error names, lower-cased. On 2026-10-16 production counted@@ -166,6 +175,7 @@ export const PRODUCT_USAGE_METRICS = [...PRODUCT_USAGE_ONBOARDING_METRICS,...PRODUCT_USAGE_PHONE_SCREEN_METRICS,...PRODUCT_USAGE_ADD_PHONE_METRICS,+ 'ui_phone_first_open',// Written by the backend itself: a report that named counters this backend does not know yet, which// it kept without them (routes/productUsage.ts). One per report, never the names.'health_cli_report_unknown_metric', 'health_desktop_report_unknown_metric', 'health_phone_report_unknown_metric',diff --git a/docs/product-measurement.md b/docs/product-measurement.mdindex ecce84a35..5596823aa 100644--- a/docs/product-measurement.md+++ b/docs/product-measurement.md@@ -19,7 +19,7 @@ automatically proven improvement. Changes still need review, tests and a deliber| Which features get tried and used again? | First measured installations and daily first/repeat feature reach | Locally deduplicated installation-days, not unique accounts. Reads the apps make on their own (history, history paging, Store list, model list; `PRODUCT_USAGE_AUTOMATIC_ACTIONS`) count reliability only. The Store and model lists get reach only from the request an app marks `userAction` when a person opens them (`<action>_user_*`, `PRODUCT_USAGE_USER_OPENED_ACTIONS`); history has none. || Where do app flows break? | Setup, Harness/tmux/clipboard steps, sign-in, workspace/remote connections, computer linking, viewer-pane opening and manual update checking/staging; a setup step whose tool was missing at a check (`setup_desktop_setup_<step>_missing`); the agents a new computer downloads beside setup (`setup_desktop_agent_download_<opencode\|codex\|claude>_started`, `_ok`, `_failed`, with under 1 min, 1–5 min and over 5 min) | Fixed started/ok/failed/cancelled/unknown counts and coarse duration buckets. Opening a viewer pane is not rendering its content; staging an update is not a successful relaunch. A setup step stays open from the first check until its tool is in place, so a tool that was missing and then installed is one ok step and one `_missing` mark; only a setup that ends failed fails its step. Earlier Desktop releases counted every check that found a tool missing as a failed step (on 2026-10-16 the Harness step read 72 failed of 221 while 0 setups failed): compare releases separately. `_missing` is any tool a check found absent or out of date (a Harness CLI older than this Desktop needs, on a computer already in use, counts too), not only new computers. A step left waiting (the review, a Linux Terminal handoff, manual mode, someone who walks away) now ends `unknown` at the 15-minute observation bound instead of `failed`, so expect `setup_*_unknown` to rise, mostly on Linux. `_missing` and the download counts are anonymous setup counts only. A download whose prerequisite (curl, Harness's Node) never arrived counts as started and failed; `ok` means the agent's program is in place, judged per engine. |-| Where does the phone's onboarding stall? | After sign-in: waiting for the first computer, opening its session, the first message, the notification prompt. A sign-in that went through, by button, counted again under the account's sharing. Waits past a minute split into 1–5 min, 5–15 min, 15 min–1 h and over 1 h for the computer and the first message. Once per step per sign-in: `resumed` (reopened in a run that did not sign in), "Not you? Sign out", the address sent from the share sheet, a joining computer that wants its password or is offline | Stage totals per day, not a linked funnel. Subtract `resumed` from starts for fresh starts; an unmatched start is a closed app or a step still waiting. A resumed step's duration starts at the reopening. Signed-in sign-in counts are successes only; failures and cancels before an account remain the signed-out counts', but a success is marked `retried` (a failed or cancelled try came first in that app run) or `switched` (another button was tried first). Phone reports carry release and iOS/Android, so every phone count also splits by those two margins (above 20 collector days); debug builds are not kept. A chosen sign-out sends what is queued first (up to 2 s), so "Not you? Sign out" reaches the totals. |+| Where does the phone's onboarding stall? | After sign-in: waiting for the first computer, opening its session, the first message, the notification prompt. A sign-in that went through, by button, counted again under the account's sharing. Waits past a minute split into 1–5 min, 5–15 min, 15 min–1 h and over 1 h for the computer and the first message. Once per step per sign-in: `resumed` (reopened in a run that did not sign in), "Not you? Sign out", the address sent from the share sheet, a joining computer that wants its password or is offline, `joined_after_leaving` (the computer turned up after the app left the wait), `new_account` (a sign-in that created the account). Once per install: `first_open` (signed out `setup_phone_first_open`, signed in `ui_phone_first_open`) | Stage totals per day, not a linked funnel. A wait's `ok` is a computer that turned up while its screen was open: add `joined_after_leaving` for the computers that came while the app was away (16–19 October 2026: 5 `ok` in 49 fresh waits, while 91% of the phone's people had a computer on the same account). `new_account` is an account minutes old at sign-in, its first Harness sign-in anywhere. `first_open` is set once per install by a local flag that is never sent: the step between a store's download and a sign-in. Subtract `resumed` from starts for fresh starts; an unmatched start is a closed app or a step still waiting. A resumed step's duration starts at the reopening. Signed-in sign-in counts are successes only; failures and cancels before an account remain the signed-out counts', but a success is marked `retried` (a failed or cancelled try came first in that app run) or `switched` (another button was tried first). Phone reports carry release and iOS/Android, so every phone count also splits by those two margins (above 20 collector days); debug builds are not kept. A chosen sign-out sends what is queued first (up to 2 s), so "Not you? Sign out" reaches the totals. || How fast does the phone get back to work? | A launch that came back signed in, to its first computer answering (`app_start`); a dial the person asked for ("Try again", `connect_user`) apart from the app's own (`connect_auto`), beside the unchanged `remote_connect`; a stopped harness resumed from the phone, to its first live turn (`resume_recovery`) | A launch that signs in is the onboarding's and is not counted; one that leaves the screen before a computer answers is `unknown`, one whose computers never answer stays started. An asked-for dial fails at 12 s, as Desktop Connect does. A phone dial is `failed` only when the phone knows why (locked or offline), `unknown` otherwise; the reasons (`connect_error_*`) are Desktop health counters. || Are the phone's side pages used? | Find and Computers opens, by a sideways swipe on the terminal or by a button (Computers' row in Settings, its link on a long wait at home) | Which page and which way, nothing more. Find's key and screen-reader actions are not counted; a swipe that lets Find go back opened nothing. || Does Desktop's Add Phone card get used, and where else is Add Phone opened? | The card's flow (`ui_desktop_phone_offer_*`): started once it is on screen, `ok` by its Add Phone, `cancelled` by its ×, `unknown` when it went another way (Add Phone opened from elsewhere, a sign-out); every Add Phone opening by its way in (`ui_desktop_add_phone_<offer\|titlebar\|menu\|account\|machines\|command>`) | The card is offered once per computer, so its starts are computers, not people, and it has no 15-minute bound: started minus outcomes is an app closed with the card still up. An opening is the dialog shown, not a phone paired. `menu` includes a key bound to Harness ▸ Add Phone… on macOS; `command` is `> add phone` or a key bound to it elsewhere. The browser counts none. Vocabulary 3: counted from the start, but sent only once the local CLI has answered that it forwards them, so a Desktop on an older CLI sends none. |@@ -55,7 +55,13 @@ click trails, stable analytics identifiers, locations, content or arbitrary propThe exact counter vocabulary is in [productUsage.ts](../backend/src/types/productUsage.ts); the Hub's is in[hubMetricsContract.ts](../backend/src/lib/hubMetricsContract.ts).-Daemon reports combine participating signed-in installations, including staff and both environments.+From the first backend release after v1.2.93, the totals everyone reads leave out the team and the testers: a signed-in report from an+`@autonomous.ai` account is kept under `staff:<metric>`, and one from a tester's build (the phone from TestFlight,+`context.channel: 'testing'`) under `testing:<metric>`, margins included. `usage:daily` reads neither. On 16–19 October+2026 the team was 8–30% of the phone's people each day. Compare across this change separately: totals drop by what+the team and the testers sent. Signed-out setup counts have no account and still include them.++Daemon reports combine participating signed-in installations, both environments.App reports are surface-specific operation totals; never add them to daemon or relay counts.They are not all-user counts and are not directly comparable with earlier account-cohort reportsor industry retention benchmarks. Apart from the 10-day people marks below (a keyed pseudonym, deleted on opt-out), no per-person analytics@@ -291,7 +297,8 @@ Deploy backend schema and the singleton worker first, including unique indexes aUse synthetic data to verify duplicate receipts, transaction rollback/retry, off/on revision fencingand expiry. Then release CLI, desktop and phone together. An older backend refuses a whole reportcarrying a counter it does not know (a phone page opening, a `request_phone_*` count, a phone-`sharing: "default"` setup report, a launch code, a first launch's engine, Desktop's Add Phone card or opening), so the backend always goes first. Check that the switch saves and that reports+`sharing: "default"` setup report, a launch code, a first launch's engine, Desktop's Add Phone card or opening, a+phone's `testing` channel, which it refuses whole), so the backend always goes first. Check that the switch saves and that reportsstop when it is off. Old clients stop contributing individual daily histories when the backend changes;the historical reporting command will no longer be a current-usage source.