В specs/ четыре разных языка под расширением .tri (72 не-YAML спеки)

[gHashTag]

The narrow question was why 44 specs slip past t27c's new guard and parse to an
empty module. The answer is wider: four different languages share the .tri
extension under specs/.

Census of all 1137 specs

format	marker	count
YAML VIBEE	name: at line start	1065
t27 blocks	spec X { }	14
Markdown	## headings	32
TOML	[section], key = "value"	13
comment-led / generated	starts with //	10
near-empty	under 3 non-blank lines	3

The sum checks out: 1065 + 14 + 32 + 13 + 10 + 3 = 1137.

Examples

specs/storm_main.tri — Markdown:

# tri storm — STORM Operation

## Module
tri.storm

specs/hslm/model.tri — TOML:

[spec]
name = "hslm_model"
version = "1.0.0"

[interface]

specs/tri/ab_testing_test.vibee — generated output living in the source
directory: its header reads Generated from .tri specification.

Why it matters

1. vibee_gen silently produced boilerplate for all 72 non-YAML specs —
   Types: 0, Behaviors: 0, exit 0. The corpus gate cannot object, because it
   counts 0/0 as a legitimate spec with no behaviours. Отказываться от Markdown- и TOML-спек, а не только от t27 #793 now refuses 62 of
   them by name; the remaining 10 are comment-led and fall through on purpose.
2. "Migrating from .tri to t27" is not one migration but four. Markdown and
   TOML convert to t27 through no existing path.
3. A generated file inside specs/ is a source of truth that is actually
   derived — exactly what CLAUDE.md warns against.

Proposed

• Decide the fate of each dialect. The 32 Markdown and 13 TOML files are
  either documentation that acquired a .tri extension by accident, or
  abandoned formats. Both cases need a decision, not a conversion.
• Move generated files out of specs/.

Found while closing gHashTag/t27#3471 — the 44-spec residue, invisible to that
discriminator by construction, turned out to be these dialects.