Part of #5095.
Context
The "[BETA] Chat with Gittensory" collapsible (#5078) is the first experimental feature surfaced directly in the public PR comment. Right now it's visually identical to every stable, long-shipped collapsible above it ("Review context", "Signal definitions", etc.) -- the only difference is three characters of literal text in its <details><summary> title. As more experimental features ship into this comment (which this whole epic will likely produce more of), a reader has no way to tell "this is new/unstable, expect it to change" from "this has been solid for months" at a glance.
A small, already-shipped, concrete bug to fix as part of this: the BETA collapsible's copy mixes a real em-dash (—, used in its intro line) with a literal double-hyphen (--, used in its intent-routing bullet) -- pick one and use it consistently (chatBetaBody in src/signals/engine.ts).
Requirements
- Design a visual convention for "this is beta" that's stronger than a text prefix -- options to consider: a distinct emoji/icon consistently used only for beta features, a dedicated "Beta features" super-section that groups ALL beta collapsibles together (rather than interleaving them with stable ones), a different heading weight/style, or a one-line disclaimer auto-appended to any beta collapsible's body.
- Whatever convention is chosen must be a single, reusable helper (not copy-pasted per feature) so the NEXT beta feature gets the same treatment for free.
- Fix the em-dash/double-hyphen inconsistency in the current BETA collapsible's copy.
- Must degrade cleanly: a repo with no beta features enabled sees nothing extra (no empty "Beta features" header with nothing under it).
Deliverables
- A shared "beta collapsible" builder/wrapper in
src/signals/engine.ts (or wherever makes sense) that any current/future beta feature routes through.
- The existing "[BETA] Chat with Gittensory" collapsible migrated to use it.
- The em-dash fix.
- Tests covering the new wrapper and the migrated collapsible.
Expected outcome
Opening a PR's review comment, a maintainer can tell at a glance which collapsibles are experimental vs. established, without reading each title carefully.
Open questions for the maintainer
- Exact visual treatment (icon choice, grouping vs. inline distinction, disclaimer wording) -- this is a subjective call, propose 2-3 concrete options with real rendered examples rather than picking one unilaterally.
Part of #5095.
Context
The "[BETA] Chat with Gittensory" collapsible (#5078) is the first experimental feature surfaced directly in the public PR comment. Right now it's visually identical to every stable, long-shipped collapsible above it ("Review context", "Signal definitions", etc.) -- the only difference is three characters of literal text in its
<details><summary>title. As more experimental features ship into this comment (which this whole epic will likely produce more of), a reader has no way to tell "this is new/unstable, expect it to change" from "this has been solid for months" at a glance.A small, already-shipped, concrete bug to fix as part of this: the BETA collapsible's copy mixes a real em-dash (
—, used in its intro line) with a literal double-hyphen (--, used in its intent-routing bullet) -- pick one and use it consistently (chatBetaBodyinsrc/signals/engine.ts).Requirements
Deliverables
src/signals/engine.ts(or wherever makes sense) that any current/future beta feature routes through.Expected outcome
Opening a PR's review comment, a maintainer can tell at a glance which collapsibles are experimental vs. established, without reading each title carefully.
Open questions for the maintainer