Stabilize Context Panel runtime validation

[cbusillo]

Objective

Make runtime validation trustworthy before any provider or UI fixes continue. The foreground app, WidgetKit extension, and refresh agent must be proven to come from the intended bundle root before behavior is judged.

Finish Line

A repeatable validation pass records app process path, widget registration path, refresh-agent executable path, bundle hashes, entitlements, provisioning profile names, and active storage roots, and reports mixed runtime as blocked instead of fixed.

Current Status

State: Active
Next action: Launch only the intended signed /Applications/Context Panel.app when ready to judge app UI; do not judge Settings while no foreground app is active.
Blocked by: Dirty tree triage (#66) before building or installing another candidate.
Last verified: 2026-05-12

Evidence captured:

• Branch: fix/widget-refresh-regression at a2173352a7161effdb69012175f5d5eddd2413c6, with broad dirty state.
• Foreground app process: none currently active.
• Widget extension process: /Applications/Context Panel.app/Contents/PlugIns/ContextPanelWidgetExtension.appex/....
• Widget registration: /Applications/Context Panel.app/Contents/PlugIns/ContextPanelWidgetExtension.appex.
• Refresh agent process: /Applications/Context Panel.app/Contents/Library/LoginItems/ContextPanelRefreshAgent.app/....
• Installed app hash: 0178a68f95a10427b7019bd47d6fe5d6c62cad12168ffe399b1dc0e2cb93f5e6.
• Installed app entitlements: sandbox true, app groups include group.com.shinycomputers.contextpanel and MM5YXC7T6E.group.com.shinycomputers.contextpanel, user-selected read-only true, app-scope bookmarks true.
• Embedded profiles: app Context Panel Mac App Store Profile New, widget Context Panel Widget Mac App Store Profile New, refresh agent Context Panel Refresh Agent Mac App Store Profile.
• Active storage roots exist in Application Support, app group, and widget container mirror.
• Current snapshots match across the three roots and still show duplicate logical OpenAI/Anthropic identities plus Gemini failure: The file couldn’t be opened.

Current interpretation:

• The runtime is not actively mixed right now because no foreground app is running, and widget/agent both point to /Applications.
• App UI behavior is not currently validated because no foreground app process is active.
• Provider/storage behavior remains blocked by dirty-tree triage and snapshot/account dedupe.

Scope

• In: Process/path/hash/entitlement/profile/storage inventory and stop conditions for mixed runtimes.
• Out: Provider code, UI restoration, or snapshot migrations.

Acceptance Criteria

• DerivedData app plus /Applications widget/login item is detected as mixed runtime.
• Signed dogfood validation uses one intended /Applications bundle root.
• Debug/Xcode validation uses a single coherent debug runtime or is explicitly marked as debug-only.
• Validation output includes all storage roots and the current snapshot savedAt.

Relationships

Sub-issue of #64. Blocks provider/UI readiness work.

Validation

Use the AGENTS.md minimum runtime evidence commands and record output summary in the issue.

Decisions

Mixed runtime is a blocker, not background noise.

Open Questions

Should we add a script for the runtime evidence commands after the manual pass is stable?

[cbusillo]

State: Active
Next action: Review/merge PR #72 for runtime validation guardrails, then continue with dirty-tree cleanup (#66).
Blocked by: PR #72 CI/review for the guardrail change; broader provider/UI fixes remain blocked by dirty-tree triage.
Last verified: 2026-05-12

Update:

• Created PR Document runtime validation guardrails #72 from clean branch docs/runtime-validation-guardrails containing only the AGENTS.md runtime validation guardrails.
• Validation for PR Document runtime validation guardrails #72: npx --yes markdownlint-cli2 AGENTS.md docs/todo.md passed.

[cbusillo]

2026-05-14 runtime-validation update:

• scripts/context-panel-runtime-baseline.sh is now the canonical receipt for ready-to-test claims.
• The script builds, installs to /Applications/Context Panel.app, stamps/verifies a build fingerprint, checks app/widget/refresh-agent presence, verifies PluginKit registration, verifies contextpanel:// handling, checks for conflicting bundles/stale local build bundles, and reports known Context Panel storage roots without broad Library scans.
• It now also verifies the signed team/app-group entitlement path so we do not accidentally validate a build signed by the wrong team.
• Latest installed runtime receipt passed with baseline=OK; app, widget, URL handler, and refresh agent all pointed to /Applications/Context Panel.app.

Remaining before close:

• Decide whether the receipt needs to print embedded provisioning profile names in addition to the current signing/team/entitlement evidence.
• Run one final baseline check after the broader gate pass and record the output summary here.

[cbusillo]

2026-05-14 final local receipt update:

• Added provisioning-profile reporting to scripts/context-panel-runtime-baseline.sh. The current debug-installed runtime has no embedded provisioning profiles, and the receipt now says that explicitly instead of leaving it unknown.
• Latest receipt passed: baseline=OK app=/Applications/Context Panel.app.
• Receipt evidence includes canonical app group, canonical team MM5YXC7T6E, matching build fingerprint, app process from /Applications, PluginKit widget registration from /Applications, contextpanel:// resolving to /Applications, refresh login item running from /Applications, no conflicting bundles, and preserved known Context Panel storage.
• Local gates also passed: swift build, swift test with 146 tests, and scripts/commit-gate.sh.

I think this issue is now closeable once we decide whether #65 should also require TestFlight/export-profile validation, or whether that belongs only to #71.

[cbusillo]

2026-05-14 acceptance update:

• Runtime receipt now prints embedded provisioning-profile state and current snapshot savedAt.
• Latest storage section includes: current snapshot savedAt=2026-05-14T15:43:50Z.
• After the script change, swift build and swift test passed again with 146 tests.

Remaining scope for TestFlight/export profile validation belongs to #71. For local runtime validation, #65's finish line is now satisfied.

[cbusillo]

Closing: the canonical runtime validation path is now codified in AGENTS.md and implemented in scripts/context-panel-runtime-baseline.sh. The receipt verifies the installed /Applications app, widget registration, URL handler, refresh login item, canonical team/app-group signing, build fingerprint, provisioning-profile state, known storage roots, and current snapshot savedAt. TestFlight packaging/export validation remains separately tracked in #71.