Skip to content

ci: remove copied helpers from STEP1/STEP2 t27 ports #9631

Open

Description

@dmitrii-f-t27

Summary

Remove copied STEP1/STEP2 helper bodies through shared .t27 behavior. Active implementation is already assigned to the owner's Claude lane; do not start a second implementation.

Boundary

  • specs/port/trinity/fpga/openxc7-synth/trinity_block_step1_top.t27
  • specs/port/trinity/fpga/openxc7-synth/trinity_block_step2_top.t27
  • specs/port/trinity/fpga/openxc7-synth/trinity_block_common.t27

User Scenarios

Given both published port specs, when their generated behavioral tests run after helper extraction, then STEP1 and STEP2 retain their distinct frame types and existing behavior.

Requirements

FR-001: Shared helpers MUST be implemented once in .t27 and reused.
FR-002: Public contracts, constants, assertions and existing behavioral tests MUST be preserved.
FR-003: The detector and ratchet MUST NOT be weakened; no cosmetic renaming or manual generated-code edits.
FR-004: Necessary shared-module tests MUST cover boundaries and both frame types.

Success Criteria

The eight affected duplicate groups disappear through reuse. Parser/typecheck and executable tests of both ports exit 0. The gen_w generator family remains a separate lane. Final-SHA CI must be inspected before claiming green.

Evidence

PR9622 failed check: https://github.com/gHashTag/t27/actions/runs/38751547419/job/116478946837 .
The same 12 names were reproduced by the existing CI scanner on clean master cd8a656 (exit1); eight belong to this family: weight_sign, bit_at, uart_tx_bit_at, led_state_next, led_counter_next, debug_state_bits, build_report_frame, on_comb.
Related port/policy issues: #9370, #9415, #8963. The active Claude lane selected the shared-module path listed above.
Hardware, flashing, other ports and deployments are out of scope.

Dmitrii Fedorov (@dmitrii-f-t27)

Activity

  1. added
    shape-refusedClosed by the issue-shape gate (specs/policy/issue_shape.t27); a passing edit reopens it
    on Oct 15, 2026
  2. github-actions commented on Oct 15, 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
  3. removed
    shape-refusedClosed by the issue-shape gate (specs/policy/issue_shape.t27); a passing edit reopens it
    on Oct 15, 2026
  4. github-actions commented on Oct 15, 2026

    @github-actions
    Contributor

    The shape check passes now (specs/policy/issue_shape.t27); reopened.

  5. dmitrii-f-t27 commented on Oct 15, 2026

    @dmitrii-f-t27
    ContributorAuthor

    Coordination: the parallel codex/ci-repair-9622-9630 lane also prepared a STEP common module before discovering this lane. It will not publish a competing STEP PR; #9631 remains the publication issue. Its gen_w-family deduplication is verified separately: all eight ports retain 13/13 reference tests, and gen_w_tree passes 7/7 under reference and native (33 asserts). The STEP experiment used a parent fpga module path to avoid a hyphen in the use path; its common helper native tests passed 7/7 (49 asserts), reference/port validation is still pending. Please preserve both frame tags 0x43/0x44 and unchanged port test meaning. No duplicate-body baseline increase is allowed. Dmitrii Fedorov (@dmitrii-f-t27)

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions