Skip to content

Fix beta.8 campaign findings for beta.9 - #249

Merged
Proxicon merged 11 commits into
mainfrom
fix/beta9-campaign-findings
Oct 20, 2026
Merged

Proxicon merged 11 commits into
mainfrom
fix/beta9-campaign-findings

Conversation

@Proxicon

@Proxicon Proxicon commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Signed public ticket views can expose an internal worklog, and approval startup can fail after a request or predecessor task has already committed. This beta.9 candidate repairs those paths and the other eight recorded beta.8 findings at their API, MCP, provider-contract and logging layers.

The finding-by-finding before/after and reproduction map covers all ten finding IDs and both post-commit triggers. The baseline manifest records the original archive and finding hashes. Beta.8 remains NOT_READY: 350 PASS, 16 FAIL, 16 NOT_RUN, 7 fixed exclusions across 389 operations. Its archive and receipts are unchanged.

Includes the unchanged reusable HTTP MCP/backend harness commits from draft #248 and extends independent read parity for Prometheus metrics and populated warning assertions. Updates the current MCP catalog/revision and root-owned candidate version. No release publication or deployment.

Sixteen operations remain unproven without live provider permissions, pairing, populated state or an isolated instance. In particular, bootstrap-defaults is blocked by unrelated organization effects, not by missing credentials. No source test is claimed as a live campaign pass.

Validation

  • Focused regressions added at owning layers, including real HTTP/stdio MCP and SQLite/PostgreSQL API routes.
  • Final focused .NET/API/HTTP-MCP/provider regressions: 98 passed, 0 failed, 0 skipped. Includes signed-public tests, both post-commit entry points on SQLite/PostgreSQL, and existing structured connection-selection/pagination failure contracts.
  • 25 opt-in synthetic reproduction receipts cover all ten finding IDs; CI retains them in the .NET test-results artifact.
  • Shared HTTP MCP envelope test covers all 389 operations with zero upstream requests; duplicate fields rejected in HTTP and stdio.
  • Offline HTTP MCP harness: 21 passed.
  • Layout and documentation checks passed.
  • Release solution build passed with 0 errors.
  • Full hosted .NET suite: 3,296 passed, 0 failed, 8 existing skips (3,304 total).
  • Receiver HTTP/provider acceptance: 399 passed, 0 failed, 0 skipped; complete-evidence guard passed.
  • All six normal validation jobs passed for final head 3fe71d70d88b310f71566c9c8dabd9fe36db03af in run 39416152886. Optional deep acceptance/release jobs retained their normal skip conditions.
  • Existing approval-service unit tests: 16 passed.

Disclosure check

  • Original private campaign captures, credentials, signed URLs and fixture identifiers are excluded. Only finding paths/hashes and synthetic reproduction fixtures are included.

Reproduction artifacts: full .NET TRX plus 25 synthetic finding receipts, receiver/provider TRX. GitHub artifact digests are sha256:3de321df5cab0354442fdeb54bd269c09dd4270146ca558996877a75ca211de3 and sha256:fb33fc9e6731eaf35b078bff5d19b8539b894dfe7420aa0c5a771534fdc108f7, respectively.

@Proxicon
Proxicon marked this pull request as ready for review October 20, 2026 12:20
@Proxicon
Proxicon merged commit 900621f into main Oct 20, 2026
28 checks passed
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 20, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
🔒 Security Review ✅ Completed 2026-10-20T12:21:28.810640Z 3fe71d7 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

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