Open
Conversation
Replay the STEP-03 governance preflight reports onto docs-v2-dev and refresh derived component governance metadata/content required by the branch state.
Move the English orchestrator advanced pages under v2/orchestrators/advanced, absorb the payments page into the section, and refresh the generated nav/search/link-map artifacts.
Archive the legacy orchestrator reference sources after moving the canonical FAQ, CLI flags, and community-pools pages under v2/orchestrators/resources.
Replace the short orchestrator FAQ with the full troubleshooting draft, normalize frontmatter to the repo schema, and preserve review notes. Refs: TASK-ORCH-2A
Import the TASK-ORCH-2B job types draft with REVIEW comments preserved.
Copy the orch config draft into the setup route and preserve review notes. Refs: TASK-ORCH-2C
Replace the legacy pool page with the full TASK-ORCH-2G draft. Refs: TASK-ORCH-2G
Populate v2/orchestrators/setup/connect-to-arbitrum.mdx with the Arbitrum RPC setup guide content from the task brief, preserve review notes in MDX-safe form, and add the legacy RPC-stability review note.
Replace the setup publish-offerings page with the on-chain activation guide and allow repo-supported REVIEW comments in MDX-safe validation. Refs: TASK-ORCH-2F
Convert raw REVIEW comments in run-a-pool.mdx to JSX comments so the page parses as valid MDX.
Write the curated orchestrator guides landing page and align internal tooling links with the current tools-and-guides route. Refs: TASK-ORCH-2J
Convert raw HTML REVIEW comments to JSX in live orchestrator pages. Reject raw REVIEW HTML comments in the MDX-safe validator so invalid MDX is caught before publish.
Replace the tooling stub with the orchestrator tools reference for Explorer, Prometheus monitoring, dashboards, and capability tests. Normalize the page frontmatter, convert review markers to JSX comments, and fix the CLI flags internal route.
…tional Mintlify patterns
…pts in script-classifications.json
New structure: Hub, Concepts, Get Started, Build, Guides, Opportunities, Resources Build group includes new sdk-gateway page Adds 30 redirects for all old developer paths Preserves sidebar section (developer-tools, changelog, Resource HUB) — untouched Preserves intentional Mintlify workarounds (empty anchor separator, redirect page)
Refresh the AI pipelines page for the current AI subnet state. Refs: TASK-ORCH-2H
# Conflicts: # docs-index.json
* [create-pull-request] automated change * fix(governance): use shared yaml loader Use the repo YAML fallback loader in the governance auditor and docs index utils so clean docs-v2 worktrees can run STEP-02 verification without a local tools install. * chore(codex): release stale 808 lock Expand this branch's task scope to codex lock metadata and mark the superseded 808 governance replay lock as released so codex pre-push validation can pass for the docs-v2 direct push. * chore(governance): record repair preflight drift Refresh STEP-03 governance repair reports for current docs-v2. Dry-run now yields 265 safe repairs with zero judgement autofills and zero pipeline drops, so fix mode remains blocked pending revalidation. * feat(config): [SE-NAV-FIX] add navigation exclusions config for intentional Mintlify patterns * fix(governance): [BLOCK-D-REPAIR] register 16 undeclared archive scripts in script-classifications.json * feat(enforce): [REPAIR-00f] add governance check to PR gate * docs(internal): align governance pipeline page with repo truth * fix(governance): keep sync PRs refreshable --------- Co-authored-by: DeveloperAlly <12529822+DeveloperAlly@users.noreply.github.com> Co-authored-by: test-runner <tests@example.com>
Align tracked docs, navigation, governance, and generated artifacts with the current repository state while intentionally leaving untracked incoming work out of scope. allow-deletions: true
Revert the live mintlify[bot] commit block on docs-v2 before docs-v2-dev recovery and merge reconciliation. human-override: no-verify override-note: explicit user instruction in chat to use no-verify for rollback and follow-up recovery commits
Replace only docs.json redirects in docs-v2-dev with the restored docs-v2 redirect set before branch reconciliation. human-override: no-verify override-note: explicit user instruction in chat to use no-verify for rollback and follow-up recovery commits
Reconcile docs.json after the docs-v2 rollback and align the Resource HUB redirect surface with scoped navigation during docs-v2-dev branch reconciliation.
Generated-By: mintlify-agent Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Updated the description and titles for clarity and consistency. Changed references from 'Arbitrum Mainnet' to 'Arbitrum One'.
# Conflicts:
Updated contract addresses to reflect the change from Arbitrum Mainnet to Arbitrum One and modified the last verified date.
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
1 participant
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.
Summary
docs-v2history so GitHub can compare it directly againstmaindocs-v2-devlineage by anchoringdocs-v2to bothmainanddocs-v2-devdocs-v2 -> maina real PR pathDetails
docs-v2now points to merge commit67b8093dmain(de6026f6)docs-v2-devstate (fd2a2eb2)backup-docs-v2-pre-main-history-20260317Validation
git merge-base origin/main origin/docs-v2now returnsde6026f6git merge-base --is-ancestor origin/main origin/docs-v2passesdocs-v2 -> mainis restored