Skip to content

Expose installed companion builds and document device delivery - #815

Merged
10 commits merged into
mainfrom
work/cp-808-d1
Oct 11, 2026
Merged

10 commits merged into
mainfrom
work/cp-808-d1

Conversation

@shiny-code-app

Copy link
Copy Markdown
Contributor

The Horizon release shipped the Mac channel while companion uploads were skipped, leaving no recorded Horizon delivery to the devices in #808. A Mac release or unsigned companion build does not install an iPad update, and the companions lacked a visible installed version/build to separate an old executable from stale readings.

Add About version/build details from each executable's own Info.plist: the iPhone/Vision Pro toolbar, regular-width iPad page header, Watch list and visible TV footer. Missing metadata stays unknown. Document the three existing companion Ship channels, sequential dispatch, tester audience, upload/processing/distribution readback and per-device installation checks. Remove stale manual-merge statements and point to the overall direction and shared train procedure; live Launchplane policy confirms enrollment.

Refs #808. The diagnosis and Chris-only checklist remain on the issue. #807 owns stale-data repair; #731 owns matching physical companion acceptance. This PR does not complete device delivery or close #808.

Validation: full commit gate passed with 1,263 Swift tests and its Python lane. All four unsigned companion builds passed; iOS, visionOS and tvOS passed again after the UI review fixes, with repo-owned bundle quarantine completed. Behavioral tests exercise installed bundle metadata and missing/partial values. No Apple credentials/signing keys were read or copied, no release was dispatched and no device was installed/reset.

Anthropic Claude Opus 5.5 reviewed the source and delivery guidance. Its hidden-iPad-toolbar finding was fixed in the visible header; the docs now require sequential Ship runs and distinguish all internal groups from a named narrower audience. TV uses a visible footer instead of relying on navigation chrome. The final follow-up found no blocking defects. Declined its unenrolled-repository fallback because the live policy explicitly enrolls this repo and overall direction owns any future routing; declined wording and optional test-unwrap nits because they change no product behavior or test pass/fail contract.

JetBrains: five-file PyCharm assessment returned UNKNOWN / scope_semantic_coverage_missing (Swift); helper-owned project closed with no tracked/index/worktree mutation. The UI follow-up was not reinspected because the same route lacks Swift semantic support. No IDE-clean claim. Signed on-device presentation remains unverified: the canonical Production Mac is preserved at 1.0.69 (202610031303), and this source is not installed. The existing release-environment hand action is #781.

Device test notes after signed delivery: open About on iPhone, iPad at regular width, native Vision Pro and TV in each display mode; scroll to About on Watch. Compare version/build with each recorded train package, check the account layout, and assess freshness separately. Confirm the Watch update, then restart before routine complication review while preserving placement. Simulator/compiler evidence does not establish physical acceptance.

Landing is a Supervisor merge-train handoff; no label, merge, upload or distribution is requested by this PR.

@shiny-code-app

Copy link
Copy Markdown
Contributor Author

Review evidence addendum: the sequential companion dispatch guidance was checked against GitHub's current concurrency documentation. queue: single is the default and a later pending run replaces an existing pending run. This repository's Ship workflow has no queue: max, so waiting for each platform's run avoids dropping the middle platform. No workflow behavior or release guard was changed.

Local tests, native companion builds and final Anthropic review are complete. Current-head CI remains pending; this is not a green or device-ready claim.

@shiny-code-app

Copy link
Copy Markdown
Contributor Author

Source checks passed; CI cleanup pending at the 11:28 PM ET handoff.

Current head is 633b201. Swift tests, aggregate swift, macos-release, Analyze Swift and CodeQL passed; Clean Trusted CodeQL Temp remains queued. Matching-head reads are complete, zero failed checks/runs, one unfinished workflow. No retry was warranted. Final model review is complete and findings are accounted for; no unanswered review feedback is recorded.

Supervisor next action: continue the babysit-pr watch for this exact head. Once cleanup is terminal green and fresh review/check evidence is complete, post Ready for the merge train and route through the active Launchplane policy. That marker is not posted now, and this worker applied no enqueue/owner-review label and performed no merge.

The source PR does not complete #808's signed device delivery. Preserve the existing #781 manual release-environment step, the posted device checklist, #807 stale-data work and #731 exact-build physical acceptance. Local tests/review/inspection have ended and the local CI watch is stopped. The clean pushed worktree and private acceptance evidence remain for Supervisor adoption/PR landing.

@shiny-code-app

Copy link
Copy Markdown
Contributor Author

CP-FT-D1 current-head follow-through: CI is 6/6 passed at 633b201, with zero failed/pending checks and zero unfinished workflows. Review threads are available and empty; full-history external-comment radar is clear. Existing outside-review accounting remains on this PR.

