Jannis Braun 4064d822cd fix(janitor): restore inbound /peer/denied expiry notification ...

Task 9's first pass replaced inbound expiry's signed /peer/denied
POST with a plain delete, citing symmetric independent expiry as
the design. The spec at §4.10 explicitly said 'inbound row cleanup
unchanged' — that was scope creep, not a fix. Inbound expiry now
preserves the pre-branch behavior verbatim: signed POST to remote,
delete only on success, retry on failure. Outbound expiry's fanout
logic (the actual Task 9 scope) is unchanged.

2026-04-26 22:22:34 +02:00

..

db

feat(federation): outbound gate in ensurePeered with required intent argument

2026-04-26 21:18:43 +02:00

routes

feat(federation): peering-notifications endpoints + janitor expiry fanout

2026-04-26 22:18:44 +02:00

utils

fix(janitor): restore inbound /peer/denied expiry notification

2026-04-26 22:22:34 +02:00

ws

feat(server): reclassify undeliverable targeted-peer as no_recipient failure (#18)

2026-04-24 21:11:11 +02:00

config.ts

feat: security hardening, DB indexes, token revocation, and input validation

2026-03-15 00:06:15 +01:00

index.ts

feat(federation): rollbackFriendRequestCreate + side-effect registration

2026-04-25 21:51:04 +02:00