Skip to content

Seshat BI v0.8.1

Choose a tag to compare

View all tags
@Kemetra Kemetra released this 02 Aug 15:55
· 416 commits to main since this release
v0.8.1
aec1d87
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Patch release. Full detail in docs/releases/v0.8.1.md and CHANGELOG.md.

Install

pipx install seshat-bi==0.8.1

Why upgrade

The bundled governor MCP server no longer hangs. In v0.8.0, seshat_run_static_check never returned when the plugin ran the governor over stdio — over 11 minutes with no output, against a 12-second CLI baseline for the identical check. One of the six governor tools was unusable for anyone who installed the plugin, with no workaround. (#557, PR #558)

subprocess.run(...) without an explicit stdin gives the child the parent's stdin. For seshat mcp that handle is the live JSON-RPC pipe from the client: git inherited it and blocked reading it, while the parent blocked in communicate() waiting for git — and the pipe could only be fed by the MCP client, which was itself waiting for the response.

Only that one tool hung, because it is the only governor tool that shells out to git. The CLI was never affected, because there stdin is a terminal and inheriting it is harmless — which is the whole 12-seconds-versus-forever gap.

Fixed with a single gitutil.run_subprocess helper (stdin=DEVNULL plus a default timeout, so a residual stall fails loud rather than hanging), with 11 governance call sites routed through it. The dbt/dagster execution runners are deliberately excluded: they invoke user builds that legitimately outlive the shared cap and are not reachable from the read-only governor tools.

Covered by a regression test that spawns the real server and drives it over a pipe — the only shape that reproduces the defect, since the existing in-process tests return in 0.2s. Verified failing on the unpatched code before being trusted green.

Also in this release

  • Four corrected facts in the public-catalog submission guidance (#556). The runbook is copied into an external portal under a verified identity, so a wrong path or capability answer is a submission defect. It cited plugin manifest paths at the repository root that do not resolve, told the owner to declare no MCP server when both bundles ship seshat-governor, and gave a skill-count command that silently returned zero for the Claude bundle. The shipped Codex bundle README carried the same false "activates no ... MCP server" claim and was corrected at its template and regenerated.

What has not changed

  • No new capability, verb, skill, or rule. Both bundles still carry 21 skills.
  • No governance behavior changed. No tool advances a stage, grants an approval, writes a readiness artifact, or emits a score.
  • Spec 138 remains partially implemented — US2 and US3 delivered; US1, US4, and the external-acceptance half of US5 outstanding.

Note on MCP acceptance

This release fixes a defect in the bundled MCP server; it does not constitute external acceptance of that server. Spec 138 US1 (T021–T023) still requires operator-run verification in a clean workspace with no Seshat development checkout. Any public-catalog submission should declare the seshat-governor MCP server (local, read-only, stdio, no auth) and should not claim verified external MCP behavior.

Assets 2
Loading