Allow contact deletion after ActivityPub unfollow #314
No reviewers
Labels
No labels
activitypub
admin
api
architecture
articles
auth
bug
cleanup
cli
comments
compatibility
config
contacts
content
database
deployment
design
dev-env
diagnostics
docs
documentation
email
enhancement
feature
federation
feed
health
homepage
implementation
integration
logging
mastodon
media
navigation
npm-packages
openapi
opengraph
packages
passkeys
preview
priority:high
priority:low
priority:medium
production
proof
proxy
public-routes
public-ui
release
safety
slug-api
slug-auth
slug-core
slug-federation
slug-media
slug-template
social
sources
status:active
status:canceled
status:done
status:inprogress
status:waiting
syndication
tailwind
template
test
web
webauthn
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
erik/slugkit!314
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/task-b116d607-contact-unfollow"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Verification
794e7c1).794e7c1; review summary recorded in PR comment.Operational boundaries
All migration tests use isolated in-memory databases. No normal application startup or migration execution against existing data; dev server was stopped. No release, deployment, production contact cleanup or historical changelog edits. Existing-site adoption requires backup/restored-copy testing and separately authorized migration/startup. This does not delete or merge the production contacts mentioned in the task.
Task: task-b116d607.
Pipeline state
Ready for explicit human merge approval. Do not auto-merge.
Independent review of exact head
794e7c1completed by a separate read-only pi reviewer following the pr-review skill:Implementing-agent verification: current-head CI / build-lint-test passed at
794e7c15bd(1m3s): https://forge.caradoc.com/erik/slugkit/actions/runs/566/jobs/0 . Full local checks passed and working tree is clean. No workflows, npm versions, pins, lockfile or generated CSS changed. No existing-data migrations, application startup, release/deployment or production cleanup performed.Pipeline state: implementation, local checks, exact-head CI and independent review complete. Awaiting explicit human merge approval; do not auto-merge. Task remains in progress and task branch is retained.
Merged with explicit human approval as
d007a5f2f6. Post-merge main CI passed (1m7s): https://forge.caradoc.com/erik/slugkit/actions/runs/567/jobs/0 . Local main synchronized and task branch cleaned up locally/remotely. No release, existing-data migration execution, deployment or production contact cleanup performed.