Synchronize Nx Forge with the latest Forge toolchain and proxied CLI interfaces

[tbinna]

What to build

Create and run a repeatable compatibility-synchronization workflow that keeps Nx Forge aligned with the latest stable Atlassian Forge toolchain. The workflow must reconcile Forge dependencies, every Nx Forge executor that proxies a Forge CLI command, its tests, and its public documentation as one vertical maintenance slice.

The executor contract remains typed. Do not introduce generic raw argument forwarding or declare @forge/cli as a peer dependency. Nx Forge should develop and test against the latest stable Forge CLI while allowing consumers to choose their own CLI version; Forge remains responsible for rejecting flags unsupported by the consumer's installed version.

Create the workflow as an explicit cross-agent skill named sync-nx-forge-compatibility. Keep one canonical skill under .agents/skills/ for Codex and expose that same directory to Claude Code from .claude/skills/ without duplicating its instructions.

Acceptance criteria

• sync-nx-forge-compatibility can be explicitly invoked by both Codex and Claude Code and has a single maintained source of instructions.
• The skill resolves current stable Forge package versions from authoritative sources at runtime rather than caching version numbers in its instructions.
• The skill updates and verifies @forge/cli, @forge/manifest, and any other Forge dependencies owned or generated by Nx Forge, including the lockfile and relevant runtime requirements.
• The skill discovers every executor that proxies a Forge CLI command and compares its typed interface and command construction with current official Forge documentation and the installed CLI's <command> --help output.
• Every upstream option is classified as typed and supported, intentionally transformed, intentionally unsupported with a rationale, or missing and implemented as part of the synchronization.
• The current deploy, register, and tunnel interfaces are synchronized with the latest stable Forge CLI after Deploy executor drops --approve and --major-version options #204 is complete.
• forge deploy --tag is evaluated as a distinct pre-built-artifact workflow. If it remains intentionally unsupported by the specialized deploy executor, users are directed to the generic Forge executor and any required prepared-manifest precondition is documented.
• Exact command-argument tests cover every supported proxied option and important transformed option.
• The complete public docs/ site is cross-checked against the plugin executor interfaces so option tables, examples, behavior descriptions, compatibility notes, and intentional omissions are current.
• Generated executor reference content and consumer-facing dependency guidance are updated wherever the synchronization changes behavior or supported versions.
• Supported Node/runtime versions and CI coverage are checked against the latest Forge and Nx requirements, with any necessary compatibility updates included.
• The completed skill is validated in both Codex and Claude Code, and the synchronized repository passes the relevant Nx build, test, lint, and documentation checks.
• No generic Forge argument pass-through or @forge/cli peer dependency is introduced.

Blocked by

• Deploy executor drops --approve and --major-version options #204