MBTI-GSC-25: GSC submission and monitoring execution#1728
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 41d203c4cd
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| const report = { | ||
| id: "MBTI-GSC-25", | ||
| artifact: "MBTI-GSC-25-SUBMISSION-MONITORING-EXECUTION", | ||
| generated_at: evidence.captured_at, |
There was a problem hiding this comment.
In this GSC-25 evidence flow, evidence.captured_at is the initial Search Console UI capture time, but the same report embeds post-submission INDEX-24R rechecks from much later in the day. Copying that earlier capture time into generated_at makes the generated artifact claim it predates some of its own input evidence, so freshness checks or monitoring jobs keyed off generated_at can treat the final gate as stale or chronologically impossible after a rerun. Use the builder run time or the latest evidence timestamp instead.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d1a109bf9c
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| title: "CAREER-DIRECTORY-ERROR-SEMANTICS-01 career directory error semantics" | ||
| train_scope: career_10k_stability | ||
| status: in_progress | ||
| status: pr_open_checks_pending |
There was a problem hiding this comment.
This GSC-25 metadata update changes the unrelated CAREER-DIRECTORY-ERROR-SEMANTICS-01 manifest entry to pr_open_checks_pending, but the state ledger already records that same train item as merged with PR #1680 merged at 2026-07-11T07:03:07Z. Any train tooling that reads the manifest status will now treat a completed career PR as still open/pending, which can block dependency progression or cause duplicate follow-up work; this entry should remain merged or be left untouched by the GSC-25 PR.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: de038e978c
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "commit_sha": null, | ||
| "pr_url": null, | ||
| "checks": [], | ||
| "commit_sha": "41d203c4cd3d6900bc4f3eee8dcbf5ae17969cd8", |
There was a problem hiding this comment.
This ledger entry records 41d203c4..., but the reviewed PR tree is at 5b3f8c67149a37a966e2fef07af41c4e08d258ac and 41d203c4... is not an ancestor of that commit. Any PR-train closeout or post-merge reconciliation that verifies commit_sha against the PR head or origin/main will be checking the wrong object, so the item can appear unmerged or its GitHub checks can be attributed to a stale commit after the final metadata-only commit is pushed.
Useful? React with 👍 / 👎.
1 participant
What changed
Why
GSC-25 was blocked after llms.txt temporarily omitted all nine promoted MBTI URLs. The deployed frontend revision restored stable authority enumeration, and two consecutive production gates now satisfy the release dependency.
Validation
node scripts/seo/build-mbti-index-24r-release-gate-revalidation.mjs --allow-networkruns: all metrics 9/9, zero private URL leaksnode scripts/seo/build-mbti-gsc-25-submit-monitoring-execution.mjspnpm lint . --max-warnings=0pnpm typecheckpnpm test:contract: 4 shards / 4,131 testsgit diff --check, exact manifest scope validationDeferred
Repository rule impact
No authority ownership or runtime rule changes. Backend/CMS remains authoritative; this PR contains evidence and monitoring artifacts only.