Skip to content

Cut the model-read ecosystem specifics from tdd: observable-behavior and testing-styles #17765

Description

@kyle-sexton

Part 3 of 6 of #16758. Refs #15703.

Problem

The observable-behavior and testing-styles pages teach through C#, xUnit.net, Moq and Fluent Assertions listings.

Rows (2: all R11)

Row Rule Kind Cited at (as of 5b66a7f) Fact
F0402 R11 K7 plugins/tdd/skills/principles/reference/observable-behavior-khorikov.md:18-53, 99-209 C# and Moq Mock<T> listings
F0403 R11 K7 .../reference/testing-styles-khorikov.md:20-330 output/state/communication listings (C#, xUnit.net, Moq, Fluent Assertions BeEquivalentTo)

A spot grep at d46efa9 finds only one xUnit/Moq/"Fluent Assertions" hit in testing-styles-khorikov.md, against its fence ceiling of 9 (.performance/ratchets.json:196). Re-read F0403's span first: list any listing already rewritten as GONE.

Files

  • Cut: plugins/tdd/skills/principles/reference/observable-behavior-khorikov.md, .../reference/testing-styles-khorikov.md.
  • Outside references at d46efa9: .performance/ratchets.json:192 (observable-behavior ceiling 6), :196 (testing-styles ceiling 9).

Rules this part follows (from #16758, rules revision 5)

  • R11 (shipped knowledge): model-read K2, K3, K4, K5 or K7 text. Generic text replaces it only at a routing site where the skill still takes a language-specific step; anywhere else it is deleted with no replacement. An item kept only because a removed item consumes it goes in the same pull request.
  • R4 (consumer default): the value picks a tool or library for the consumer. It goes: no bundled default survives (ADR 0101 decision 2, "Ship no bundled default"); the choice is resolved from the consumer through docs/contracts/ecosystem-resolution/.
  • R8 (measured fact): cut it like the other rows and mark it in the pull request body as pending its targeted case; the host session's eval (below) decides whether it comes back, annotated portability-ok: measured <case-id>.
  • AC1's named exceptions are the kept classes of ADR 0101 (docs/adr/0101-resolve-ecosystem-specifics-from-the-consumer-repository.md, Decision and the 2026-11-17 amendment). Bundled defaults that pick a tool, command or library are retired wherever they appear (Interview Q32, D4 of the Brief).
  • Line numbers below were read at 5b66a7fa and may have moved; find each row by its cited text.

After the pull request opens (host session, not the lane)

The lane opens the pull request with Closes this issue and stops; it adds no label. The pull request stays held for the eval:

  • Hold line: a sweep or host session adds do-not-merge and posts, from a listed human's account, a comment with <!-- pr-hold reason=eval --> on a line of its own.
  • Targeted case per changed skill: one before-and-after case on sonnet at 3 runs a side, --case, --runs 3, a --max-cost-usd ceiling; opus only to confirm a sonnet loss; a new case gets a 1 to 3 run smoke first; start no batch after a usage-limit error (owner decision of 2026-11-16).
  • Controls: the owner's Q53 decision of 2026-11-17 (owner-decisions.md L202) reads: "each cut pull request is gated on a no-loss compare alone, with no wrong-text side". It supersedes Cut the model-read ecosystem specifics from tdd #16758's Controls line and its AC7 sentence ("each partial cut carries a detection-control result"). A whole-page deletion still states its predicted outcome in the pull request body before the first batch, and the record says the case cannot detect wrong text.
  • On a LOSS reading: a trace read of each dropped case and an opus confirm; only a loss traced to the changed text counts.
  • R8 rows: the row's targeted case with and without it; on a case drop or a mean fall of 0.15 or more without it, restore the row annotated portability-ok: measured <case-id>; a deterministic grader states before the run in how many of n runs it must fail.
  • Record: on a VALID no-loss run, post from a listed human's account <!-- eval-pair verdict=no-loss validity=VALID head=<40-hex head SHA> --> naming the current head, with no "do not merge" text (docs/contracts/loop-lane/README.md, "Cross-lane PR hold"). pr-merge's "Release eval holds whose record matches the head" step (.github/scripts/pr-merge/release-eval-hold.mjs) then removes do-not-merge; a later push needs a new record.

Out of scope

Rows outside this part's table, the parent's kept rows, every other plugin, toolchain's bundled defaults (#15733), and widening the portability gate (#15732).

Done when

  • Both rows are cut or replaced at a routing site; any cited listing already gone on main is listed as GONE.
  • The pull request body states this part's row count (2) and lists both row ids with their rule and outcome.
  • Each row's script-reader search is quoted in the pull request body; a row whose file a script reads is not cut, and is listed in the pull request body under a Script readers heading.
  • The pull request body names, for tdd:principles, the existing eval case that reads the cut text, or says none does.
  • The pull request body says, for each changed file, whether the cut deletes the whole page or part of it, with a predicted outcome for each whole-page deletion.
  • The skill-stack-fences ceilings for both files in .performance/ratchets.json are lowered to the fences left.
  • AC10: no new enforcement-placing skill is added.

Activity

  1. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 21, 2026
  2. github-actions commented on Nov 21, 2026

    @github-actions
    Contributor

    Size: Small
    Complexity: Low
    Uncertainty: Known
    Flags: none
    Blocked by: none
    Blast radius: two tdd:principles reference pages and two ceilings in .performance/ratchets.json. Plugin consumers and the model reading the skill see the change.
    Reversible: yes; revert the pull request.
    Open questions: none
    I read this as part 3 of 6 of #16758: cut the C#, xUnit.net, Moq and Fluent Assertions listings from observable-behavior-khorikov.md and testing-styles-khorikov.md under rule R11. Check each row's span first and list any listing already rewritten as GONE. Then lower both skill-stack-fences ceilings to the fences left. The done-when is exact and the issue's own text settles the approach, so I see no open question.

    The eval hold and targeted cases after the pull request opens are host-session work, not part of this lane. They don't hold the issue.

    Related issues are siblings in the same series: #17763 and #17764 for other tdd parts, with #16758 as the parent. These are not duplicates. I found no merged pull request that already does this cut.

    Automated triage. A maintainer reviews it.

  3. removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 21, 2026
  4. melodic-automation-lanes commented on Nov 21, 2026

    @melodic-automation-lanes
    Contributor

    {"v":1,"actor_id":337595936,"title_sha256":"c9e8c6b9182d3c55657a064c5447c84c7937786274ba2d0d07b089ebfc2812e8","body_sha256":"b57d0c527dd31e833f2a1bdc4debd91beec47c1fb5401ca19fc77a24804af010"}

  5. github-actions commented on Nov 21, 2026

    @github-actions
    Contributor
    No description provided.
  6. github-actions commented on Nov 21, 2026

    @github-actions
    Contributor
    No description provided.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Fields

    Work status

    needs-triage

    Priority

    medium

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions