[aXenDeveloper]

Adds vitnode generate (alias g) with module, route and service:

• A shared planner holds every create/update in memory, formats it with the
  project's own oxfmt, prints the real diff under --dry-run, re-checks files
  before writing and rolls back a failed batch.
• Sources are read with oxc-parser and edited with span-based insertions, so
  comments, options and the VitNodeApiPlugin contract are preserved.
  Module and route registrations stay explicit; unsupported structures stop
  before writing with exact manual steps.
• Project resolution: the current plugin, --project <name|path>, or the
  only/selected API plugin in the workspace.
• Routes separate file name from HTTP path, refuse method/path collisions,
  return labelled sample data for GET and 501 for unimplemented writes.
• Admin routes require an explicit staff permission, validated against
  permissionStaff; --declare-permission adds it and its AdminCP labels.
• Services are plain factories over explicit dependencies.

Docs: CLI reference plus how-tos for modules, endpoints, admin endpoints
and services.

Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01CnAiFZ3bExobTQrGyYnt3P

[chatgpt-codex-connector]

Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-09T20:39:32.720600Z	7215ff3	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[github-actions]

React Doctor found 12 new issues in 11 files · 12 warnings · score 78 / 100 (Needs work) · 2 fixed · vs canary

12 warnings

scripts/cli/commands/doctor.ts

• ⚠️ L213 await inside a loop async-await-in-loop

scripts/cli/commands/generate.ts

• ⚠️ L604 Independent awaits run sequentially async-parallel
• ⚠️ L605 Sequential independent awaits server-sequential-independent-await

scripts/cli/commands/inspect.ts

• ⚠️ L146 await inside a loop async-await-in-loop

scripts/cli/commands/plugin-validate.ts

• ⚠️ L134 await inside a loop async-await-in-loop

scripts/cli/generate/content-resource.ts

• ⚠️ L238 Array lookup inside a loop js-set-map-lookups

scripts/cli/generate/endpoints.ts

• ⚠️ L287 Array lookup inside a loop js-set-map-lookups

scripts/cli/generate/format.ts

• ⚠️ L101 await inside a loop async-await-in-loop

src/api/modules/admin/ai/routes/update-role-access.route.ts

• ⚠️ L74 await inside a loop async-await-in-loop

src/api/modules/admin/ai/routes/update-translation-sources.route.ts

• ⚠️ L73 await inside a loop async-await-in-loop

src/api/modules/forum/routes/list-forum-stats.route.ts

• ⚠️ L117 Sequential independent awaits server-sequential-independent-await

src/api/modules/forum/routes/list-topic-stats.route.ts

• ⚠️ L72 Sequential independent awaits server-sequential-independent-await

_{Reviewed by React Doctor for commit 7215ff3. See inline comments for fixes.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 78e1327f5f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Quote permission module names in the initial declaration

When a plugin has no permissionStaff yet, generating an admin route with --permission site-notes.can_view --declare-permission inserts permissionStaff: { admin: { site-notes: ["can_view"] } }. Hyphenated module names are explicitly accepted by parsePermission, but this unquoted property is invalid TypeScript, so generation aborts without writing any files. API resources with a hyphenated --permission-module hit the same issue. Use the quoted-key handling already present below when constructing this initial declaration too.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c2daeaa0c1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Reject reserved content admin paths before writing files

For a content resource named create or edit, the generator accepts the name and writes an explicit admin.path ending in that segment. However, resolveAdminPath in packages/vitnode/src/content/define-admin.ts explicitly rejects both endings. The command therefore reports success and registers a definition that throws when imported, preventing the plugin API from loading until the generated code is manually repaired. Validate the derived admin path against the Content Engine's restrictions before applying the plan.

Useful? React with 👍 / 👎.

[github-actions]

React Doctor · react-doctor/async-await-in-loop (warning)

This for…of loop waits before starting the next iteration. If iterations perform independent asynchronous work, consider bounded concurrency; await syntax alone does not establish a speedup.

Fix → Consider concurrent calls only for independent asynchronous work. Shared queues or synchronous work may not benefit. Preserve resource limits, transaction ordering, and failure/cancellation semantics; observe all callback promises.

Docs

[github-actions]

React Doctor · react-doctor/async-parallel (warning)

These 3 sequential await statements run one after another even though they look independent, so the page waits longer than it needs to. Run them together with Promise.all() instead

Fix → Use const [a, b] = await Promise.all([fetchA(), fetchB()]) so independent calls run at the same time

Docs

[github-actions]

React Doctor · react-doctor/server-sequential-independent-await (warning)

This awaited initializer does not read the previous result. If the operations are independent asynchronous work, they may overlap; await syntax alone does not establish a speedup.

Fix → Consider Promise.all([...]) only for independent asynchronous work. Shared queues or synchronous work may not benefit. Preserve resource limits, transaction ordering, and failure/cancellation semantics.

Docs

[github-actions]

React Doctor · react-doctor/async-await-in-loop (warning)

This for…of loop waits before starting the next iteration. If iterations perform independent asynchronous work, consider bounded concurrency; await syntax alone does not establish a speedup.

Fix → Consider concurrent calls only for independent asynchronous work. Shared queues or synchronous work may not benefit. Preserve resource limits, transaction ordering, and failure/cancellation semantics; observe all callback promises.

Docs

[github-actions]

React Doctor · react-doctor/js-set-map-lookups (warning)

This scales poorly because array.includes() inside a loop scans the whole list every time. Use a Set for constant-time lookups.

Fix → Use a Set or Map when you check for the same items over and over. Array.includes/find scans the whole list each time

Docs

[github-actions]

React Doctor · react-doctor/async-await-in-loop (warning)

This for…of loop waits before starting the next iteration. If iterations perform independent asynchronous work, consider bounded concurrency; await syntax alone does not establish a speedup.

Fix → Consider concurrent calls only for independent asynchronous work. Shared queues or synchronous work may not benefit. Preserve resource limits, transaction ordering, and failure/cancellation semantics; observe all callback promises.

Docs

[github-actions]

React Doctor · react-doctor/async-await-in-loop (warning)

This for…of loop waits before starting the next iteration. If iterations perform independent asynchronous work, consider bounded concurrency; await syntax alone does not establish a speedup.

Fix → Consider concurrent calls only for independent asynchronous work. Shared queues or synchronous work may not benefit. Preserve resource limits, transaction ordering, and failure/cancellation semantics; observe all callback promises.

Docs

[github-actions]

React Doctor · react-doctor/async-await-in-loop (warning)

This for…of loop waits before starting the next iteration. If iterations perform independent asynchronous work, consider bounded concurrency; await syntax alone does not establish a speedup.

Fix → Consider concurrent calls only for independent asynchronous work. Shared queues or synchronous work may not benefit. Preserve resource limits, transaction ordering, and failure/cancellation semantics; observe all callback promises.

Docs

[github-actions]

React Doctor · react-doctor/server-sequential-independent-await (warning)

This awaited initializer does not read the previous result. If the operations are independent asynchronous work, they may overlap; await syntax alone does not establish a speedup.

Fix → Consider Promise.all([...]) only for independent asynchronous work. Shared queues or synchronous work may not benefit. Preserve resource limits, transaction ordering, and failure/cancellation semantics.

Docs

[github-actions]

React Doctor · react-doctor/server-sequential-independent-await (warning)

This awaited initializer does not read the previous result. If the operations are independent asynchronous work, they may overlap; await syntax alone does not establish a speedup.

Fix → Consider Promise.all([...]) only for independent asynchronous work. Shared queues or synchronous work may not benefit. Preserve resource limits, transaction ordering, and failure/cancellation semantics.

Docs

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7215ff3849

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Check proposed routes at every mount of a shared module

When a module is mounted under multiple parents, this checks the proposed route only at the logical path supplied to the command, even though planRoute updates the shared module declaration and therefore adds the route at every mount. For example, if a and b both mount notesModule, and b already declares GET /notes/items, generating a/notes/items --method get --path /items succeeds but introduces a collision at /b/notes/items; the existing parent handler shadows the generated handler there. Expand proposed endpoints to every mount of the destination module, or check the complete inventory after planning the registration, before writing files.

Useful? React with 👍 / 👎.