vxcontrol/pentagi
1
0
Fork 0
mirror of https://github.com/vxcontrol/pentagi.git synced 2026-07-21 08:15:23 -04:00
Code Issues 45 Packages Projects Releases 9 Wiki Activity

[PR #293] [MERGED] docs: fix processor wizard integration links #304

New Issue
Closed
opened 2026-06-06 22:10:08 -04:00 by yindo · 0 comments
yindo commented 2026-06-06 22:10:08 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/vxcontrol/pentagi/pull/293
Author: @mason5052
Created: 4/29/2026
Status: ✅ Merged
Merged: 4/30/2026
Merged by: @asdek

Base: feature/next-release ← Head: codex/issue-291-fix-processor-doc-links

📝 Commits (1)

  • 29d5723 docs: fix processor wizard integration links

📊 Changes

1 file changed (+68 additions, -66 deletions)

View changed files

📝 backend/docs/installer/processor-wizard-integration.md (+68 -66)

📄 Description

Summary

  • Updates processor wizard integration docs so links point at the current processor files.
  • Replaces stale ProcessorTerminalModel, terminal_model.go, tea_integration.go, and processor_test.go references with the current ProcessorModel, WithTerminal, message, and test files.
  • Keeps the change docs-only and focused on the broken references reported in #291.

Problem
The installer processor integration guide still referenced files and APIs that no longer exist after the processor refactor. That made the guide hard to follow and left several source links broken.

Solution
I aligned the affected examples and references with the current implementation in processor.go, model.go, state.go, logic.go, logic_test.go, and mock_test.go.

User Impact
Users and contributors following the installer processor guide now land on real files and current examples instead of stale implementation names.

Test Plan

  • Verified the previously mentioned stale references no longer appear.
  • Verified the replacement file paths exist in the current tree.
  • Ran git diff --check.

Closes #291

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/vxcontrol/pentagi/pull/293 **Author:** [@mason5052](https://github.com/mason5052) **Created:** 4/29/2026 **Status:** ✅ Merged **Merged:** 4/30/2026 **Merged by:** [@asdek](https://github.com/asdek) **Base:** `feature/next-release` ← **Head:** `codex/issue-291-fix-processor-doc-links` --- ### 📝 Commits (1) - [`29d5723`](https://github.com/vxcontrol/pentagi/commit/29d57236209857018c87190924822cdea6900030) docs: fix processor wizard integration links ### 📊 Changes **1 file changed** (+68 additions, -66 deletions) <details> <summary>View changed files</summary> 📝 `backend/docs/installer/processor-wizard-integration.md` (+68 -66) </details> ### 📄 Description Summary - Updates processor wizard integration docs so links point at the current processor files. - Replaces stale `ProcessorTerminalModel`, `terminal_model.go`, `tea_integration.go`, and `processor_test.go` references with the current `ProcessorModel`, `WithTerminal`, message, and test files. - Keeps the change docs-only and focused on the broken references reported in #291. Problem The installer processor integration guide still referenced files and APIs that no longer exist after the processor refactor. That made the guide hard to follow and left several source links broken. Solution I aligned the affected examples and references with the current implementation in `processor.go`, `model.go`, `state.go`, `logic.go`, `logic_test.go`, and `mock_test.go`. User Impact Users and contributors following the installer processor guide now land on real files and current examples instead of stale implementation names. Test Plan - Verified the previously mentioned stale references no longer appear. - Verified the replacement file paths exist in the current tree. - Ran `git diff --check`. Closes #291 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-06-06 22:10:08 -04:00
yindo closed this issue 2026-06-06 22:10:08 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: vxcontrol/pentagi#304
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?