docs(install): migrate plugin-architecture-v2 link to git.moleculesai.app (#37) #1

claude-ceo-assistant · 2026-05-07T06:52:41Z

2026-05-07 06:52:41 +00:00

What

Single actionable edit: README:119 Markdown link reference [plugin-architecture-v2] migrated from github.com/Molecule-AI/internal/blob/main/... (suspended GitHub org) to git.moleculesai.app/molecule-ai/internal/src/branch/main/... (canonical Gitea, path-shape adjusted from GitHub's /blob/<branch>/ to Gitea's /src/branch/<branch>/).

Files NOT touched in this PR

Line	Why left	Reference
78	Code-block narrative describing current go.mod state. Will be migrated as part of cross-repo Go-module PR.	Per Q5 + parked Go-module follow-up.
118	Historical PR ref `[molecule-core#1957]` — audit trail for one of the 119 historical issue/PR refs.	Per Q3 confirm + #38 section B3.

Plugin-* sync direction

This is one of 21 plugin-* repos. Sync direction (standalone Gitea vs monorepo _plugins/<>/) discussed in internal#42; my read is that the standalone Gitea repo is post-bulk-flip canonical → PRs against it are correct. If a future "import from local vendored copy" sync runs, this edit needs to reverse-sync into ~/molecules-org/_plugins/molecule-ai-plugin-gh-identity/README.md first.

DoD waivers

Pure-docs PR. No tests / security / observation / back-compat / migration / version bump.

Hostile self-review (3 weakest spots)

The destination internal/product/plugin-architecture-v2.md is in a private repo. Anonymous Gitea visitors get a private-repo response. Accepted because: same applies on GitHub originally; logged-in users see the doc; non-logged-in users are not the target audience for an internal architecture doc.
Link rot risk if product/plugin-architecture-v2.md is renamed. Same risk existed on github with /blob/main/; not worse.
README:78 narrative still references suspended GitHub. Code-blocks describing the monorepo state are intentionally consistent with current go.mod; correct fix is the cross-repo Go-module PR. Leaving here would create a half-state mismatch with code.

Refs: internal#37, internal#38, internal#42.

## What Single actionable edit: README:119 Markdown link reference `[plugin-architecture-v2]` migrated from `github.com/Molecule-AI/internal/blob/main/...` (suspended GitHub org) to `git.moleculesai.app/molecule-ai/internal/src/branch/main/...` (canonical Gitea, path-shape adjusted from GitHub's `/blob/<branch>/` to Gitea's `/src/branch/<branch>/`). ## Files NOT touched in this PR | Line | Why left | Reference | |---|---|---| | 78 | Code-block narrative describing current go.mod state. Will be migrated as part of cross-repo Go-module PR. | Per Q5 + parked Go-module follow-up. | | 118 | Historical PR ref `[molecule-core#1957]` — audit trail for one of the 119 historical issue/PR refs. | Per Q3 confirm + #38 section B3. | ## Plugin-* sync direction This is one of 21 plugin-* repos. Sync direction (standalone Gitea vs monorepo `_plugins/<>/`) discussed in [internal#42](https://git.moleculesai.app/molecule-ai/internal/issues/42); my read is that the standalone Gitea repo is post-bulk-flip canonical → PRs against it are correct. If a future "import from local vendored copy" sync runs, this edit needs to reverse-sync into `~/molecules-org/_plugins/molecule-ai-plugin-gh-identity/README.md` first. ## DoD waivers Pure-docs PR. No tests / security / observation / back-compat / migration / version bump. ## Hostile self-review (3 weakest spots) 1. **The destination `internal/product/plugin-architecture-v2.md` is in a private repo.** Anonymous Gitea visitors get a private-repo response. *Accepted because*: same applies on GitHub originally; logged-in users see the doc; non-logged-in users are not the target audience for an internal architecture doc. 2. **Link rot risk if `product/plugin-architecture-v2.md` is renamed.** Same risk existed on github with `/blob/main/`; not worse. 3. **README:78 narrative still references suspended GitHub.** Code-blocks describing the monorepo state are intentionally consistent with current go.mod; correct fix is the cross-repo Go-module PR. Leaving here would create a half-state mismatch with code. Refs: [internal#37](https://git.moleculesai.app/molecule-ai/internal/issues/37), [internal#38](https://git.moleculesai.app/molecule-ai/internal/issues/38), [internal#42](https://git.moleculesai.app/molecule-ai/internal/issues/42).

claude-ceo-assistant added 1 commit 2026-05-07 06:52:41 +00:00

docs(install): migrate plugin-architecture-v2 link to git.moleculesai.app (#37 )

CI / Shellcheck + wrapper tests (pull_request) Successful in 1m21s

Details

CI / Go build + test + vet (pull_request) Successful in 9m43s

Details

51bf44f094

One actionable edit: README:119 link reference [plugin-architecture-v2]
points at github.com/Molecule-AI/internal (suspended) → migrated to
git.moleculesai.app/molecule-ai/internal/src/branch/main/...
(Gitea path-shape).

LEFT AS-IS:
- README:78 — Go module path `github.com/Molecule-AI/molecule-ai-plugin-
  gh-identity` inside a code block describing current go.mod state.
  Updates with the cross-repo Go-module migration PR.
- README:118 — historical PR ref to molecule-core#1957. Per Q3 (kept
  as audit trail for the 119 historical issue/PR cross-refs).

Refs: molecule-ai/internal#37, molecule-ai/internal#38, molecule-ai/internal#42

claude-ceo-assistant merged commit 81602fcac9 into main

2026-05-07 09:24:06 +00:00

claude-ceo-assistant referenced this issue from a commit

2026-05-07 09:24:06 +00:00

Merge pull request 'docs(install): migrate plugin-architecture-v2 link to git.moleculesai.app (#37)' (#1) from fix/install-path-gitea into main

Sign in to join this conversation.

No reviewers

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: molecule-ai/molecule-ai-plugin-gh-identity#1