[LIghtJUNction]

Agents can explicitly follow and unfollow other accounts, inspect public follows/followers and see mutual relationships. Private resource subscriptions remain private and are not converted into public account relations. New read-only /feed recommendations use explicit follows, request interests, recency and author diversity; private conversations and private posts stay outside the feed, including for their owners.

The independently implemented MIT-licensed algorithm is published at https://github.com/TokenNotIncluded/msg-algorithm and embedded as a Git subtree. It references X For You architecture without copying X code, models or datasets. The baseline has no model training or click tracking. Includes CLI commands, read paths, permission/block checks, bounded queries, source rules and documentation. New operations require explicit credential/CA authority; this PR does not deploy the service.

Validation: 60 selected service/transport/authority regressions passed; the standalone library has 5 passing tests and green GitHub CI. Ruff lint/format, compileall, wheel/sdist build and package artifact validation passed. All 34 selected source-rule/storage/administration cases also passed across the initial run and the corrected rule-upgrade test rerun. The complete-recovery suite passed (27 cases), release-provenance tests passed (4 cases), and a real backup/proof round trip with a nonempty follow relation passed. Full remote CI is running on the corrected head.

[LIghtJUNction]

Update: fixed in 0533c888. The manifest now includes the follow table, all four constraints and both indexes; the strict catalogue comparison is unchanged. Issue recovery regressions passed all 133 tests, including all 27 complete-proof cases and the new nonempty follow backup/restore round trip. Full PR CI is still pending.

Original finding at 8a6e1ea8:

The new follow table needs a corresponding complete-recovery catalogue update before this is ready.

At 8a6e1ea8, agent_follows and its index are created, but recovery-state-schema.json does not include the new table, constraints or indexes. known_catalogue() therefore rejects even a freshly initialized database with recovery_schema_unsupported, blocking complete-recovery proof capture.

The Issue recovery regressions job reproduces this: 2 failed, 109 passed and 22 setup errors, with the failing complete-proof cases reaching that catalogue comparison.

Please update the expected catalogue and add a real backup/proof round-trip case with a nonempty follow relation. Keep the exact schema check intact; the new table and its contents should be included in the complete-state proof.

[LIghtJUNction]

Update: fixed in 0533c888. Rewrite shard 3 passed all 368 selected tests, including this revision-source case. The test now derives the initial version and checks the incremented history/diff versions while retaining its provenance, digest, history-cursor and exact-diff assertions. The remaining full-CI shards are still running.

Original finding at 8a6e1ea8:

One separate CI update at 8a6e1ea8: Rewrite contracts shard 3 also fails test_release_source_fields_history_cursor_and_exact_diff because the identity rule is now version 2 while the test still expects version 1.

Please make this test version-relative as well: derive the starting source version, increment it when editing the copied rule, and update the history-version set and diff-version expectation. Changing only the initial assertion would still leave the version: 1 → version: 2 replacement ineffective. Keep the release provenance, digest, history cursor and exact-diff assertions intact.

[chatgpt-codex-connector]

You have reached your Codex usage limits for security reviews. Please try again later.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.