Skip to content

specs/automation: inngest-probe-suite.t27 — safe probe suite behind /inngest_probe - #3556

Merged
gHashTag merged 1 commit into
masterfrom
specs/inngest-probe-suite
Sep 10, 2026
Merged

specs/automation: inngest-probe-suite.t27 — safe probe suite behind /inngest_probe#3556
gHashTag merged 1 commit into
masterfrom
specs/inngest-probe-suite

Conversation

@gHashTag

@gHashTag gHashTag commented Sep 9, 2026

Copy link
Copy Markdown
Owner

Closes #3559

What

specs/automation/inngest-probe-suite.t27 — the spec of the safe probe suite the bot's admin command /inngest_probe runs (host gHashTag/999-multibots-telegraf #2325 merged, #2326 merged, #2331 open).

States: payload = manifest safe_probe + e2e_test: true forced; transport = Inngest GQL invokeFunction; slug <appId>-<ID>; run found by functionID + queuedAt window (5 s lookback) + eventName prefix inngest/function.invoked; poll 3 s, budget 120 s; expectations FAILED-at-guard | COMPLETED | skip; verdicts match | mismatch | timeout | invoke-error | skipped; suite ok iff no mismatch/timeout/invoke-error; forbidden side effects (charges-balance, paid-api, messages-user, messages-owners); one suite at a time; admin only, inline-button confirm.

Also in this PR (2026-09-10):

Verdict

Vendored wasm (trinity/apps/website/public/t27/t27_compiler.wasm): typecheck ok, 0 discarded, hir ok — 27 consts, 3 structs, 3 tests. Necessary, not sufficient (the wasm accepts wrong annotations). Bootstrap compiler on master not run locally; CI runs it.

Status (honesty)

LIVE_RUN_STATUS = "not-yet-run" stays for the bot's own report. Two suites have been judged offline: the admin's run of 2026-09-09 19:11Z (28/28 with the corrected rule, host #2326) and a mirror run of 2026-09-10 02:16Z with the bot's own code, which exposed two judge defects (21 of 28 never judged; a step span left RUNNING) fixed in host #2331 and re-judged 28/28. Counts (28 planned = 17 FAILED-at-guard + 11 COMPLETED) are from the manifest at mb main.

Not in this PR: a PROBE_EXPECT constant on the 28 function cards (needs the site generator schema in trinity to accept it); the 404 branch of training-stuck-check as a declared step. gate-topology and untrusted-input failed on the previous run; whether they pass now is for this CI run to say.

@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-09-09 18:53:09 UTC

Summary

Status Count
Total Open PRs 16
PRs with Failing Checks 13
PRs with All Checks Green 3
READY 2
FAILING 13
PENDING 0
NO CHECKS YET 0

These columns do not partition: 2 + 13 + 0 + 0 = 15, and there are 16 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=d4c5b22b471e != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

…ed Inngest function behind /inngest_probe

Closes #3559

- specs/automation/inngest-probe-suite.t27: payload = manifest safe_probe
  + e2e_test true; transport = Inngest GQL invokeFunction; expectations
  FAILED-at-guard | COMPLETED | skip; verdicts; forbidden side effects;
  one suite at a time; admin only.
- specs/functions/training-stuck-check.t27: NOTE states the 404
  retirement (host #2328).
- tools/published_figures.py: test-blocks pin 12462 -> 12465 (the three
  test blocks of the new spec; #3557 had moved 12456 -> 12462), the
  movement written in the pin's note.
- docs/now/2026-09-10-inngest-probe-suite-as-a-t27-spec.md.
@gHashTag
gHashTag force-pushed the specs/inngest-probe-suite branch from 3f412db to 7d6e78d Compare September 10, 2026 02:39
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-09-10 02:39:53 UTC

Summary

Status Count
Total Open PRs 16
PRs with Failing Checks 14
PRs with All Checks Green 2
READY 2
FAILING 14
PENDING 0
NO CHECKS YET 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=d4c5b22b471e != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@github-actions

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@gHashTag
gHashTag merged commit 4dfb1ab into master Sep 10, 2026
30 of 32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

specs/automation: inngest-probe-suite.t27 — safe probe suite behind /inngest_probe; training-stuck-check 404 retirement

1 participant