Skip to content

ci: remove the stale assertion for retired brain-seal-refresh workflow #9640

Closed as not planned

Description

@dmitrii-f-t27

Summary

Retire a stale integration assertion that includes a workflow intentionally deleted from master. This is part of CI recovery for all pull requests authored by dmitrii-f-t27. Active work is assigned to Claude lanes; avoid duplicate implementation.

Boundary

  • cli/tri/src/gates.rs
  • tools/census/quiet.txt
  • tools/census/shell.txt

User Scenarios

Given current master with no brain-seal-refresh.yml, when cargo builds all tri targets and runs the existing cause_removed tests, then compilation succeeds and the active parser/footnote contract remains tested.

Requirements

FR-001: The stale test whose only subject was the retired workflow MUST be removed without removing the inline cause_removed parser and footnote guards.
FR-002: No handwritten Rust addition, restored obsolete workflow, skip-ratchet weakening or hook bypass MUST be introduced.
FR-003: Any necessary census update MUST be generated by the existing tool and attributable exactly to the retired test; unrelated movement must be investigated.
FR-004: The final PR MUST have a verified dmitrii-f-t27 author and current-SHA CI evidence.

Success Criteria

cargo build -p tri --all-targets exits 0. The remaining cause_removed parser and footnote tests pass. The relevant census gates pass with no hand-edited census data. The cli-tri check on the final SHA succeeds.

Evidence

Master cd8a656 still contains include_str! for .github/workflows/brain-seal-refresh.yml in cli/tri/src/gates.rs:9012.
CI failure: https://github.com/gHashTag/t27/actions/runs/38758247650 .
The workflow was retired and its derived-data work moved to queen-publish (#2915, #9092, #9117). Do not resurrect it.
Related CI recovery tasks: #9600, #9631, #9632, #9633, #9635.

Dmitrii Fedorov (@dmitrii-f-t27)

Activity

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

    @dmitrii-f-t27
    ContributorAuthor

    Closing as a duplicate of #9634. That issue already carries the owner's approval and the request to @gHashTag for the same gates.rs activation change (#9634 (comment)), and the base activation PR #9639 follows it. Further discussion belongs there.

    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