[LIghtJUNction]

Posts and replies now support author-written summaries in version 2 write contracts. Summaries remain part of immutable revisions, survive body-only edits and roll back with historical content. Compact hexadecimal read links expose authorized metadata, history, diffs and thread previews while preserving legacy signed identifiers and paths. Registration stays within the installed issuer authority.

Public RSS advertises an optional set of WebSub hubs and queues durable publication hints independently per hub. Retries, including expired worker leases, respect backoff and an eight-attempt limit. Legacy identifier conversion is shared with database lookup, SQLite supports the same references, and ambiguous references are rejected. Includes CLI flags, homepage/rule updates and usage documentation.

Validation: 175 selected regressions checked; the single outdated Markdown assertion was updated and re-run successfully. A further 25 worker/reference/recovery boundary checks and a SQLite reference check passed. Ruff lint/format, compileall, wheel/sdist builds and package artifact validation passed. Remote CI remains the full-suite check; no service deployment or package release is included.

[LIghtJUNction]

Two P2 compact-read compatibility findings at 4d17b3b. These are source-traced; I have not run local reproductions.

1. Preserve existing names beginning with "". parse_post_view intercepts any path containing a segment that starts with "", before normal resource lookup. validate_name still permits names such as "*report.md", so an existing /main/*report.md is now interpreted as an ID and fails instead of reading the named post. Descendants of a starred directory also fail the compact-route grammar. Please preserve ordinary lookup for existing starred names and add compatibility coverage, including percent-encoded legacy links.

2. Read a bounded body prefix for large post previews. thread_summary treats a missing content field as an empty body, but read_projection omits that field when the blob is at least max_response_bytes // 2. A valid nonempty uploaded post without an authored summary therefore returns an empty summary on /*ID/thread. Please add a boundary-size post regression and produce the requested prefix plus ellipsis from a bounded read after authorization.

[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.

[LIghtJUNction]

Two additional P2 WebSub lifecycle/configuration gaps at 4d17b3b. These are source-traced; I have not run local reproductions.

1. Retry expiry during delivery as well as expiry before claiming. The new WebSub branch calls _finish/_retry after sending. If the lease expires during that await, current_attempt changes the row to uncertain and clears its lease. Subsequent _claim scans only running/pending rows, so the idempotent publication hint is stranded instead of receiving the promised bounded retry. Please add a fake-sender test that advances the clock past the lease before returning. Preserve the stale-attempt fence while scheduling the current WebSub attempt for bounded retry; the general lease guard should remain intact for other effect kinds.

2. Validate the WebSub dependency on the optional extensions plugin. Hub configuration accepts a nonempty list with extensions disabled, but discovery.feed is registered only by that plugin. The new event hook lookup then raises unknown_operation inside qualifying post/topic write transactions, rolling those writes back. Please reject this incompatible configuration early or gate publication on an installed feed contract, and add a reduced-plugin configuration regression.