Adopt contract 3.0.0 consumed-delivery cleanup #31
No reviewers
Labels
No labels
bug
priority:high
status:active
status:inprogress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
erik/erikvancraddock.com!31
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "task-72ab5dfa-consumed-delivery"
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
Adopts published Slugkit client-owned incoming history: API package 2.0.0, breaking contract 3.0.0, and template 1.0.0 retention behavior while preserving site customizations. Task:
task-72ab5dfa.objectIdversus boostactivityIdrecognition.docs/incoming-activity-retention.md.Verification
npm run typecheck,npm run lint,npm run build: pass.npm test: 754 passed, including signed federation/local HTTP integration tests.npm run test:ci: 586 passed.PLAYWRIGHT_CHROMIUM_EXECUTABLE_PATHpointing to installed Chromium 1234. Default expected Chromium 1243 is absent; no browser install or production app startup performed.git diff --check: pass. Build regenerated unrelated CSS; that generated-only change was discarded.Hard rollout restrictions
Do not deploy/publish a web release or purge legacy tombstones until Rott
task-5a4a4e82verifies remote identity/redelivery recognition and repeat cleanup including offline/restart and uncertain responses. Deployment and production cleanup each require separate explicit authorization. Rott readiness is not verified. Source merge does not authorize either action. No CLI update.No existing private/hosted database was inspected or migrated, no production cleanup or application restart occurred. Docker daemon unavailable; source-watching rehearsal app must remain stopped under existing rollout restrictions. Legacy body-less counts remain unknown; SQL is only exercised on synthetic disposable fixtures. Existing-data startup/migration and production-shaped rehearsal require separate authorization.
Independent review and final delivery gates
Reviewed head:
1fdde15c476e1a7728ec7e50d18ab26f1436a376.An independent read-only reviewer inspected the diff, new operator SQL/adoption guide, surrounding services/routes/tests, packaged API metadata/schema and migrations 028–031. No actionable defects or unmet source-adoption requirements were found; no optional suggestions. The reviewer confirmed scoped atomic removal, cursor/high-water preservation, fresh redelivery copy IDs, old-ID retry isolation, bounded body-less-only operator cleanup and preservation of site customizations.
Review limits: static assessment; reviewer did not rerun commands/tests or open databases. Production schema/rehearsal and client readiness were not independently verified. Original review artifact:
/tmp/task-72ab5dfa-independent-review.login the implementation environment.Verified separately by the implementing agent:
The user explicitly removed Rott readiness verification from task-72ab5dfa's acceptance/completion criteria. That client work is tracked separately in task-5a4a4e82; existing rollout documentation is not a task-completion gate. No deployment, web release, application restart against private data or production cleanup is authorized or performed. Those remain separate explicitly authorized operations. Legacy hosted counts and production-shaped rehearsal remain unknown/pending.
npm audit reported 29 dependency advisories (21 moderate, 8 high), none directly for slug-api; broad dependency remediation is outside this adoption.