Skip to content

feat(t27mcp): dashboard.t27 -- grades and next step of the t27 MCP session dashboard - #10249

Merged
gHashTag merged 1 commit into
masterfrom
t27mcp/dashboard
Oct 18, 2026
Merged

gHashTag merged 1 commit into
masterfrom
t27mcp/dashboard

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

What

specs/t27mcp/dashboard.t27 (module T27mcpDashboard) is the logic of the t27 MCP server's session dashboard. That is one page that tells the agent and the human operator four things:

  • whether the corpus is healthy enough to reuse from
  • whether a tool call failed
  • whether a reply grew past what the host shows inline
  • what to do next

The spec does the following:

  • Grades: ok < unknown < warn < bad. worst() never lets unknown add up to ok.
  • health_tone: bad at 5 in 100 failing specs. It warns when any spec fails or when 20 in 100 warn, and it is unknown when the manifest names no spec.
  • calls_tone: bad when one call in four failed, warn when any call failed, unknown before the first call.
  • reply_tone: warn above 8192 bytes, bad above 25000. On 2026-10-18 a plain t27_status reply was 57,084 bytes.
  • next_step: picks one line of NEXT_TEXT, most urgent first.
  • Texts and templates: UNKNOWN_TEXT names what the page cannot know from the server's data, so a blank reads as unknown. The page templates ({} marks, filled left to right) are here too, so the server only counts and fills.

The server side is gHashTag/t27-mcp dashboard.mjs: the tool t27_dashboard plus the MCP Apps resource ui://t27/dashboard.

Evidence

  • Lab, t27c 0.5.2: the test report gives 8 of 8 pass and 0 vacuous.
  • Negative controls: each of six mutants fails at least one test.
    • worst() returning the milder grade fails 2.
    • An exclusive 5-in-100 boundary fails 1.
    • An empty manifest read as ok fails 1.
    • A failed call left ungraded fails 1.
    • Inclusive reply thresholds fail 1.
    • Size checked before a failed call fails 1.
  • The C route (wasm32-wasi reactor) gives a 404-byte wasm, sha256 450af040...0798.

Refs #10066

🤖 Generated with Claude Code

…ssion dashboard

One page for the agent and the human operator: corpus health, this
session's calls, errors and largest reply, and the next step. The spec
grades each number (ok, unknown, warn, bad; worst() never lets unknown
add up to ok), picks one next-step line, and holds the page templates
and the "not known here" texts. The server only counts calls and fills
the templates (gHashTag/t27-mcp dashboard.mjs).

t27c test-report: 8 of 8 pass, 0 vacuous. Six mutants (milder worst,
exclusive 5-in-100 boundary, empty manifest read as ok, ungraded failed
call, inclusive reply thresholds, size before a failed call) each fail
at least one test.

Refs #10066

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

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-18 06:02:24 UTC

Summary

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

Seal Status

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

@gHashTag
gHashTag enabled auto-merge (squash) October 18, 2026 06:06
@gHashTag
gHashTag merged commit 8a37566 into master Oct 18, 2026
27 of 30 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.

1 participant