Skip to content

Release 1.1.0 — operator web UX + SEI conformance#2

Closed
tachyon-beep wants to merge 1 commit into
mainfrom
release/1.1.0
Closed

Release 1.1.0 — operator web UX + SEI conformance#2
tachyon-beep wants to merge 1 commit into
mainfrom
release/1.1.0

Conversation

@tachyon-beep

Copy link
Copy Markdown
Contributor

Release 1.1.0

Cuts the 1.1.0 release. The 1.1.0 code already landed on main via PR #1 (operator-facing webUX MVP + SEI conformance consolidation); release/1.1.0 was identical to main, so this PR carries the release ceremony that makes the version real:

  • Bump _version.py 1.0.0 → 1.1.0 (minor bump — additive, no breaking changes).
  • Add the [1.1.0] CHANGELOG section + release link reference, drawn from the 35 commits since v1.0.0.

Merging this is the reviewable release gate; tag v1.1.0 after merge.

What 1.1.0 contains

  • Operator web UI (plainweave web, optional plainweave[web] extra) — read-and-author mirror of the intent graph: intent dashboard (coverage / orphans / no-silent-clean banner), corpus browse, requirement detail & authoring (current-vs-draft, two-step approval), goals, and a unified review queue (drafts + trace links, accept/reject with required reason, drift-confirm).
  • SEI conformance — Plainweave becomes the 4th SEI conformer; producer freeze (wire golden) for the Legis preflight-facts envelope.
  • Security & hardening — CSRF middleware (body-preserving, cold-start 403 fixed), input-validation 400s, authority/operator-actor attribution, output hygiene, structural accessibility contracts + recorded manual AT gate.
  • Docs — README install + coverage north-star, CONTRIBUTING, web UI quickstart, webUX design spec & implementation plan.

Compatibility

Additive and backward-compatible — the 1.0 CLI, MCP surface, store schema, and JSON envelopes are unchanged. The web UI is opt-in via the [web] extra and stays advisory and verdict-free.

Verification

  • Full test suite green on the bumped state (uv run pytest).
  • Resolved package version reports 1.1.0.

🤖 Generated with Claude Code

Bump version 1.0.0 → 1.1.0 and add the [1.1.0] CHANGELOG section.

The 1.1.0 code already landed on main via PR #1 (operator-facing webUX MVP
+ SEI conformance consolidation); this commit carries the release ceremony so
release/1.1.0 is a reviewable release gate. Additive and backward-compatible:
the 1.0 CLI, MCP surface, store schema, and JSON envelopes are unchanged.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
tachyon-beep added a commit that referenced this pull request Jun 27, 2026
… Wardline work)

Owner is implementing the Wardline scan_manifest metadata in parallel for
integration testing, so make the exact-scope path primary: the adapter
consumes scope.covered_paths/scan_id/ruleset_id/commit to compute resolved/
unseen against the actually re-scanned surface, adds wardline_ruleset_mismatch
when rulesets differ, and degrades to the path-set heuristic (flagged
wardline_scan_identity_absent) only when the manifest is absent — correct on
today's manifest-less .wardline/ data, exact once the parallel work lands.
Prompt #2 reframed from future ask to agreed parallel contract.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@tachyon-beep

Copy link
Copy Markdown
Contributor Author

Superseded: main has been fast-forwarded directly to include the 1.1.0 release (commit de13416, tagged v1.1.0) plus all subsequent peer-facts and CLI-parity work. origin/main is now at 8258f76 and the v1.1.0 tag is pushed, so this release branch is behind main and no longer needed. The 1.2.0 ceremony will go out via a fresh release/1.2.0 PR.

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