Stated blocker: GitHub now reports CONFLICTING / DIRTY against main. This is not an unconditional Ready for the merge train handoff. The brief permits only CI/review fixes and assigns train routing to the Supervisor; no CI or review finding authorizes resolving these integration conflicts in this session. Supervisor next action: arrange a bounded conflict-refresh handoff preserving #807's newly merged freshness behavior, then rerun current-head CI/review before routing. #808's delivery and physical acceptance remain open.

No source changes, branch update, label, merge, install or release performed.

@shiny-code-app

Copy link
Copy Markdown
Contributor Author

CP-808-D2 conflict refresh pushed at head 580e555 (current main 9399a04 plus retained #815). The two conflicting hunks retain the iPad header's About action and #807's merged visible freshness card, removing the obsolete header sync-result argument. No new product scope.

Validation: full commit gate passed, including 1,270 Swift tests and the fast Python lane; unsigned iOS, visionOS, watchOS and tvOS builds passed. Repo-owned bundle quarantine completed and companion-cache preflight=OK. Anthropic claude-opus-5-5 reviewed the refreshed tree: no Swift/About/freshness/platform/delivery defect. Its medium landing-guidance finding was declined with fresh authoritative evidence: the GET-only Launchplane policy read reports this repository enrolled for main (policy record merge-train-policy-20261010T144516Z-caf8e5e6004a); overall DIRECTION requires train landing. Main's inherited “does not use” prose is stale, not de-enrollment. The existing PR correction points to those owning sources instead of copying policy values.

JetBrains five-file run 329 remains UNKNOWN / scope_semantic_coverage_missing for Swift in the configured PyCharm route, with lifecycle unchanged and no Git/index mutations. Per the brief, recorded and continued; no IDE-green claim. Canonical signed Production app/agent/registrations preserved; read-only baseline fails the expected source fingerprint mismatch. No install/reset or device-ready claim; no release or device action.

Current-head CI/CodeQL watch restarted with a 90-minute wall-clock deadline. Ready for the merge train is not posted yet. No enqueue/owner-review label or merge mutation; Supervisor routing remains the next action once CI/review settles. #808 remains active for signed delivery and physical acceptance after landing. #781's old reviewer-removal wait is resolved by Q162 and its full checker, not repeated.

@shiny-code-app

Copy link
Copy Markdown
Contributor Author

Ready for the merge train

Head: 580e555.

CP-808-D2 resolved both main conflicts while preserving #807's visible freshness card and #815's iPad About action. All six current-head checks passed, including CodeQL, Analyze Swift and Clean Trusted CodeQL Temp; zero failed/pending checks and zero unfinished workflows. CI: https://github.com/cbusillo/context-panel/actions/runs/38115084861. CodeQL: https://github.com/cbusillo/context-panel/actions/runs/38115084853.

GitHub reports MERGEABLE / BLOCKED under protected-branch rules; this is an engineering handoff for the Supervisor's authoritative train evaluation, not a direct-merge all-clear. Current-head review threads are available and empty; no Client-review request or owner-review label observed. Both full-history external-comment checks are clear. Anthropic claude-opus-5-5 review and the declined guidance finding's fresh Launchplane-policy evidence are accounted for in #815 (comment). Background Review: not yet observable for this head as of October 11, 2026, 2:14 AM ET; a post-turn review may still start.

Local commit gate passed with 1,270 Swift tests and the Python lane; all four unsigned companion builds passed with bundle quarantine and cache preflight=OK. JetBrains run 329 remains UNKNOWN / scope_semantic_coverage_missing (Swift), with helper-owned project closed and no Git/index mutation; recorded and continued under this brief. No installed-current or physical UI acceptance is claimed; canonical signed Production is preserved.

Supervisor next action: route this exact head through the train. CP-808-D2 applied no enqueue/owner-review label and performed no merge, release, install or device action. #808 remains open/plan:active for the existing signed delivery and device acceptance finish line; #781's old environment metadata wait is resolved. The local watcher stops at this authorized handoff, and clean work/cp-808-d2 plus the original work/cp-808-d1 remain retained until PR landing/closure.

@shiny-code-app

Copy link
Copy Markdown
Contributor Author

Ready for the merge train

Head: 580e555

@shiny-code-app shiny-code-app Bot added the ready-to-merge Every Code PR is ready for repository owner merge review label Oct 11, 2026
shiny-code-app Bot added a commit that referenced this pull request Oct 11, 2026
@shiny-code-app shiny-code-app Bot closed this pull request by merging all changes into main in 38714c2 Oct 11, 2026
@shiny-code-app
shiny-code-app Bot deleted the work/cp-808-d1 branch October 11, 2026 19:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-to-merge Every Code PR is ready for repository owner merge review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Get current companion builds onto Chris's devices

0 participants