Skip to content

docs: mark LoopForge Local as legacy - #1068

Merged
Robert0622 merged 1 commit into
mainfrom
codex/docs-local-legacy
Nov 18, 2026
Merged

Robert0622 merged 1 commit into
mainfrom
codex/docs-local-legacy

Conversation

@Robert0622

Copy link
Copy Markdown
Collaborator

What changed

The project READMEs currently advertise LoopForge Local as a quick-start option. Mark it as legacy and give readers the path for either continuing an existing Local workflow or using platform projects and SOPs from CodeBuddy.

  • Move Local installation examples to the guides and pin them to a published version.
  • Document how to retain Local artifacts, resume in-progress work, and connect CodeBuddy to an existing LoopForge instance over MCP.
  • Describe current capabilities in the READMEs and guides. Keep maintenance dates and platform SOP export in roadmap planning.

Scope

  • Documentation only

Compatibility

The existing Classic and Portable commands still apply to their respective installations. The guides explain how to keep using the published version for the installed host.

Validation

  • Passed git diff --check.
  • Passed python3 scripts/check-public.py against the five changed documents.
  • Checked all six added links and cross-checked the steps against the platform's CodeBuddy configuration and MCP API reference.
  • Runtime suites and live CodeBuddy/MCP testing were not run for this documentation change.

Safety

  • The change contains public documentation only.
  • User files and unrelated changes are preserved.

@cocofhu cocofhu left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Robert0622
Robert0622 merged commit 451d38c into main Nov 18, 2026
16 checks passed
@Robert0622
Robert0622 deleted the codex/docs-local-legacy branch November 18, 2026 17:52
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.

2 participants