ci: drop schedule: from the 8 workflows the Queen dispatches

[gHashTag]

Step 2 of the order in t27 docs/now/2026-09-13-the-queen-holds-the-scheduler-crons-and-skills-as-one-inngest-app.md: a function is seen firing, then a PR removes the schedule: block, then CONTROL becomes inngest.

Seen firing, gh run list --event workflow_dispatch on 2026-10-04, at the exact cron minute: agent-cron-cleanup (08:00, 10:00, 12:00), agent-queue-drain (every 5 min), brain-ci (Sundays 00:00), codegen (00:00 daily), discover-callers (05:41), pages-health-check (every 15 min), signal-health-self (04:23), site-live-gate (06:17). Each also ran from schedule, i.e. twice.

• schedule: removed from those 8 files; workflow_dispatch stays.
• brain-ci brain-trend-report was if: event_name == 'schedule'; it now also runs on workflow_dispatch, which is how the weekly run arrives.

Failures of agent-queue-drain, brain-ci, discover-callers, signal-health-self are fixed in a separate PR. CONTROL in the t27 cards changes after this merges.

Refs gHashTag/t27#6014

🤖 Generated with Claude Code

{
  "version": 1,
  "head_sha": "89e1935a9772c97304f78c4e80095d905aa6d844",
  "summary": "Eight trinity workflows lose their schedule block because the Queen's Inngest app already dispatches each of them at the same cron minute, so every one of them was running twice.",
  "changes": [
    "Removed the schedule: trigger from agent-cron-cleanup, agent-queue-drain, brain-ci, codegen, discover-callers, pages-health-check, signal-health-self and site-live-gate; workflow_dispatch stays in all eight.",
    "Each removed block is replaced by a comment naming the cron expression and the t27 card under specs/crons that the Queen dispatches from.",
    "brain-ci's Weekly Brain Trend Report job now runs on workflow_dispatch as well as schedule, because the weekly run now arrives as a dispatch."
  ],
  "tests": [
    {
      "command": "GitHub Actions: S3AI Brain CI on the pull_request event",
      "status": "passed",
      "result": "The edited brain-ci workflow parsed and its build, unit, integration and stress jobs passed on this head.",
      "evidence": "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/gHashTag/trinity/actions/runs/37202487648"
    },
    {
      "command": "GitHub Actions: Build & Test, Code Format Validation, Validate VIBEE Codegen",
      "status": "passed",
      "result": "Build, format and codegen validation jobs passed on this head commit.",
      "evidence": "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/gHashTag/trinity/actions/runs/37202487611 and https://github.com/gHashTag/trinity/actions/runs/37202487610"
    },
    {
      "command": "GitHub Actions: pr-opened project automation",
      "status": "failed",
      "result": "The project-board job failed on its own credentials; it does not exercise these workflow files.",
      "evidence": "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/gHashTag/trinity/actions/runs/37202487622/job/111436832731"
    },
    {
      "command": "workflow_dispatch of brain-ci Weekly Brain Trend Report",
      "status": "not_run",
      "result": "The trend report job under a dispatch event was not exercised before merge.",
      "evidence": "The job showed as skipping on the pull_request run 37202487648, as its condition requires."
    }
  ],
  "limitations": [
    "After merge these eight jobs run only when the Queen dispatches them; if the Inngest app stops, nothing in this repository schedules them.",
    "The dispatches were observed firing on 2026-10-04 by the author with gh run list; this report did not re-observe them.",
    "The CONTROL field of the matching t27 cron cards still has to change to inngest in a follow-up in gHashTag/t27."
  ],
  "tags": [
    "ci",
    "githubactions",
    "queen",
    "scheduler"
  ],
  "blog": {
    "title": "The Queen takes over eight trinity schedules",
    "summary": "Eight trinity GitHub Actions workflows were firing twice: once from their own schedule block and once from the Queen's Inngest dispatch. The schedule blocks are gone; the Queen is now the only scheduler for them.",
    "outline": [
      "The order for moving a cron to the Queen is to see the Inngest function fire, remove the schedule block in a pull request, and only then switch the card's CONTROL field.",
      "On 2026-10-04 gh run list showed workflow_dispatch runs at the exact cron minute for all eight workflows, alongside the schedule-triggered runs, so each job ran twice.",
      "The pull request deletes the schedule trigger from those eight files and leaves workflow_dispatch, with a comment pointing at the cron expression and the t27 card that owns it.",
      "brain-ci's weekly trend report was gated on the schedule event, so its condition now also accepts workflow_dispatch, which is how the weekly Sunday run arrives from the Queen.",
      "The trade-off is a single point of scheduling: if the Queen's Inngest app is down these jobs do not run, which is why the cards in gHashTag/t27 remain the source of truth."
    ]
  }
}

[github-actions]

X Brain Health Check

Score: 100.0/100
Status: 🟢 HEALTHY
Threshold: 80/100

X Brain is above merge threshold

[github-actions]

🧪 Brain Stress Test Results

Tests: 261/261 passed, 0 leaked
Status: 🟢 PASS
Gate: every test in zig build test-brain-stress passes and none leaks