postEditCommunity.spec.ts makes a second, unrecorded bridge.get_community variant that intermittently fails fixture teardown

Problem

#1397 (closed)'s full fixture_e2e run (commit 34891988) failed in global teardown on a new fixture MISS: bridge.get_community in postEditCommunity.spec.ts. Its parent (6ed32f43) already includes #1396 (closed), whose known-misses.json has the intermittent entry for hash 50f0a6832c3ff911 (get_community {name: hive-137823, observer: guest4test}). Teardown matches spec, method and hash exactly (apps/blog/playwright/tests/support/fixture-misses/known-misses.ts), so this miss must have had a different hash, i.e. a second get_community variant from the post editor with other parameters. One example would be observer empty or another account while the user is still loading, or another community name. It is intermittent, so full fixture gates on the session can still fail at random.

Expected

  • Reproduce and record the variant(s), e.g. aidev test run --slot full --suite fixture_e2e -- postEditCommunity.spec.ts --repeat-each=10, and read the miss log for the hash and params.
  • Prefer recording the response, so it isn't a miss at all, if the call is legitimate and deterministic enough. Otherwise add a known-miss entry with intermittent giving the cause. If the variant comes from a real bug (e.g. a query firing with an empty observer before the user loads), fix the query's enabled condition instead of masking it.
  • Make the teardown's failure message print the missing call's hash and params, so the next agent sees which variant it was without rerunning.

Acceptance

  • The repeated run above passes the teardown in every repetition.
  • A unit test of the teardown message shows the params are printed.