Purge consumed ActivityPub incoming delivery metadata #316
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!316
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/task-95f554ae-consumed-delivery-cleanup"
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
Task: task-95f554ae. Coordinated counterpart: Rott task-5a4a4e82.
Verification
Safety and coordination
The user approved lifting the Slugkit implementation deferral and breaking 3.0.0 plan. Shared remote-vs-copy identity/rollout notes were recorded in both tasks before coding. Do not deploy server retention or run legacy cleanup before verified Rott redelivery recognition, stable post/boost read identities, offline/restart handling and repeat cleanup. Rott storage/retention implementation remains client-owned and is not claimed ready. No existing/production database inspection/migration/deletion, website deployment, release or Rott source changes were performed. Dev environment remained stopped; tests use isolated databases.
Gates
CI run 572 passed at
2197392. Independent review returned PASS with no actionable findings (static review; local test log inspected). Explicit human merge approval required; do not auto-merge.