Skip to content

specs/automation: inngest-functions-status.t27 (lastRun без проб, lastProbe отдельно) + inngest-probe-suite VERSION 2 - #5631

Merged
gHashTag merged 1 commit into
masterfrom
bee/replace-3593
Oct 2, 2026
Merged

gHashTag merged 1 commit into
masterfrom
bee/replace-3593

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 2, 2026

Copy link
Copy Markdown
Owner

Что

  1. Новая спека specs/automation/inngest-functions-status.t27 — контракт маршрута GET /api/inngest/functions/status, который читает вкладка FUNCTIONS на t27.ai.
    Ключевое (VERSION 2): lastRun = последний органический запуск (event/cron); invoked-запуски (пробы /inngest_probe, кнопка Invoke) в него не попадают — они выносятся в отдельное поле lastProbe с ожиданием из манифеста (probe_expect) и asExpected на уровне статуса. Функция без органических запусков — muted, не красная и не зелёная.
  2. inngest-probe-suite.t27 → VERSION 2: LIVE_RUN_STATUS больше не «not-yet-run» — перечислены три продовых прогона; явно отмечено, что Telegram-путь смерженного судьи не засвидетельствован; добавлены PROBE_RUN_IS_HEALTH_SIGNAL=false, PROBE_FAILURE_ALERTS_ADMIN=false.

Зачем

Продовое чтение статуса 2026-09-12T14:01Z: 28 функций, у 20 lastRun.status = FAILED — все 20 от проб 9–10 сентября, спроектированных падать на guard; 22 из 28 не имели ни одного органического запуска за 7 дней. Вкладка показывала 20 красных точек за функции, которые ничего плохого не сделали. Логика исправления заявлена здесь до реализации в хосте (999-multibots-telegraf) и в потребителе (trinity FunctionExplorer).

Откуда свидетельства

  • Invoked-запуски всех трёх прогонов видны в продовом GraphQL Inngest (прочитано 2026-09-12).
  • 28/28 match, commit хоста 224a87f и интервал 03:19:17–03:20:05Z — из docs/inngest/witness/2026-09-10-probe-suite-03-19Z.json в репозитории хоста (28 записей, все match).
  • «17 mismatch» (19:11Z) и «21 skipped» (02:17Z) — как записано в docs/inngest/probe-suite.md хоста; независимо не перепроверены, в спеке помечены как записанные хостом.

Проверка

Вендорный wasm (trinity/apps/website/public/t27/t27_compiler.wasm): оба файла typecheck ok, 0 discarded, hir ok; 30 и 33 константы, 3 структуры и 3 test-блока в каждом. Bootstrap-компилятор на master локально не запускался — это скажет CI.

Не в этом PR

Реализация в хосте и на сайте (отдельные PR); PROBE_EXPECT на 28 карточках функций.

Refs #3559 (the probe-suite spec this PR moves to VERSION 2).


Supersedes #3593. Same net diff, one commit with an issue reference so L1 TRACEABILITY passes.

Refs #3559

🤖 Generated with Claude Code

…tProbe отдельно) + inngest-probe-suite VERSION 2

Supersedes #3593: same net diff as one commit carrying an issue reference.

Refs #3559

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-02 21:30:40 UTC

Summary

Status Count
Total Open PRs 34
PRs with Failing Checks 30
PRs with All Checks Green 4
READY 1
FAILING 30
PENDING 0
NO CHECKS YET 0

These columns do not partition: 1 + 30 + 0 + 0 = 31, and there are 34 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=b45a356c2eb6 != 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

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

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

@gHashTag gHashTag added the bee-reviewed A reviewer bee reviewed and verified this PR at its current head; the only merge signal (#5525) label Oct 2, 2026
@gHashTag

gHashTag commented Oct 2, 2026

Copy link
Copy Markdown
Owner Author

Bee review evidence (reviewer bee, not the author)

Head: f9a02fb9cbe0ffb71a35ff61e33b000776ee8d30, one commit on master 7079823. The commit message carries Refs #3559, the same issue the original #3593 referenced.

Tree identity: replacement tree 92bdc0d333b91c3a292eb62d441ba67f735acba3 == the tree of the original #3593 head 6924780ffba143f69dc3b52e11eca02a9b1df739. This was checked through the GitHub commits API, so git diff 6924780ffba143f69dc3b52e11eca02a9b1df739 f9a02fb9cbe0ffb71a35ff61e33b000776ee8d30 is empty.

Content: 3 files. The new spec specs/automation/inngest-functions-status.t27 covers the status route contract: the lastRun/lastProbe split, a function with no organic run shown as muted, and 3 tests. inngest-probe-suite.t27 moves to VERSION 2, with LIVE_RUN_STATUS witnessed, PROBE_RUN_IS_HEALTH_SIGNAL=false and PROBE_FAILURE_ALERTS_ADMIN=false. The third file is the NOW entry. The PR has no secrets and nothing unrelated to its topic.

Mergeable: MERGEABLE (UNSTABLE only because of the red checks below). Re-read after #5630 merged.

Red checks discounted, each confirmed red on master or on every PR:

  • spec-guards: fails at step "Does every seal still describe what the compiler emits" on this PR, and the same step fails on master 1cf5252 (job 111036327348).
  • emit-bitexact: fails at "GF-T primitives agree across C + Rust + Zig + model" with gft_sadd.sadd: Zig backend failed to build/run. The workflow has no master push trigger (last master run: a workflow_dispatch on 2026-08-28). The same step fails on unrelated PRs, for example feat/source-kind, payment-claim-spec and sweep-spec.
  • Master 1cf5252 is also red on untrusted-input (step "Every re-taken proposition is still anchored": "the corpus size is stated somewhere in the re-takes"), Scorecard and test-ratchet.

Required checks green: validate, check-linked-issue, parse-ratchet, Check L1 TRACEABILITY, L1 Traceability Summary, check-now-freshness, and GitGuardian.

@t27-bees t27-bees Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bee review: see evidence comment

@gHashTag
gHashTag merged commit b6d1d5c into master Oct 2, 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

bee-reviewed A reviewer bee reviewed and verified this PR at its current head; the only merge signal (#5525)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant