Skip to content

Land 25 green trios-chat port PRs as one combined PR #10096

Closed as not planned

Description

@gHashTag

25 open port PRs (trios-chat rings, Refs #8884 / #8887 and siblings) have green required checks and pass the duplicate-body ratchet together, but cannot land one by one:

  • each adds one row to docs/reports/t27b_expectations.json; neighbouring rows collide, so every merge on master makes the next PR CONFLICTING again;
  • each PR re-queues ~29 jobs, and the Actions queue did not finish one round before master moved (all rebuilt heads were still pending when 17 of them were already DIRTY again).

Land them as one PR: one commit per original PR, original author kept, ledger rows resolved as the union of both sides (sorted, one verdict per path; the resolver refuses a path with two different verdicts). Then close the 25 originals as landed.

Checked before opening, on the Railway lab:

  • tools/dupe_scan.py on master plus all 25, applied in order: no error that master does not already have;
  • only .t27, .trinity/seals/*.json, docs/now/*.md and the ledger change; no foreign code; no secret-shaped added line.

Not in this batch: #9650, #9651 and #9652 (each adds another copy of ids_equal / hashes32_equal, which master already carries in CR-CHAT-03), and 76 other port PRs that each add their own copy of the same helper (66 of them ids_equal([16]u8, [16]u8)); together they break the duplicate ratchet and need one shared helper first.

Activity

  1. added
    shape-refusedClosed by the issue-shape gate (specs/policy/issue_shape.t27); a passing edit reopens it
    on Oct 17, 2026
  2. github-actions commented on Oct 17, 2026

    @github-actions
    Contributor

    Closed by the issue-shape gate (specs/policy/issue_shape.t27, #7498): an issue must have the template's sections. Edit the body; an edit that passes reopens it.

    • missing: ## Boundary -- list every file this task may touch, one per line (- specs/x.t27); without it the Queen reserves nothing and no bee can take the issue
    • missing: ## User Scenarios -- at least one Given/When/Then scenario
    • missing: ## Requirements -- numbered obligations, FR-001: ... MUST ...
    • missing: ## Success Criteria -- an outcome a machine can settle: a number with a unit, a backticked file, exit 0, or a backticked command
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

    shape-refusedClosed by the issue-shape gate (specs/policy/issue_shape.t27); a passing edit reopens it

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions