- Don't dequeue global-styles or friends theme styles in dequeue_scripts
- Fix extra } in post-title block attribute in index.html
- Add pagination inside query block in index.html
- Replace placeholder text in footer.html with a valid block
- Remove site-specific widget instance hashes from sidebar.html
- Fix composer.json dependency conflict (phpcompatibility version)

- Add friends/subscriptions-query block: iterates subscriptions passing
  each as block context, mirroring the wp:query + wp:post-template pattern
- Add friends/subscription block: renders a subscription card from context,
  works for both WP users and virtual subscriptions (taxonomy terms)
- Add friends/followers block: server-side rendered ActivityPub followers list
- Add friends-followers.html and friends-subscriptions.html block templates
- Route subpage requests to block templates via $_wp_current_template_content
  when a block theme is active, falling back to PHP templates otherwise

- Register 'block' as a selectable Friends frontend theme via
  friends_load_themes, rather than always overriding the stylesheet
- Move stylesheet filter into block_theme() so it only activates
  when the block theme is chosen
- Add single-friend_post_cache.html block template for single post view

Only use block theme template paths when the Friends block theme is
explicitly selected, not just because the site's WP theme is a block
theme. Also restore global-styles dequeue for the default theme and
fix get_user_option call that passed 'expanded' as user ID.

- Only use block theme code paths when explicitly selected
- Restore global-styles dequeue for default theme
- Fix get_user_option call using wrong parameter
- Register friends theme directory for site editor discovery
- Add pre_get_block_file_template filter for friends// templates
- Replace legacy widgets with proper blocks (stats, refresh,
  post-formats, add-subscription) with editor support
- Enqueue site theme stylesheet alongside friends block theme

- Use wp-block-heading class on starred friends heading for
  consistent styling with template headings
- Check database for user-customized template parts before falling
  back to plugin files, so site editor changes are respected

Use core blocks (post-author-name, post-title, post-content) in the
query loop so the site editor can render previews. Only the permalink
section (time ago, domain, reading time) remains a custom block.

… editor

Friend posts contain raw HTML from feeds, not WordPress blocks.
The core post-content block runs it through the block parser which
wraps it in freeform blocks and iframes. This custom block renders
the content directly with wp_kses_post and wpautop.

Tests cover:
- Block registration for all custom blocks
- Template and template part files exist on disk
- Template content mapping (get_block_template_content_for)
- Render output of each block (search, feed-header, stats, refresh,
  post-formats, add-subscription, post-permalink, post-content,
  author-header, starred-friends-list)
- Placeholder rendering when no post/author context
- Template structure (correct blocks referenced, no footer)
- calculate_read_time accessibility and correctness

…lict

The reflection in the test was triggering a doctrine/instantiator
autoload conflict in CI. Make the method public for testability
and restore the starred friends list test.

…conflict"

This reverts commit 80da70f.

The test assumed no starred subscriptions exist but the test
environment may return results. Check the actual query result
and assert the correct output structure for either case.
This also fixes the PHP 8.2 CI crash where the assertion failure
triggered doctrine/instantiator autoload via PHPUnit error output.

- friends/feed-header → friends/feed-title (h2 heading) +
  friends/feed-chips (post counts, hidden items, reactions)
- friends/author-name now renders as h2 with id="page-title"
- friends/author-description shows placeholder in site editor
- Both feed-chips and author-chips use identical chip markup
  (<a class="chip">) so one CSS rule styles all chips consistently
- Header and author-header template parts compose the individual
  blocks so each is selectable and styleable in the site editor

All sidebar widgets, chip blocks, heading blocks, and permalink block
now have WordPress block supports (color, typography, spacing). The
site editor shows sidebar controls to change background, text color,
link color, font size, line height, padding and margin — no custom
CSS needed.

Each render callback uses get_block_wrapper_attributes() to apply
the user's style choices to the wrapper element.

Remove the "Friends Visibility" editor panel, block-visibility JS,
and related dead code since the friendship feature was removed.

Keep a simplified render_block filter that hides content marked
with the "only-friends" CSS class to prevent accidental exposure
of previously hidden content. Content marked "not-friends" is
shown to everyone.

- Add "starred" as a user_types option to friends/friends-list
- Remove separate friends/starred-friends-list block
- Add block supports (color, typography, spacing) to block.json
- Update editor JS with current options (subscriptions, starred)
- Rebuild with latest @wordpress/scripts
- Use get_block_wrapper_attributes() for styling support
- Update sidebar template to use friends-list with user_types attr

New friends/post-footer block renders the interaction buttons for
each post in the block theme query loop:

- Reblog button with status indicator
- Boost button (when ActivityPub is active) with status indicator
- Emoji reaction buttons with counts and reaction picker
- Comments button with AJAX loading and mention indicator
- Comments content container for AJAX-loaded comments

The existing JS in friends.js handles all interactions via event
delegation on CSS class selectors, so no JS changes needed.

Split friends/post-footer into four individual blocks:
- friends/post-reblog, friends/post-boost, friends/post-reactions,
  friends/post-comments

Wrapped in a flex group so they appear on one horizontal line.
Users can add/remove individual blocks in the site editor.

- Use href="#" instead of get_comments_link() to prevent navigation
- Wrap comments link and content container in a single div so JS
  can find .comments-content relative to the clicked link
- Update JS loadComments to find .comments-content in block theme
  context (closest .wp-block-friends-post-comments or li)
- Add block theme selector to comments click handler
- Fix JS error when .card ancestor not found in block theme

- Default $attributes parameter to empty array so tests can call
  render methods without arguments
- Add get_wrapper_attributes() helper that safely falls back when
  not in a block rendering context (avoids null access crash in
  WP_Block_Supports when called from unit tests)