Skip to content

Reseal process.t27 and kanban-card-chat.t27 with a current t27c (master coverage red) #6239

Closed

Description

@gHashTag

Refs #5776. Follow-up of #6221.

Context

Master's coverage check fails with FAIL: 3 seal(s) newly do not hold after the 2026-10-04 batch merge: specs/runtime/process.t27 (changed in 3d73d51 after sealing; it has two seal files) and specs/automation/kanban-card-chat.t27 (changed in 9a5b7f5). The workstation's t27c is from 2026-10-02, about 30 codegen commits old, so resealing there would write hashes the current compiler does not produce.

Requirements

  • FR-001: the seals MUST be written by a t27c built from current master (Railway lab t27c-lab or CI), never the workstation.
  • FR-002: run t27c seal <spec> --save for both specs, then tri seals sync-twins.

Acceptance criteria

  • coverage is green on the PR.

Boundary

  • specs/automation/kanban-card-chat.t27
  • specs/runtime/process.t27

Activity

  1. added
    needs-boundaryNo '## Boundary' section, so the Queen can reserve nothing for it and no bee can take it
    and removed
    needs-boundaryNo '## Boundary' section, so the Queen can reserve nothing for it and no bee can take it
    on Oct 5, 2026
  2. gHashTag commented on Oct 5, 2026

    @gHashTag
    OwnerAuthor

    Already done on master: 9d3f657 (chore(seals): re-seal kanban-card-chat and runtime/process after their spec changes) wrote the same three seal files this issue asks for, and 8fe2857 resealed them again after the gen-zig field-syntax fix. The bee branch queen-6239 carries an older copy of the same reseal and is superseded. Closing; reviewed by hand in the review-jam pass (lane A).

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