fix(): Add package write permissions

[kevintylerstark]

No description provided.

[github-actions]

Coverage Report

File	Stmts	Miss	Cover	Missing
src
exceptions.py	4	0	100%
main.py	87	16	16	82%
src/clients/github
graphql.py	40	2	2	95%
queries.py	2	0	100%
src/clients/slack
client.py	23	3	3	87%
tests
__init__.py	0	0	100%
conftest.py	0	0	100%
test_main.py	57	0	100%
tests/clients/github
test_github_graphql.py	41	0	100%
tests/clients/slack
test_slack.py	37	0	100%
TOTAL	291	21	93%

Tests	Skipped	Failures	Errors	Time
24	0 💤	0 ❌	0 🔥	0.351s ⏱️

[diff-vader-bot]

🟢 Risk: LOW — no substantive findings

✅ Diff Vader · Approved

Council reviewed 1 file · 11 reviewers · 0 findings · $0.25

• ✅ blast‑radius
• ✅ correctness
• ✅ github‑actions
• ❓ iac — skipped: filter: not applicable to changed files
• ❓ migration‑safety — skipped: filter: not applicable to changed files
• ✅ performance
• ✅ revertibility
• ✅ security‑tenant‑isolation
• ❓ supply‑chain — skipped: filter: not applicable to changed files
• ✅ supportability
• ✅ test‑adequacy

Why: All approval gates passed.

_{💡 /diff-vader-review <name> adds a one-shot reviewer. Beyond this PR's council, you can request: backup-correctness, loop-design-system.}

[diff-vader-bot]

pr-reviewer-github-actions — MEDIUM severity · confidence 85% (advisory)

New packages: write permission added to the top-level permissions: block. This grants the workflow the ability to publish packages to GHCR (or other GitHub Packages registries). Verify this is intentional and scoped to only the jobs that require it — if only the docker-action job needs to push images, consider moving this permission to the job-level permissions: block to limit blast radius.

React with 👍 / 👎 / 😕 to help us calibrate — why.