Decide the app icon direction, or close the question

[lightcloud00]

Decision needed

AppIcon-1024.png ships today and is untouched — this issue is the decision, not a change.

Two things hold the current mark back at the sizes people actually see it:

• a soft radial glow behind the pin, which reads as generated output rather than as a designed mark;
• the car's grille — two horizontal slots above a circular dial — resolves as a face at 29pt.

Three alternatives are drawn and tested side by side at 60pt (home screen) and 29pt (Settings, Spotlight) on the canvas: https://claude.ai/code/artifact/fb729515-1f77-4920-b2ad-0ea03705bdb9 — page "Icon & Store".

• A · Flat pin — same silhouette, glow removed, hard hue split; the car keeps a real windscreen so there is no face.
• B · Pin & meter — drops the car for the timer. One shape, one counter-form; the most legible of the three at 29pt.
• C · Inverted — navy pin on amber. Loudest in a home-screen grid, furthest from what ships.

Why it is worth deciding now rather than at submission

The icon is the one asset that cannot be changed without a new build, and #8 (metadata and screenshots) will want it settled. Keeping the current mark is a legitimate outcome — the point is to stop carrying it as an open question.

Acceptance

• One of: keep current / A / B / C.
• If changed: 1024×1024 exported, AppIcon-1024.png replaced, and check-asset-catalog confirms the catalog still reaches the built app.
• If kept: close this issue and note the decision, so it is not re-litigated.

The canvas holds vectors, not an export. Nothing is produced until a direction is chosen.

Resolution plan

• Verified: 2026-08-25T05:34:24Z against main@04a6cd5e808720983471ee9595fd40bc94e1f0fe (commit time 2026-08-25T00:53:29Z).
• Source basis: Original issue body, all 0 comment(s), current default-branch tree, disposition-appropriate source-path checks, and referenced pull-request states.
• Disposition: Product decision - obtain the named decision before implementation.
• Outcome: Decide the app icon direction, or close the question

Current evidence and corrected premise

The issue remains open and requires the resolution steps below.
All 0 issue comment(s) were read. There are no comments.

Resolution steps

1. Option A (recommended): implement the issue's stated outcome as the smallest coherent change that preserves current public and persisted contracts.
2. Option B: retain current behavior, document why the expected benefit does not justify the migration or operational cost, and close as not planned.
3. Option C: split independently shippable outcomes into child issues and keep this issue only as the umbrella acceptance ledger.
4. Present the options with current-source evidence and stop for the user decision before any implementation.

Tests and acceptance

Acceptance

• One of: keep current / A / B / C.
• If changed: 1024×1024 exported, AppIcon-1024.png replaced, and check-asset-catalog confirms the catalog still reaches the built app.
• If kept: close this issue and note the decision, so it is not re-litigated.

The canvas holds vectors, not an export. Nothing is produced until a direction is chosen.

Dependencies and stop gates

• Preserve unrelated behavior, data, public copy, and active owner work.
• Stop before credentials, operator attestations, deployment, release, billing, App Store, or other protected external actions.
• Do not close this issue until every acceptance item is mapped to exact merged-head evidence.

Next AI first action

Option A (recommended):** implement the issue's stated outcome as the smallest coherent change that preserves current public and persisted contracts.

[lightcloud00]

Verified issue disposition — diagnostic

This is the current managed disposition for lightcloud00/parknudge#31 at default-branch 5c3d185143a2.

Current evidence

• Current stable snapshot for Decide the app icon direction, or close the question #31 at 5c3d185143a2 keeps the issue open with body hash 50d6ebec4e32; the validated grounded planner classified it as diagnostic_ready.

Files or owner actions

• For Decide the app icon direction, or close the question #31, bind symbol AppIcon-1024.png to an existing source path before implementation.
• For Decide the app icon direction, or close the question #31, bind symbol check-asset-catalog to an existing source path before implementation.

Bounded plan

• For Decide the app icon direction, or close the question #31: Resolve the recorded targeted-source diagnostic or bind a canonical checkout before any implementation attempt.
• For Decide the app icon direction, or close the question #31: Record the canonical checkout, default-branch SHA, worktree dirt, and issue body hash before probing.
• For Decide the app icon direction, or close the question #31: Trace the issue-named behavior through these bounded source concepts or surfaces: AppIcon-1024.png, check-asset-catalog.
• For Decide the app icon direction, or close the question #31: Write a source-bound diagnostic receipt with reproduced/refuted state, root cause, implicated paths, and the smallest safe change boundary.
• For Decide the app icon direction, or close the question #31: Only after that receipt exists, implement the bounded fix and run the focused check followed by the repository-wide gate.

Commands

• Run git grep -n -F AppIcon-1024.png main for Decide the app icon direction, or close the question #31 and retain sanitized output.
• Run git grep -n -F check-asset-catalog main for Decide the app icon direction, or close the question #31 and retain sanitized output.
• Run git grep -n -F Decide main for Decide the app icon direction, or close the question #31 and retain sanitized output.
• Run git grep -n -F icon main for Decide the app icon direction, or close the question #31 and retain sanitized output.
• Run git grep -n -F direction main for Decide the app icon direction, or close the question #31 and retain sanitized output.
• Run python3 -m pytest -q for Decide the app icon direction, or close the question #31 and retain sanitized output.

Acceptance tests

• For Decide the app icon direction, or close the question #31: [ ] One of: keep current / A / B / C.
• For Decide the app icon direction, or close the question #31: [ ] If changed: 1024×1024 exported, AppIcon-1024.png replaced, and check-asset-catalog confirms the catalog still reaches the built app.
• For Decide the app icon direction, or close the question #31: [ ] If kept: close this issue and note the decision, so it is not re-litigated.
• For Decide the app icon direction, or close the question #31: [ ] One of: keep current / A / B / C.
• For Decide the app icon direction, or close the question #31: [ ] If changed: 1024×1024 exported, AppIcon-1024.png replaced, and check-asset-catalog confirms the catalog still reaches the built app.
• For Decide the app icon direction, or close the question #31: [ ] If kept: close this issue and note the decision, so it is not re-litigated.

Risks

• For Decide the app icon direction, or close the question #31, a false source binding could widen the change or invalidate this plan; Revert only the exact task-branch change after capturing source and runtime identity; never reset or restore an owner worktree.

Stop gates

• For Decide the app icon direction, or close the question #31: no issue close, reopen, body edit, pull-request, branch, or merge mutation while implementing this plan
• For Decide the app icon direction, or close the question #31: the managed plan comment and disposition-specific readiness labels are the only authorized issue mutations in the planning lane
• For Decide the app icon direction, or close the question #31: no push, protected-branch update, force-push, or merge
• For Decide the app icon direction, or close the question #31: no deploy, upload, App Store Connect, TestFlight, or public release
• For Decide the app icon direction, or close the question #31: no credential value disclosure, rotation, billing, or provider change
• For Decide the app icon direction, or close the question #31: no owner-worktree restore, reset, checkout, process signal, or queue reorder

---

Ledger schema: aos.github-issue-plan-coverage.v1 · issue body: 50d6ebec4e32