Repository navigation
fix(notifications): make Enable Notifications work; group attention policy by role - #47
Conversation
…d; group attention policy by role - release-ci.sh: ad-hoc sign the bundle when no Developer ID is configured. The linker-only signature has no bound Info.plist, so macOS rejected requestAuthorization without a prompt and 'Enable Notifications' did nothing. - Surface a rejected permission request in Settings instead of print(). - Attention Policy grouped into Your PRs / PRs You Review; the comment event is split by role (newCommentOnReviewPR), with a v2 migration copying the stored level.
…ale signing comment
✅ No issues foundThird pass. The delta only updates the CLAUDE.md file map, which now matches the code; the prior Architecture-tree thread is closed and no new issues were found. Checked: 8 of 8 changed files read · 3 possible issues → 0 confirmed → 0 posted Progress: open review threads 1 → 1 → 0 across the last 3 reviews Review details
Found Quality — produced 3 → posted inline 0 · cleared 0 · carried forward 0 · deferred 0 · below-bar 0 Run full · 8 lines in delta · tier deep · depth checkout Nothing to report — severity, 0 files skipped.
|
Addresses review comment by pr-reviewer: #47 (comment) (thread PRRT_kwDOTPehCs6ooiRC)
…ion error Addresses review comment by pr-reviewer (thread PRRT_kwDOTPehCs6oomUZ)
…ission-and-policy-groups # Conflicts: # CLAUDE.md
|
Darkplane auto-approval is enabled for this repository (mode: Auto-approve). Trigger an evaluation for this pull request when it is ready: |
Why
"Enable Notifications…" did nothing: CI release builds (no Developer ID) shipped with only the linker's Mach-O signature — no bound Info.plist, no sealed resources — so macOS rejected
requestAuthorizationwithout ever prompting. Separately, the Attention Policy list mixed events about your PRs and others' PRs with no way to tell them apart.What changed
release-ci.shad-hoc signs the bundle when no Developer ID is configured (Gatekeeper still treats it as unsigned).print()ing.newCommentOnReviewPR); a v2 migration copies the stored level, and migration rules are now gated on the stored version so a bump never re-runs an older rule.How to verify
codesign -dvon a CI-style Release build:Identifier=com.mainline.github-pr-notifier,Info.plist entries=28, sealed resources present (wasnot bound/none).AttentionPolicyCheckspass via a swiftc harness; the new version-gating assertion fails when the gate is removed.Notes for reviewers
"Ready for review" sits under PRs You Review but also fires for your own draft→ready; left as-is, worth a follow-up.