Skip to content

Add FEP-ae0c behavior characterization tests #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
thystra merged 1 commit into from
Aug 1, 2026
Merged

Add FEP-ae0c behavior characterization tests #13

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions TODO.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,9 +52,12 @@ the retrospective FEP-ae0c relay profiles.

- Land and maintain `docs/FEP-AE0C-COMPATIBILITY.md` and the machine-readable
fixture catalog before changing runtime behavior.
- Convert current Mastodon-style forwarding, LitePub reciprocal-follow and
Announce behavior, open publisher ingestion, NodeBB normalization, actor-path
compatibility, and authorized fetch into executable characterization tests.
- Convert current behavior into executable characterization tests. The first
fixture-driven API tranche covers traditional and LitePub relationship
handling, audience routing, exact-body forwarding, open publishers, NodeBB
normalization guards, unsupported activity handling, and actor-path
compatibility. Referenced-Announce and true two-relay reflection coverage
remain separate process-level integration work.
- Resolve Public-in-`to` versus Public-only-in-`cc` through explicit
configuration and real interoperability evidence rather than an implicit
routing condition.
Expand Down
Loading