feat: prepare MainFrame v0.4.0 with MindGraph - #3
Merged
Merged
Conversation
Owner
Author
Public CI receiptThe public release-surface workflow has now executed against this exact PR head:
This was a real executed run. The following product steps completed successfully:
The earlier private-repository zero-step failures remain recorded as |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
MainFrame v0.4.0 public review candidate
This PR promotes the reviewed MindGraph capability into the public MainFrame
surface. It is generated from merged private
main, uses the positive exportmanifest, and does not tag or release v0.4.0.
Source chain
726f9d83126ce65f17224bc6599ce222b21b54ad(
403de41eb3b5daa065caee1de53609998c7f2fdc).f0b6083ade7b63589756ea11ee76329cc6feda40(
919e45d28060c829791c2ac03f6c3226feb79435).6501024a19dd9feae415a7197a65c70ff214c40a(
e08d009836e62f5d23754886329d3fc91bc4fcae).71280be791edd98baf5b684dbd682acb07a86129(
e08d009836e62f5d23754886329d3fc91bc4fcae).The standalone merge advanced the commit identity without changing the
qualified tree. The exporter still binds the selected nested files to the
qualified source commit and tree.
Public snapshot
codex/mainframe-v04-public6bfa334b53de75d5eda792e66b6dbed104aa3baacb1134498905158979dfd6313b3742a7796af46aengine-with-optional-semantic-and-mcp781cffa982e7bf7fdf084e3dadb45b8b263db0b126d04c3c6af67766e2f156e35b3b7eb0a16b5c13cebcca31c87050d7bc8b924c4c2483e3424aa29e0b5d5aa7119035e617cfc7b7b5660562deedf0cbbf9d6959675736cfefb3b09dc3e64e4f45f9ee2ab4cd5bcf6a2433718da99a9da86866ee49eb0b2cf43699fa9af8a38The candidate is identical to the earlier pre-merge candidate. The only
receipt-level change is the private source SHA:
ee805cea...became mergedprivate
f0b6083...; the private tree, selected files, and output bytes didnot change.
MindGraph provenance binding
git-blob-sha1.8e60480a52e295e806a3c292e1525f03e7aec7412ee4a1c049a08a05751e30c8.71280be791edd98baf5b684dbd682acb07a86129and treee08d009836e62f5d23754886329d3fc91bc4fcae:5be688bc582f3219d676ebd2dd688025adce11ab6bbe085d5f2af779ab31540d214c74890a268b25891b7c5a550a6f6bc0c4e56bbc7a257541b4ede9949b3685ee4c94ffe3a9193aac076d29c3e91728d734290a2ae55edc1b0dc46060a64ae9Difference from v0.3.0
The diff contains 48 changed paths:
maintained tests, and
uv.lock.boundary.
.github/workflows/public-core.ymladds the dependency-light MindGraph coretest step.
All 108 tracked v0.3.0 control files remain present. No databases, model
caches, private state, or MainFrame operational outputs were copied.
Qualification
Run from a clean copy of the exact regenerated candidate:
JUnit SHA-256:
3d6eaad1e034f2253a342860a272f6f8613f082b10fb460c9bd5bd9b40eddc57.48,368 KiB environment size; no semantic, Torch, Transformers, or MCP
packages.
JUnit SHA-256:
155563f08a91a663446e0a1d5beed3416bc4c604ce3f0daec7db6321c3f3eb37.KiB environment size, and 89,480 KiB model cache after explicit
all-MiniLM-L6-v2bootstrap.environment size using MCP 1.30.0 under
mcp>=1.0.0,<2.contract-lint --selftest: 13/13 passed.uv lock --check: passed.Semantic and MCP behavior remains covered by the exact source-bound receipts
above. The candidate bytes and selected MindGraph blobs were independently
compared with the pre-merge candidate and are identical.
Privacy and export boundary
The positive manifest and exporter check passed with:
publication_performed=false;AGENTS.mdor.gitignore;test_link_audit.pyor retiredtest_pruning.py;The only
/home/string is the generic documentation example/home/me/notesin MindGraph's provenance model; it is not a host path fromthe build environment. Generic
~/.mindgraphreferences describe thedocumented runtime default and do not include local state.
Known CI history
Private MainFrame run
34542351550and current-head run34560423883remain
CI_NOT_ASSESSED: GitHub reported failed jobs with zero executed stepsand no logs. They are not treated as product test failures. The public
repository Actions run for this exact branch is the release-surface behavioral
gate.
Release boundary
This PR is review-only. MainFrame v0.2.0 and v0.3.0 are unchanged. No v0.4.0
tag or release has been made. Merge and release remain separate decisions after
the public Actions result and final review.