Skip to content

Merge Docs-V2 to Main#824

Open
DeveloperAlly wants to merge 472 commits intomainfrom
docs-v2
Open

Merge Docs-V2 to Main#824
DeveloperAlly wants to merge 472 commits intomainfrom
docs-v2

Conversation

@DeveloperAlly
Copy link
Collaborator

Summary

  • repair docs-v2 history so GitHub can compare it directly against main
  • preserve the current docs-v2-dev lineage by anchoring docs-v2 to both main and docs-v2-dev
  • keep the current docs tree intact while making docs-v2 -> main a real PR path

Details

  • docs-v2 now points to merge commit 67b8093d
  • first parent: main (de6026f6)
  • second parent: current local docs-v2-dev state (fd2a2eb2)
  • backup tag for the previous production tip: backup-docs-v2-pre-main-history-20260317

Validation

  • git merge-base origin/main origin/docs-v2 now returns de6026f6
  • git merge-base --is-ancestor origin/main origin/docs-v2 passes
  • remote compare path docs-v2 -> main is restored

test-runner and others added 30 commits March 10, 2026 06:42
human-override: no-verify
override-note: User requested committing and pushing the REPAIR-00 governance changes to docs-v2 despite unrelated local-lock and generated-banner checks blocking a normal commit in this divergent worktree.
… page

Regenerate the required docs-guide and script indexes and sync script classification coverage so the current docs-v2 pre-commit and generated-banner gates pass with the new governance pipeline page.
Canonicalize the GPU Nodes route tree under v2/orchestrators, add the required stub pages, update repo-wide path consumers, and refresh generated indexes/link maps.
# Conflicts:
#	docs-guide/component-registry.json
#	docs-guide/component-usage-map.json
#	snippets/components/content/code.jsx
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.
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.
Archives (→ _archive/):
- developer-guide, journey-mapping, index (generated)
- developer-journey (3-path version, superseded by developer-path)
- ai-pipelines/(overview, byoc, comfystream, model-support) — superseded by new drafts
- ai-inference-on-livepeer/ (old folder)
- quickstart hub stubs
- guides-and-resources/ (stale duplicate)
- developer-tools/gateways + external-tooling (empty stubs)
- developer-platforms/, livepeer-real-time-video/, moved-to-about/, building-on-livepeer/
- x-deprecated/, x-unstaged/, partner-integrations

Moves (git mv, content preserved):
- developer-path → developer-journey (+ TODO note)
- quickstart/ai/ai-jobs → get-started/ai-quickstart
- quickstart/video/transcoding-jobs → get-started/transcoding-quickstart
- ai-pipelines/workload-fit → build/workload-fit
- guides-and-tools/ → guides/
- builder-opportunities/ → opportunities/
- technical-references/ → resources/

No files deleted.
Moved from _incoming/ staging (8 new draft files):
- concepts/(developer-stack, ai-on-livepeer, running-a-gateway, oss-stack)
- get-started/comfystream-quickstart
- build/(comfystream, byoc, model-support)

New stubs (4):
- concepts/video-on-livepeer
- get-started/(setup-paths, video-quickstart)
- build/sdk-gateway (SDK / alternative gateway client path — research from Gateways consolidation)

No files deleted.
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.
Move the about-orchestrators pages into v2/orchestrators/concepts,
split Hub and Concepts navigation, and update generated route
artifacts plus internal references to the new paths.
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.
Generated-By: mintlify-agent

Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Add or improve frontmatter description metadata across all v1 navigation
pages to ensure every page has an accurate, plain-language summary between
50-160 characters for search engine optimization.
Generated-By: mintlify-agent

Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
…ss docs (#829)

Generated-By: mintlify-agent

Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Generated-By: mintlify-agent

Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
…ocs (#831)

Generated-By: mintlify-agent

Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Generated-By: mintlify-agent

Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
#834)

Generated-By: mintlify-agent

Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
…836)

Generated-By: mintlify-agent

Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
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
Generated-By: mintlify-agent

Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
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