Skip to content

Add per-identity pinned napplets and Home - #10

Merged
gsovereignty merged 1 commit into
mainfrom
feat/pinned-napplets
Nov 16, 2026
Merged

gsovereignty merged 1 commit into
mainfrom
feat/pinned-napplets

Conversation

@macro88

@macro88 macro88 commented Nov 16, 2026 •

Copy link
Copy Markdown
Member

Merge scope: this PR merged commit a39c31f at 20:18 HKT on 16 November 2026. The later iOS interaction fix, final Simulator journey and phone-tested build use 28b795d, which is tracked separately in #11 and is not included in this merge. The later validation statements below refer to that follow-up build.

The header logo now opens a Home grid of pinned napplets while keeping open sessions mounted. Users can pin from Discover or a napplet's menu, then reopen a shortcut or switch through All napplets. No bottom navigation is added.

Pins persist separately for each identity. Discover starts pinned, and explicitly unpinning it survives restart. Unpinning removes only the shortcut. Snapshot v1 migrates to v2 without changing the SQLite schema; accepted publication updates refresh an existing shortcut in place. Discover pinning uses verified publication metadata and a trusted shortcut review, without opening the napplet or granting access. Android and iOS validate the optional pin action through the existing native extension.

The bundled Discover artifact includes listing/detail Pin controls and preserves its opening progress feedback. Home uses verified content-addressed artwork with monogram fallbacks. Long-press rearranging/unpinning remains a documented follow-up; this version uses Edit and menu actions.

Validation:

  • TypeScript; shell 101, storage 138, capability 201, routing 67 and presentation 80 tests passed, plus security and quality regressions.
  • Packaged Discover: 16 Chromium/WebKit checks passed; portable Discover: 12 unit and 42 browser checks passed.
  • Native routing: 183 assertions per platform. Android Release build and iOS Release Simulator build passed. Isolated Android and iOS Simulator fixtures verified Home, the open-session switcher, menu pinning, shortcut resume preserving live counter state, unpin retaining the open session, and restart respecting Discover removal. Light/dark Home inspected; disposable app removed and original emulator inventory/settings restored.
  • React Doctor 100/100, AISlop 100/100, zero findings; all 10 lockfile audits passed. Includes narrow development-only Hono security updates and refreshed production notice inventories; all contributor identities and original notices are unchanged. Notice guards: 84 Node checks plus iOS adversarial checks passed.

Known CI gate limitation (confirmed in the PR job; both quality scores also reached 100/100 there): Expo Doctor passes 19/20 checks. It requests expo 58.0.25 and expo-sqlite 58.0.17; installation is blocked by the existing minimumReleaseAge policy (expo-sqlite was released three days ago). The resolution policy and compatibility check are unchanged. Physical Android/iOS acceptance and ordinary standalone journeys remain pending; simulator/fixture evidence is not release acceptance.

The iOS UI regression exposed hidden overview gesture handlers intercepting Home taps. The overview controls now unmount while Home is visible, and its native gestures are disabled whenever inactive; live napplet views remain mounted. The full iPhone Simulator journey and updated Android emulator journey pass after this fix. TypeScript and shell regressions pass, with fresh React Doctor/AISlop scores of 100/100 and all ten audits passing.

Copilot AI balanced review requested due to automatic review settings November 16, 2026 11:55

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.

@gsovereignty
gsovereignty merged commit 8953252 into main Nov 16, 2026
15 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants