@enterpriseai/cli 3.19.0 → 3.19.1

package/resources/gofer/node-scripts/package-agent-plugin.mjs

@@ -12,6 +12,7 @@ import { promises as fs } from 'node:fs';
 import path from 'node:path';
 import { promisify } from 'node:util';
 import { parseStageCommand } from './parse-stage-command.mjs';
+import { buildAuthAccessDecisionContract, buildEaiHostingAndDeploymentContract, buildContinuationContractSection, buildDeliveryDisciplineContract, buildBlockerMediationContract } from './generate-commands.mjs';
 
 const execFileAsync = promisify(execFile);
 
@@ -29,6 +30,20 @@ const CLAUDE_MARKETPLACE_URL = `${PUBLIC_PLUGIN_URL}/claude-marketplace.json`;
 const CODEX_PLUGIN_MANIFEST_URL = `${PUBLIC_PLUGIN_URL}/codex-plugin.json`;
 const COPILOT_MARKETPLACE_URL = `${PUBLIC_PLUGIN_URL}/copilot-marketplace.json`;
 const GEMINI_EXTENSION_URL = `${PUBLIC_PLUGIN_URL}/gemini-extension.json`;
+const PUBLIC_ENTRYPOINTS = [
+  {
+    stem: 'eai',
+    name: 'eai',
+    title: 'Eai',
+    description: 'Start or continue the EAI delivery pipeline.',
+  },
+  {
+    stem: 'eai-update',
+    name: 'eai-update',
+    title: 'Eai Update',
+    description: 'Install or update EAI Gofer for this AI coding app.',
+  },
+];
 const WINDOWS_FORBIDDEN_SEGMENT_CHARS = new Set(['<', '>', ':', '"', '\\', '|', '?', '*']);
 const WINDOWS_RESERVED_BASENAME = /^(con|prn|aux|nul|com[1-9]|lpt[1-9])(?:\..*)?$/i;
 const WINDOWS_SAFE_RELATIVE_PATH_LIMIT = 240;
@@ -141,7 +156,7 @@ function buildCodexManifest(version, stages, paths = {}) {
     name: PLUGIN_NAME,
     version,
     description:
-      'Gofer core pipeline and helper commands for Claude, Codex, Copilot, Gemini, and VS Code.',
+      'Gofer single-entry delivery command with internal pipeline routing for Claude, Codex, Copilot, Google Antigravity, Grok, and VS Code. Gemini files are legacy compatibility assets only.',
     author: {
       name: 'EAI Tools',
       url: REPOSITORY_URL,
@@ -155,15 +170,17 @@ function buildCodexManifest(version, stages, paths = {}) {
       'codex',
       'claude',
       'copilot',
-      'gemini',
+      'antigravity',
+      'grok',
+      'gemini-legacy',
       'spec-driven-development',
     ],
-    skills: paths.skills ?? `./${UMBRELLA_SKILLS_DIR}/`,
+    skills: paths.skills ?? './skills/',
     interface: {
       displayName: PLUGIN_DISPLAY_NAME,
       shortDescription: 'Spec-driven delivery workflow for agentic coding',
       longDescription:
-        'Run Gofer’s core /0_gofer_start → /6_gofer_validate workflow, with optional bootstrap, save/resume, testing, and communications helpers.',
+        'Run Gofer from one public entrypoint: eai. Gofer routes internally through the full research, specify, plan, tasks, implement, and validate pipeline.',
       developerName: 'EAI Tools',
       category: 'Coding',
       capabilities: ['Interactive', 'Write'],
@@ -171,19 +188,12 @@ function buildCodexManifest(version, stages, paths = {}) {
       defaultPrompt: [
         'Set up my first EAI Platform app with Gofer',
         'Run Gofer research for this feature',
-        'Create a Gofer implementation plan',
         'Validate this branch with Gofer',
       ],
       brandColor: '#145DA0',
       composerIcon: paths.icon ?? `./${PLUGIN_ICON_TARGET}`,
       logo: paths.icon ?? `./${PLUGIN_ICON_TARGET}`,
     },
-    gofer: {
-      stages: stageNames(stages),
-      marketplacePath: PUBLIC_PLUGIN_URL,
-      releaseAsset: buildPublicAgentPluginZipUrl(version),
-      vsixAsset: buildPublicVsixUrl(version),
-    },
   };
 }
 
@@ -191,7 +201,7 @@ function buildGeminiManifest(version, paths = {}) {
   return {
     name: PLUGIN_NAME,
     version,
-    description: 'Gofer core pipeline and helper commands as a Gemini CLI extension',
+    description: 'Legacy Gemini CLI file-format compatibility for EAI Gofer',
     license: 'Apache-2.0',
     commands: paths.commands ?? '.gemini/commands/gofer/',
     gofer: {
@@ -211,7 +221,7 @@ function buildPluginManifest(version, paths = {}) {
     name: PLUGIN_NAME,
     version,
     description:
-      'Gofer core pipeline and helper commands for Claude, Gemini, Codex, Copilot, and VS Code.',
+      'Gofer single-entry delivery command with internal pipeline routing for Claude, Codex, Copilot, Google Antigravity, Grok, and VS Code. Gemini files are legacy compatibility assets only.',
     author: {
       name: 'EAI Tools',
       url: REPOSITORY_URL,
@@ -225,7 +235,9 @@ function buildPluginManifest(version, paths = {}) {
       'claude-code',
       'codex',
       'copilot',
-      'gemini',
+      'antigravity',
+      'grok',
+      'gemini-legacy',
       'spec-driven-development',
     ],
     skills: paths.skills ?? `./${UMBRELLA_SKILLS_DIR}/`,
@@ -239,7 +251,7 @@ function buildClaudeManifest(version, paths = {}) {
     name: PLUGIN_NAME,
     version,
     description:
-      'Gofer core pipeline: /0_gofer_start through /6_gofer_validate, plus optional helper commands.',
+      'Gofer single-entry delivery command with internal pipeline routing.',
     author: {
       name: 'EAI Tools',
       url: REPOSITORY_URL,
@@ -261,7 +273,7 @@ function buildBundleMarketplace(version) {
     },
     metadata: {
       description:
-        'Public Gofer bundle for Claude Code, Gemini CLI, Codex, and Copilot workflows.',
+        'Public Gofer bundle for Claude, Codex, Copilot, Antigravity, Grok, and VS Code. Gemini files are legacy compatibility assets only.',
       version,
     },
     plugins: [
@@ -269,7 +281,7 @@ function buildBundleMarketplace(version) {
         name: PLUGIN_NAME,
         source: './plugins/eai-gofer',
         description:
-          'Gofer core pipeline from /0_gofer_start through /6_gofer_validate, with optional helper commands.',
+          'Gofer single-entry delivery command with internal pipeline routing.',
         version,
         author: {
           name: 'EAI Tools',
@@ -284,7 +296,10 @@ function buildBundleMarketplace(version) {
           'claude',
           'codex',
           'copilot',
-          'gemini',
+          'antigravity',
+          'grok',
+          'vscode',
+          'gemini-legacy',
           'spec-driven-development',
         ],
       },
@@ -301,7 +316,7 @@ function buildRepoMarketplace(version) {
     },
     metadata: {
       description:
-        'Install the Gofer repo marketplace for Claude Code, Gemini CLI, Codex, or Copilot CLI from the public GitHub repository.',
+        'Install Gofer for Claude, Codex, Copilot, Antigravity, Grok, and VS Code from this GitHub repository. Gemini files are legacy compatibility assets only.',
       version,
     },
     plugins: [
@@ -309,7 +324,7 @@ function buildRepoMarketplace(version) {
         name: PLUGIN_NAME,
         source: './plugins/eai-gofer',
         description:
-          'Gofer core pipeline from /0_gofer_start through /6_gofer_validate, with optional helper commands.',
+          'Gofer single-entry delivery command with internal pipeline routing.',
         version,
         author: {
           name: 'EAI Tools',
@@ -325,7 +340,10 @@ function buildRepoMarketplace(version) {
           'claude',
           'codex',
           'copilot',
-          'gemini',
+          'antigravity',
+          'grok',
+          'vscode',
+          'gemini-legacy',
           'spec-driven-development',
         ],
       },
@@ -381,12 +399,367 @@ function buildBundleCodexMarketplace(version) {
   };
 }
 
-function buildUmbrellaSkill(version, stages) {
+function buildAlwaysEaiSection() {
+  return `## Always-On EAI Contract
+<!-- gofer:always-on-eai:start -->
+
+Apply this contract to every request after Gofer is installed for this repo or AI coding app. The user does not need to type \`/eai\`, \`$eai\`, or \`#eai\`.
+
+1. Preserve the user's request. Do not rewrite it or add a visible command prefix.
+2. Treat an explicit \`/eai\`, \`$eai\`, or \`#eai\` prefix as an idempotent request for the same contract.
+3. Apply the Controlled English Contract to every Gofer-authored message and artifact.
+4. Keep the reply short unless the user asks for detail.
+5. Explain the business effect first.
+6. Put technical evidence in durable artifacts.
+7. Do not make the user choose pipeline stages. Select the next internal stage yourself.
+8. Do not repeat workspace setup on every message. Check it before meaningful repo work, tool use, or a pipeline stage.
+9. Keep the update and installation path separate. When the user explicitly asks to update Gofer, run only its maintenance contract.
+10. When a new app conversation starts with \`Get started with EAI\`, send the Required First-Run Response before workspace preflight, EAI readiness, setup, tool calls, or stage routing.
+<!-- gofer:always-on-eai:end -->`;
+}
+
+function buildUserFacingResponseGateSection() {
+  return `## User-Facing Response Gate
+
+Before each user-facing reply, check the draft against these rules:
+
+1. Lead with the business outcome, effect, risk, or decision.
+2. Use concise, simple language.
+3. Include technical detail only when it supports a decision or the user asks for it.
+4. If any check fails, rewrite the reply before sending it.`;
+}
+
+function buildJourneyStateSection() {
+  return `## Journey State
+
+Before routing work, decide where the user is now.
+
+1. Read current feature state from \`.specify/specs/\`, \`goal-ledger.json\`, \`eai-preflight.md\`, \`research.md\`, \`spec.md\`, \`plan.md\`, \`tasks.md\`, validation reports, loop evidence, and handoff notes when they exist.
+2. Classify the request as conversation, research/docs/audit, EAI app delivery, or ambiguous.
+3. For conversation or research/docs/audit, continue the non-app Gofer path after the one required non-app confirmation.
+4. For EAI app delivery or ambiguous app work, continue directly into EAI readiness.
+5. Find the earliest missing pipeline artifact or blocked EAI gate.
+6. Run that internal stage next, then continue forward.
+7. Keep the user-facing explanation at the business level.`;
+}
+
+function buildVerifiedEaiCliCommandContract() {
+  return `## Verified EAI CLI Command Contract
+
+Do not invent, guess, or complete EAI CLI commands from memory.
+
+1. Before you suggest or run an \`eai ...\` command, verify the exact command from the installed CLI.
+2. Start with \`eai --describe\` and use its command map as the source of truth.
+3. For a specific command, run \`eai <command> --help\` or the CLI-described equivalent before using flags, subcommands, or examples.
+4. Use \`eai agent guide --format json\` when the CLI advertises it.
+5. Use \`eai errors explain <code-or-reason> --format json\` after errors when the CLI advertises it.
+6. If the command is not listed or help fails, do not run it. Say the installed EAI CLI does not expose that command, then choose a safe listed command or ask the user to update EAI CLI.
+7. Record the verified command and source in \`eai-preflight.md\`, \`service-fit-matrix.md\`, or the active feature notes before the command changes files or external systems.
+8. For commands that create, deploy, publish, change workspace data or access, change Entra, or spend money, confirm with the user after verification and before execution.
+
+${buildEaiHostingAndDeploymentContract()}`;
+}
+
+function buildEaiPlatformDecisionSection() {
+  return `## EAI Platform Decision Contract
+
+For app delivery, make EAI Platform choices for the business user.
+
+1. Read \`.specify/references/platform/eai-service-patterns.md\`, \`.specify/references/platform/eai-repo-contract.md\`, and \`.specify/references/platform/eai.md\` before architecture or storage decisions.
+2. Run \`eai --describe\` before assuming current CLI syntax.
+3. Run \`eai agent guide --format json\` when the CLI advertises it.
+4. Run \`eai resources schema --format json\` and \`eai workflow readiness --format json\` when advertised and relevant.
+5. Create or update \`.specify/specs/{feature}/service-fit-matrix.md\`.
+6. Prefer the EAI app template, PublicAPI, ResourceAPI, object types, workflows, goals, targets, platform AI services, and workspace identity.
+7. Prefer PostgreSQL for relational, transactional, reporting, and workflow state.
+8. Prefer DocumentDB for flexible JSON documents, nested records, and high-change document models.
+9. Prefer Blob Storage for large files and binary content behind API-mediated access.
+10. Prefer AI Search as a derived search projection, not as the source of record.
+11. Prefer EAI content understanding and document services for classification, extraction, summarization, and Retrieval-Augmented Generation.
+12. Prefer EAI workflows, goals, and targets for approvals, long-running work, service goals, operating targets, and auditable process state.
+13. Use Azure second when the EAI Platform does not yet expose the needed capability.
+14. Use any other platform only as an explicit exception with rationale, owner, expiry, and validation evidence.
+15. Ask the user only for material business, security, cost, deployment, destructive, or external-system decisions.`;
+}
+
+function buildLocalSettingsCleanupContract() {
+  return `## Local Settings Cleanup Contract
+
+After any Gofer install, update, release refresh, or workspace bootstrap:
+
+1. Archive stale Gofer command and skill entries before continuing.
+2. Prefer the repo helper:
+   - \`node .specify/scripts/node/gofer-local-settings-cleanup.mjs --workspace . --apply --json\`
+3. If the repo helper is missing, use the stable plugin bundle helper:
+   - macOS/Linux: \`node ~/plugins/eai-gofer/.specify/scripts/node/gofer-local-settings-cleanup.mjs --workspace . --apply --json\`
+   - Windows: \`node %USERPROFILE%\\plugins\\eai-gofer\\.specify\\scripts\\node\\gofer-local-settings-cleanup.mjs --workspace . --apply --json\`
+4. This cleanup covers old Claude, Codex, Copilot, Gemini, Grok, VS Code, desktop, and CLI command surfaces.
+5. Do not remove the current public \`eai\` entrypoint.
+6. Ask the user to refresh or restart the host command picker only after cleanup completes.`;
+}
+
+function buildAppPreviewRunnerContract() {
+  return `## App Preview Runner Contract
+
+For EAI app delivery, every UI preview must use the repo runner when it exists.
+
+1. Use \`./run.sh dev 3001\` on macOS, Linux, and GitHub Codespaces.
+2. Use \`run.bat dev 3001\` on Windows.
+3. Use a different port only when the feature notes record the reason.
+4. Restart only this app. Before stopping a process, verify its exact checkout, process ID, start time and command, then recheck immediately before stopping it. Never stop another app, an unknown process, or every process on a port. If ownership is uncertain, leave it running and ask the user. Inspect older runners before use; do not run one that kills by port alone.
+5. Do not use direct \`npm run dev\`, \`next dev\`, or package-manager preview commands when \`run.sh\`, \`run.bat\`, or \`run.ps1\` exists.
+6. After every UI-facing change, run:
+   - \`node .specify/scripts/node/gofer-ui-preview.mjs --feature-dir {FEATURE_DIR} --command "./run.sh dev 3001" --open auto --screenshot --change "<change summary>"\`
+7. On Windows, use:
+   - \`node .specify/scripts/node/gofer-ui-preview.mjs --feature-dir {FEATURE_DIR} --command "run.bat dev 3001" --open auto --screenshot --change "<change summary>"\`
+8. If the runner is missing in an EAI app template repo, refresh the template before preview work continues.
+9. Check the exact preview page and the current implemented user journey after each change. A running process, open browser, screenshot alone, error page or dry run is not proof that it works. Say ready to view only after those checks pass. Otherwise explain what is unchecked or failing; do not claim readiness. Record fresh browser and test evidence. Local MVP checks cover only implemented behaviour; do not add future auth or deployment gates. Keep showing clearly labelled drafts without adding approval stops.`;
+}
+
+function buildUmbrellaSkill(version, stages, entry = PUBLIC_ENTRYPOINTS[0]) {
+  if (entry.name === 'eai-update') {
+    return buildEaiUpdateSkill(version);
+  }
+
   const stageList = stages
-    .map((stage) => `- \`${stage.frontmatter.name}\` - ${stage.frontmatter.description}`)
+    .map((stage) => `- \`${stage.stem}\` - ${stage.frontmatter.description}`)
     .join('\n');
 
-  return `---\nname: eai-gofer\ndescription: "Run the public Gofer core pipeline and helper commands in Claude, Gemini, Codex, or Copilot."\n---\n\n# Gofer\n\nVersion: ${version}\n\nUse this skill when the user asks to run, install, update, or understand Gofer without the VS Code extension UI.\n\n## Workspace First\n\nBefore stage work, resolve the repository root and run \`node .specify/scripts/node/gofer-workspace-check.mjs --host auto --json\` when available. If the repo is missing or stale, ask before running \`node .specify/scripts/node/gofer-workspace-bootstrap.mjs --host auto --include-mirrors\`, then resume the original command.\n\n## First EAI Platform App\n\nIf the user is starting a first EAI Platform app, run \`/gofer:eai-first-run\` before \`/0_gofer_start\`. It is allowed to run before \`.specify/\` exists and checks Git, Node.js, npm, the scoped EAI registry, EAI CLI, login, workspace, \`eai init\`, and Gofer scaffold readiness with user approval gates.\n\n## EAI CLI Discovery And Recovery\n\n- Run \`eai whoami\` before Gofer pipeline work and require a valid login plus an active workspace.\n- Run \`eai update --check\` before first EAI platform work when the CLI may be stale.\n- Run \`eai --describe\` before assuming command syntax.\n- If advertised, run \`eai agent guide --format json\` before planning or fixing EAI workflows.\n- After any \`eai\` error, run \`eai errors explain <code-or-reason> --format json\` before guessing remediation.\n- If \`eai errors explain\` is unavailable, match \`.specify/references/platform/eai-error-catalog.yaml\`, run read-only diagnostics before mutating fixes, and stop at the retry or escalation condition.\n- For \`eai user invite\` 5xx or \`EXTERNAL_SERVICE_ERROR\`, check existing members with \`eai user list --workspace <workspace-id> --search <email> --format json\`; use \`eai user role set --workspace <workspace-id> --member-id <member-id> --role tenant-admin --format json\` only after verification and user approval, then tell the app user to sign out and sign back in.\n- Use \`eai publicapi\` only for authorized PublicAPI \`/v4/...\` routes.\n\n## Token And Cost Policy\n\n- Treat \`.specify/memory/gofer-model-policy.yaml\` as the repo-owned source of truth for simple, medium, hard, and arbiter model routing. Run \`/gofer:bootstrap-workspace\` if it is missing.\n- Use the cheapest capable model first. Escalate only when a cheaper pass is low-confidence, contradictory, security-sensitive, release-critical, or blocking quality.\n- Keep raw search, build, and test output out of the main chat context. Write stable findings to \`.specify/specs/{feature}/context-bundle.md\` and continue from summaries.\n- Prefer provider prompt/context caching for stable non-secret prefixes: Gofer scaffold, repository instructions, constitution, repo map, stage contracts, and validation rubric.\n- After large research, planning, implementation, or validation bursts, checkpoint artifacts and compact/clear/resume context when the host supports it.\n\n## Core Pipeline And Helpers\n\n${stageList}\n\n## Stable Local Install Path\n\nInstall or update this plugin by replacing the stable local folder:\n\n\`\`\`text\n~/plugins/eai-gofer\n\`\`\`\n\nThe public release feed is available at:\n\n\`\`\`text\n${PUBLIC_SITE_URL}/releases.json\n\`\`\`\n\nGemini CLI users can also copy the bundled \`.gemini/\` directory into a repository root to activate the same command set there.\n`;
+  return `---
+name: ${entry.name}
+description: "Run Gofer through one public entrypoint while preserving the full internal pipeline."
+---
+
+# ${entry.title}
+
+Version: ${version}
+
+Apply this skill to every request when the plugin is enabled. The user does not need to type a Gofer command. Keep the user's request unchanged and route it through Gofer internally. Use the separate update skill only when the user explicitly asks to install or update Gofer.
+
+${buildContinuationContractSection()}
+
+## Clean Surface Contract
+
+- User-facing command and skill pickers should expose only \`eai\`.
+- Do not ask users to run numbered/helper stage commands such as \`/0_gofer_start\`, \`/1_gofer_research\`, or \`/6_gofer_validate\` unless they explicitly ask for low-level internals.
+- Preserve all Gofer functions by routing internally through the stage contracts in \`.specify/commands/*.md\`.
+
+## Workspace First
+
+Before stage work, resolve the repository root and run \`node .specify/scripts/node/gofer-workspace-check.mjs --host auto --json\` when available. If the repo is missing or stale, ask before running \`node .specify/scripts/node/gofer-workspace-bootstrap.mjs --host auto --include-mirrors\`, then resume the original command.
+
+${buildLocalSettingsCleanupContract()}
+
+${buildAppPreviewRunnerContract()}
+
+## Controlled English Contract
+
+Use ASD-STE100 Simplified Technical English as the target writing standard for all Gofer-authored chat, documents, commands, summaries, PR notes, error guidance, and validation artifacts. ASD-STE100 is copyright and a trademark of ASD; do not bundle the protected ASD dictionary and do not claim ASD certification.
+
+Apply these rules before any user-facing output:
+
+1. Use short sentences. Keep instructions to 20 words or fewer where possible.
+2. Use one action per instruction.
+3. Use active voice. Use passive voice only when the actor is unknown or not important.
+4. Use simple present, simple past, simple future, infinitive, or imperative verb forms.
+5. Use approved project terms and necessary technical nouns only. Define acronyms on first use.
+6. Use direct words. Avoid idioms, marketing adjectives, vague praise, and hedging.
+7. Use vertical lists for complex information.
+8. Put one topic in each paragraph.
+9. For errors, write: what happened, why it matters, what to do next, and the exact safe command when one exists.
+10. Keep raw logs, stack traces, IDs, and secrets out of chat unless the user asks for technical detail.
+
+${buildUserFacingResponseGateSection()}
+
+${buildAlwaysEaiSection()}
+
+## Business-Friendly Progress
+
+- Keep user-facing progress short and business-level by default.
+- Explain what is being connected, changed, checked, or fixed and why it matters.
+- Use \`.specify/specs/{feature}/build-map.md\` as the shared picture of the build when app delivery applies.
+- Keep technical detail, logs, tests, and security evidence in artifacts; show deeper detail when the user asks.
+
+## App vs Non-App Routing
+
+- Classify each request before EAI readiness as EAI app delivery, non-application work, or ambiguous.
+- If the request is EAI app delivery or ambiguous, continue directly into the EAI app delivery path and run EAI readiness.
+- If the request is clearly non-app work, confirm once: **"This looks like non-app work, so I will skip EAI workspace/app setup and continue the Gofer research/docs path. Is that right?"**
+- If the user confirms non-app, do not run \`eai whoami\`, workspace selection, \`eai init\`, or first-run setup. Record the decision and continue the appropriate non-app path.
+- If the user says it is app work, switch to EAI app delivery and run EAI app preflight.
+
+${buildJourneyStateSection()}
+
+## First EAI Platform App
+
+If the user is starting a first EAI Platform app, use the public \`eai\` entrypoint, then follow the first-run/setup contract in \`.specify/commands/gofer_eai_first_run.md\` when it is present. It is allowed before \`.specify/\` exists and checks Git, Node.js, npm, the scoped EAI registry, EAI CLI, login, workspace access, \`eai init\`, and Gofer scaffold readiness with user approval gates. For older CLI versions that do not advertise \`--company-workspace\`, use the \`--company-tenant\` compatibility alias.
+
+## EAI CLI Discovery And Recovery
+
+- Run \`eai whoami\` only for EAI app delivery work or explicit EAI CLI recovery, not for confirmed non-app research/docs/audit/planning.
+- Run \`eai update --check\` before first EAI platform work when the CLI may be stale.
+- Run \`eai --describe\` before assuming command syntax.
+- If advertised, run \`eai agent guide --format json\` before planning or fixing EAI workflows.
+- After any \`eai\` error, run \`eai errors explain <code-or-reason> --format json\` before guessing remediation.
+- If \`eai errors explain\` is unavailable, match \`.specify/references/platform/eai-error-catalog.yaml\`, run read-only diagnostics before mutating fixes, and stop at the retry or escalation condition.
+- For \`eai user invite\` 5xx or \`EXTERNAL_SERVICE_ERROR\`, check existing members with \`eai user list --workspace <workspace-id> --search <email> --format json\`; use \`eai user role set --workspace <workspace-id> --member-id <member-id> --role tenant-admin --format json\` only after verification and user approval. The platform role ID \`tenant-admin\` means workspace admin access. Then tell the app user to sign out and sign back in.
+- Use \`eai publicapi\` only for authorized PublicAPI \`/v4/...\` routes.
+
+${buildVerifiedEaiCliCommandContract()}
+
+${buildEaiPlatformDecisionSection()}
+
+## Token And Cost Policy
+
+- Treat \`.specify/memory/gofer-model-policy.yaml\` as advisory capability, cost, and quality constraints. A fresh signed host receipt and independently verified benchmark evidence select the model. Run the internal bootstrap contract if it is missing.
+- Use the cheapest capable model first. Escalate only when a cheaper pass is low-confidence, contradictory, security-sensitive, release-critical, or blocking quality.
+- Keep raw search, build, and test output out of the main chat context. Write stable findings to \`.specify/specs/{feature}/context-bundle.md\` and continue from summaries.
+- Prefer provider prompt/context caching for stable non-secret prefixes: Gofer scaffold, repository instructions, constitution, repo map, stage contracts, and validation rubric.
+- After large research, planning, implementation, or validation bursts, checkpoint artifacts and compact/clear/resume context when the host supports it.
+
+## Internal Pipeline And Helper Contracts
+
+${stageList}
+
+## Stable Local Install Path
+
+Install or update this plugin by replacing the stable local folder:
+
+\`\`\`text
+~/plugins/eai-gofer
+\`\`\`
+
+The public release feed is available at:
+
+\`\`\`text
+${PUBLIC_SITE_URL}/releases.json
+\`\`\`
+
+Legacy Gemini file-format users can copy the bundled \`.gemini/\` directory into an existing repository. New installations use Google Antigravity and \`agy\`.
+`;
+}
+
+function buildEaiUpdateSkill(version) {
+  return `---
+name: eai-update
+description: "Install or update EAI Gofer for this AI coding app."
+---
+
+# Eai Update
+
+Version: ${version}
+
+Use this skill to install or update the user-level EAI Gofer plugin or extension. It works before a repository has Gofer files.
+
+1. Do not run a workspace check, \`eai init\`, \`eai whoami\`, or a delivery stage.
+2. Use \`.specify/scripts/node/gofer-surface-update.mjs\` from this plugin bundle.
+3. Check status first with \`--action inspect --host <current-host> --json\`.
+4. Show the user the planned user-level install or update. Ask for approval before \`--execute\`.
+5. Run \`--action install\` when Gofer is missing. Run \`--action update\` when it is installed.
+6. After an actual install or update, the helper archives stale Gofer command and skill entries. It also adds a small managed always-on instruction to the selected host. It keeps the current \`eai\` and \`eai-update\` entries. A clean official Codex local marketplace on \`main\` fast-forwards safely. A dirty, non-main, or unrecognised local marketplace remains unchanged and reports that its plugin update is incomplete while it still refreshes the always-on instruction. An unknown Codex marketplace source stops the update without changes.
+7. Update only the current host unless the user explicitly asks for \`--host all\`.
+8. Complete the host reload step from the helper result before saying the update is ready.
+
+Current hosts are \`claude\`, \`codex\`, \`copilot\`, \`antigravity\`, \`grok\`, and \`vscode\`. Gemini is a legacy alias only.
+
+This command archives known stale Gofer entries and replaces only Gofer's managed instruction section. It does not remove unrelated user files or host-managed plugin caches. It does not create \`.specify/\`. After the host update, use \`/eai add or refresh the Gofer scaffold for this repo\` when a repository needs Gofer files.
+${buildBlockerMediationContract()}
+`;
+}
+
+function withTenantContextErrorGuidance(content) {
+  const guidance =
+    '- For `MISSING_TENANT`, `app_token_tenant_context_required`, or "Tenant context required for app tokens" on platform user lookup or membership prerequisites, run `eai errors explain app_token_tenant_context_required --format json`, confirm workspace context, and retry `/v4/platform/tenants/<tenant-id>/...` routes before changing workspace members, Entra, role definitions, databases, or cloud portals.';
+
+  if (content.includes('app_token_tenant_context_required')) {
+    return content;
+  }
+
+  return content.replace(
+    '- Use `eai publicapi` only for authorized PublicAPI `/v4/...` routes.',
+    `${guidance}\n- Use \`eai publicapi\` only for authorized PublicAPI \`/v4/...\` routes.`
+  );
+}
+
+function withEaiAppTemplateGate(content) {
+  const guidance = `## MVP Capability-Based Validation
+
+- Create \`.specify/specs/{feature}/\` before app or operator-tool source work.
+- Classify EAI template readiness as \`not_applicable\`, \`planned\`, \`implemented\`, \`verified\`, or \`blocked\`.
+- For a local MVP with no EAI or authentication capability, record those states as \`not_applicable\` or \`planned\` and continue with local feature validation.
+- Treat \`run.sh\`, \`run.bat\`, and \`run.ps1\` as launch evidence only. They do not prove authentication, EAI access, or deployment readiness.
+- When the feature creates, changes, or validates an EAI Platform integration, run \`node .specify/scripts/node/eai-app-template-readiness.mjs --root . --json\`.
+- A missing checker or any status other than \`ready\` blocks that EAI capability. It does not block unrelated local MVP work.
+- When authentication is implemented or required, verify provider, callback, sign-in, session, protected access, and safe denied access.
+- Record screenshots and local HTTP checks in the feature validation report. A blocked browser check leaves the user journey unverified.
+- If the user changes scope, update the feature artifacts before continuing: \`spec.md\`, \`plan.md\`, \`tasks.md\`, \`traceability.md\`, and validation scope.
+- For a release or deployed claim, create \`release-capability-ledger.md\` and link each accepted requirement to evidence, PR, commit, release branch, and deployed proof.
+- Do not report a release complete or score 100% if a required capability is on an open PR, absent from the release branch, missing traceability, or lacks deployed evidence.
+- Do not accept copied marker files, partial scaffolds, or custom templates as EAI readiness evidence.
+- Confirmed non-app work is exempt from app-only gates.
+
+${buildAuthAccessDecisionContract()}
+
+${buildDeliveryDisciplineContract()}
+
+## EAI App Template Gate
+
+Apply the capability validation rules above before EAI template, workspace, authentication, or deployment work.
+
+`;
+
+  const existingHeading = '## EAI App Template Gate';
+  const existingIndex = content.indexOf(existingHeading);
+  if (existingIndex !== -1) {
+    const nextHeadingIndex = content.indexOf('\n## ', existingIndex + existingHeading.length);
+    const suffix = nextHeadingIndex === -1 ? '' : content.slice(nextHeadingIndex).replace(/^\n+/, '');
+    return suffix
+      ? `${content.slice(0, existingIndex).trimEnd()}\n\n${guidance}\n${suffix}`
+      : `${content.slice(0, existingIndex).trimEnd()}\n\n${guidance}`;
+  }
+
+  return content.replace('## EAI CLI Discovery And Recovery', `${guidance}## EAI CLI Discovery And Recovery`);
+}
+
+function withFirstConversationGuidance(content) {
+  if (content.includes('## First Conversation')) {
+    return content;
+  }
+  const section = `## First Conversation
+
+When this is the first EAI conversation for a new app:
+
+1. Treat \`Get started with EAI\` as the first-run trigger. Ignore capitalization, punctuation, and decorative emoji around the phrase.
+2. Show the following compact orientation once. Do not repeat it after onboarding starts or when existing feature state means the work should resume.
+
+### Required First-Run Response
+
+\`\`\`markdown
+## Welcome to Enterprise AI 👋
+
+I’ll help you improve a process and turn it into a secure enterprise application:
+
+1. **Improve** — understand the opportunity and design the solution.
+2. **Build** — prepare data, add AI, and connect systems.
+3. **Test and deploy** — validate, launch, and share securely.
+4. **Run and measure** — monitor results, costs, activity, and value.
+
+The EAI Platform supports every step with secure data, identity, multi-tenancy, and AI models.
+
+I’ll walk you through the whole process and ask short questions as we go. Tell me what you want me to do, or ask **“What’s next?”**, **“What else can you help with?”**, or **“Show me the admin screen.”**
+
+**First question:** What process would you like to improve, or what would you like the application to help people do?
+\`\`\`
+
+3. After the first answer, ask one short question at a time about the users, current process, desired value, success measures, and material constraints.
+4. Treat \`Show me the admin screen\` as a request for the relevant manual path. Use a verified link from repository or platform context when available. Never invent an admin URL.
+5. Explain EAI capabilities only when they help the next decision. Do not begin with platform architecture or a list of tools.
+6. Use the repository and EAI CLI as sources of truth. Run \`eai --describe\` before assuming command syntax and explain known errors before recovery.
+7. Keep numbered Gofer stages internal. Say what is being learned, designed, built, or checked in business language.
+8. Explain why specification-led delivery improves AI quality: it creates a shared, testable statement of the outcome before code changes multiply.
+9. Pause once for approval of the business specification. Then continue unless a material business, security, cost, deployment, or destructive decision needs approval.
+10. Do not create a GitHub repository, deploy, publish, spend money, or change external systems without the relevant user approval.`;
+  return content.replace('## EAI CLI Discovery And Recovery', `${section}\n\n## EAI CLI Discovery And Recovery`);
 }
 
 function buildWorkspacePreflightSection() {
@@ -400,8 +773,11 @@ Before doing stage/helper work:
    - \`.specify/.gofer-version\`
    - \`.specify/commands/0_gofer_start.md\`
    - \`.specify/templates/spec-template.md\`
+   - \`.specify/templates/build-map-template.md\`
    - \`.specify/templates/loop-contract-template.json\`
    - \`.specify/templates/working-backwards-prfaq-template.md\`
+   - \`.specify/scripts/node/gofer-local-settings-cleanup.mjs\`
+   - \`.specify/scripts/node/gofer-ui-preview.mjs\`
    - \`.specify/scripts/node/gofer-workspace-check.mjs\`
    - \`.specify/scripts/node/gofer-workspace-bootstrap.mjs\`
    - \`.specify/specs/\`
@@ -411,29 +787,80 @@ Before doing stage/helper work:
 4. If the workspace is missing or stale, ask exactly:
    - **"This repo is missing or stale for Gofer. Initialize/update it now?"**
 5. If the user says yes, run the Gofer workspace bootstrap helper and then resume this command from the top.
-6. If the user says no, stop and explain that Gofer stage/helper work depends on the repo-owned scaffold.
+6. After a Gofer install, update, or bootstrap, remove stale local Gofer command entries with:
+   - \`node .specify/scripts/node/gofer-local-settings-cleanup.mjs --workspace . --apply --json\`
+7. For EAI app delivery, use the repo runner for local previews:
+   - macOS, Linux, and GitHub Codespaces: \`./run.sh dev 3001\`
+   - Windows: \`run.bat dev 3001\`
+8. Do not start app previews with direct \`npm run dev\` commands when the repo runner exists.
+9. If the user says no, stop and explain that Gofer stage/helper work depends on the repo-owned scaffold.
 `.trim();
 }
 
-function injectWorkspacePreflight(stage, body) {
-  if (WORKSPACE_PREFLIGHT_EXCLUDED_COMMANDS.has(String(stage.frontmatter.name))) {
+function buildBusinessProgressContractSection() {
+  return `
+## Business-Friendly Progress Contract
+
+- Keep user-facing updates concise and business-level by default.
+- Use ASD-STE100 Simplified Technical English as the target writing standard for all Gofer-authored chat, documents, commands, summaries, PR notes, error guidance, and validation artifacts.
+- Do not bundle the protected ASD dictionary and do not claim ASD certification.
+- Use one action per instruction and keep instructions to 20 words or fewer where possible.
+- Use active voice, simple verb forms, approved project terms, and defined acronyms.
+- Avoid idioms, marketing adjectives, vague praise, and hedging.
+- Explain what is being connected, changed, checked, or fixed and why it matters.
+- For application delivery, create or update \`.specify/specs/{feature}/build-map.md\` from \`.specify/templates/build-map-template.md\` and refer to that map in progress updates.
+- Keep technical detail, logs, tests, and security evidence in durable artifacts; provide that detail when the user asks.
+- Before each user-facing reply, check the business effect, language, and useful technical detail. If any check fails, rewrite the reply before sending it.
+`.trim();
+}
+
+function injectBusinessProgressContract(body) {
+  if (body.includes('## Business-Friendly Progress Contract')) {
     return body;
   }
-  if (body.includes('## Workspace Preflight')) {
-    return body;
+
+  const headingIndex = body.indexOf('## Workspace Preflight');
+  if (headingIndex !== -1) {
+    const nextHeading = body.indexOf('\n## ', headingIndex + 1);
+    if (nextHeading !== -1) {
+      return `${body.slice(0, nextHeading).trimEnd()}\n\n${buildBusinessProgressContractSection()}\n\n${body
+        .slice(nextHeading)
+        .replace(/^\n+/, '')}`;
+    }
   }
 
   const headingMatch = body.match(/^# [^\n]+\n*/);
   if (!headingMatch) {
-    return `${buildWorkspacePreflightSection()}\n\n${body}`;
+    return `${buildBusinessProgressContractSection()}\n\n${body}`;
   }
 
   const insertAt = headingMatch[0].length;
-  return `${body.slice(0, insertAt).trimEnd()}\n\n${buildWorkspacePreflightSection()}\n\n${body
+  return `${body.slice(0, insertAt).trimEnd()}\n\n${buildBusinessProgressContractSection()}\n\n${body
     .slice(insertAt)
     .replace(/^\n+/, '')}`;
 }
 
+function injectWorkspacePreflight(stage, body) {
+  if (WORKSPACE_PREFLIGHT_EXCLUDED_COMMANDS.has(String(stage.frontmatter.name))) {
+    return injectBusinessProgressContract(body);
+  }
+  if (body.includes('## Workspace Preflight')) {
+    return injectBusinessProgressContract(body);
+  }
+
+  const headingMatch = body.match(/^# [^\n]+\n*/);
+  if (!headingMatch) {
+    return injectBusinessProgressContract(`${buildWorkspacePreflightSection()}\n\n${body}`);
+  }
+
+  const insertAt = headingMatch[0].length;
+  return injectBusinessProgressContract(
+    `${body.slice(0, insertAt).trimEnd()}\n\n${buildWorkspacePreflightSection()}\n\n${body
+      .slice(insertAt)
+      .replace(/^\n+/, '')}`
+  );
+}
+
 function buildStageSkill(stage) {
   const body = injectWorkspacePreflight(stage, stage.body.trim());
   return `---\nname: ${stage.frontmatter.name}\ndescription: ${yamlString(stage.frontmatter.description)}\n---\n\n${body}\n`;
@@ -444,11 +871,11 @@ function buildPluginReadmeBase(version) {
 
 Version: ${version}
 
-This package is the portable Claude, Gemini, Codex, and Copilot workflow layer for Gofer. It is released beside the VS Code extension, but it does not replace the VSIX UI, status views, updater, or language-server features.
+This package is the portable Claude, Codex, Copilot, Google Antigravity, Grok, and VS Code workflow layer for Gofer. Gemini files remain only for legacy compatibility. It is released beside the VS Code extension, but it does not replace the VSIX UI, status views, updater, or language-server features.
 
 ## Public Sources
 
-Use the public GitHub repository as the install source for Claude Code, Codex, Copilot CLI, and Gemini CLI:
+Use the public GitHub repository as the install source for Claude Code, Codex, Copilot CLI, Google Antigravity, Grok, and VS Code:
 
 \`\`\`text
 ${REPOSITORY_URL}
@@ -473,11 +900,13 @@ That host publishes:
 
 ## First EAI Platform App
 
-Run \`/gofer:eai-first-run\` before \`/0_gofer_start\` when a new user, machine, repo, workspace, or EAI app template is not ready. The command is allowed to run before \`.specify/\` exists. It checks Git, Node.js, npm, EAI CLI, registry, \`eai update --check\`, \`eai --describe\`, \`eai agent guide --format json\` when advertised, login, workspace, \`eai init <project-name> --skip-prompts --company-workspace <active-workspace-id>\`, Gofer scaffold readiness, and \`eai errors explain <code-or-reason> --format json\` for recovery across macOS, Linux, Windows, and GitHub Codespaces.
+Start with \`/eai\`, \`#eai\`, or \`$eai\` depending on the host. Gofer first classifies the request. If it is EAI app delivery or ambiguous, Gofer continues directly to EAI readiness and routes internally to the first-run setup contract when a new user, machine, repo, workspace, or EAI app template is not ready. If it is clearly non-app work, Gofer asks once before skipping EAI workspace/app setup and continuing the relevant research, documentation, audit, migration, or planning path. The setup path is allowed before \`.specify/\` exists. It checks Git, Node.js, npm, EAI CLI, registry, \`eai update --check\`, \`eai --describe\`, \`eai agent guide --format json\` when advertised, login, workspace access, \`eai init <project-name> --skip-prompts --company-workspace <active-workspace-id>\`, Gofer scaffold readiness, and \`eai errors explain <code-or-reason> --format json\` for recovery across macOS, Linux, Windows, and GitHub Codespaces. For older CLI versions that do not advertise \`--company-workspace\`, use the \`--company-tenant\` compatibility alias.
+
+Gofer does not invent EAI CLI commands. It verifies command paths and flags with \`eai --describe\` and command-specific \`--help\` before suggesting or running them. If the installed CLI does not list a command, Gofer does not run it.
 
-For EAI errors, Gofer expects agents to run live EAI guidance first, use \`.specify/references/platform/eai-error-catalog.yaml\` as fallback, run read-only diagnostics before mutating fixes, and stop at the retry/escalation condition. For \`eai user invite\` 5xx or \`EXTERNAL_SERVICE_ERROR\`, check existing members with \`eai user list --workspace <workspace-id> --search <email> --format json\`; use \`eai user role set --workspace <workspace-id> --member-id <member-id> --role tenant-admin --format json\` only after verification and user approval.
+For EAI errors, Gofer expects agents to run live EAI guidance first, use \`.specify/references/platform/eai-error-catalog.yaml\` as fallback, run read-only diagnostics before mutating fixes, and stop at the retry/escalation condition. For \`eai user invite\` 5xx or \`EXTERNAL_SERVICE_ERROR\`, check existing members with \`eai user list --workspace <workspace-id> --search <email> --format json\`; use \`eai user role set --workspace <workspace-id> --member-id <member-id> --role tenant-admin --format json\` only after verification and user approval. The platform role ID \`tenant-admin\` grants workspace admin access. For \`MISSING_TENANT\`, \`app_token_tenant_context_required\`, or "Tenant context required for app tokens" on platform user lookup or membership prerequisites, run \`eai errors explain app_token_tenant_context_required --format json\`, confirm workspace context, and retry \`/v4/platform/tenants/<tenant-id>/...\` routes before changing workspace members, Entra, role definitions, databases, or cloud portals.
 
-If \`/0_gofer_start\` is unknown in a new repo, install or update this plugin first, then run \`/gofer:eai-first-run\`.
+If \`/eai\` is unknown in a new repo, install or update this plugin first, then refresh/restart the host command picker.
 
 ## App-Native Surfaces And Repo Scripts
 
@@ -485,28 +914,70 @@ Gofer keeps repo-owned scripts and canonical command files as the source of trut
 
 | Surface | Best entry point | Repo-owned files used |
 | ------- | ---------------- | --------------------- |
-| Codex App / Codex IDE | Umbrella \`eai-gofer\` plugin skill plus repo \`.agents/skills\` when a workspace is open | \`AGENTS.md\`, \`.agents/skills/\`, \`.specify/scripts/\`, \`.vscode/mcp.json\` |
-| GitHub Copilot app / VS Code agent mode | Custom Gofer agents and one umbrella skill, not a duplicate slash-command list | \`.github/agents/\`, \`.github/skills/\`, \`.github/prompts/\`, \`.github/instructions/\`, \`.vscode/mcp.json\` |
-| Claude Code app | Plugin umbrella skill for discovery; repo slash commands remain the fast command path | \`.claude/skills/\`, \`.claude/commands/\`, \`.claude/agents/\`, \`.specify/scripts/\` |
-| Gemini CLI / Gemini Code Assist | Gemini extension commands and workspace MCP/customization when available | \`.gemini/\`, \`.specify/scripts/\`, \`.vscode/mcp.json\` |
+| Codex App / Codex IDE | \`eai\` plugin skill when a workspace is open | \`AGENTS.md\`, \`.agents/skills/\`, \`.specify/scripts/\` |
+| GitHub Copilot app / VS Code agent mode | \`#eai\`, plus custom Gofer agents where supported | \`.github/agents/\`, \`.github/skills/\`, \`.github/prompts/\`, \`.github/instructions/\` |
+| Claude Code app | \`/eai\` plugin/repo command | \`.claude/skills/\`, \`.claude/commands/\`, \`.claude/agents/\`, \`.specify/scripts/\` |
+| Legacy Gemini file format | Existing compatibility command only | \`.gemini/\`, \`.specify/scripts/\` |
+| Grok Build | Ask Grok to use the EAI skill | \`.grok/skills/\`, \`.specify/scripts/\` |
+
+The clean UX rule is: users see only \`eai\`; Gofer keeps numbered stages and helpers as internal contracts under \`.specify/commands/\`.
+
+This lightweight plugin does not include a compiled MCP server. The VS Code extension supplies and configures that runtime separately. Repository skills do not require that optional connection.
+
+## Update Cleanup
+
+After each install or update, archive stale Gofer commands and settings:
+
+\`\`\`bash
+node .specify/scripts/node/gofer-local-settings-cleanup.mjs --workspace . --apply --json
+\`\`\`
+
+If the repo helper is not present yet, run the helper from the stable plugin bundle:
+
+\`\`\`bash
+node ~/plugins/eai-gofer/.specify/scripts/node/gofer-local-settings-cleanup.mjs --workspace . --apply --json
+\`\`\`
+
+Windows:
+
+\`\`\`bat
+node %USERPROFILE%\\plugins\\eai-gofer\\.specify\\scripts\\node\\gofer-local-settings-cleanup.mjs --workspace . --apply --json
+\`\`\`
+
+Then refresh or restart the host command picker.
+
+## Local App Preview Runner
+
+For EAI app delivery, start previews through the repo runner:
+
+\`\`\`bash
+./run.sh dev 3001
+\`\`\`
 
-The clean UX rule is: use plain numbered stage commands in initialized repos, and use app/plugin skills for setup, diagnostics, and routing when those stage commands are not loaded yet.
+Windows:
+
+\`\`\`bat
+run.bat dev 3001
+\`\`\`
+
+The runner stops any process on the selected port before it restarts the app.
+Agents should not use direct \`npm run dev\` commands when the runner exists.
 
 ## Core Pipeline
 
-| Stage | Command | Main output |
+| Stage | Internal contract | Main output |
 | ----- | ------- | ----------- |
-| Gofer Start | \`/0_gofer_start\` | Full pipeline kickoff |
-| Research | \`/1_gofer_research\` | \`research.md\` |
-| Specify | \`/2_gofer_specify\` | \`spec.md\` |
-| Plan | \`/3_gofer_plan\` | \`plan.md\`, \`data-model.md\`, \`contracts/\` |
-| Tasks | \`/4_gofer_tasks\` | \`tasks.md\`, \`traceability.md\`, \`issues.md\` |
-| Implement | \`/5_gofer_implement\` | Code and doc changes |
-| Validate | \`/6_gofer_validate\` | Validation artifacts and final review evidence |
+| Gofer Start | \`.specify/commands/0_gofer_start.md\` | Full pipeline kickoff |
+| Research | \`.specify/commands/1_gofer_research.md\` | \`research.md\` |
+| Specify | \`.specify/commands/2_gofer_specify.md\` | \`spec.md\` |
+| Plan | \`.specify/commands/3_gofer_plan.md\` | \`plan.md\`, \`data-model.md\`, \`contracts/\` |
+| Tasks | \`.specify/commands/4_gofer_tasks.md\` | \`tasks.md\`, \`traceability.md\`, \`issues.md\` |
+| Implement | \`.specify/commands/5_gofer_implement.md\` | Code and doc changes |
+| Validate | \`.specify/commands/6_gofer_validate.md\` | Validation artifacts and final review evidence |
 
-\`/6_gofer_validate\` is the terminal quality gate. It includes the final engineering review loop and replaces the old standalone review stage in the core pipeline.
+The internal validation contract is the terminal quality gate. It includes the final engineering review loop and replaces the old standalone review stage in the core pipeline.
 
-Optional helpers like \`/0a_problem_validation\`, \`/7_gofer_save\`, \`/8_gofer_branding\`, \`/9_gofer_tests\`, \`/7a_stakeholder_comms\`, \`/gofer:check-workspace\`, \`/gofer:bootstrap-workspace\`, and \`/gofer:eai-first-run\` remain available outside the core 0-6 stage sequence.
+Optional helpers like problem validation, save, branding, tests, stakeholder comms, workspace checks, bootstrap, and EAI first-run remain available as internal contracts and can be routed by \`gofer\` when needed.
 
 ## Distribution Modes
 
@@ -515,7 +986,7 @@ Optional helpers like \`/0a_problem_validation\`, \`/7_gofer_save\`, \`/8_gofer_
 | Claude Code | \`claude plugin marketplace add ${REPOSITORY_URL} --scope user --sparse .claude-plugin --sparse plugins/eai-gofer\` then \`claude plugin install eai-gofer@eai-gofer --scope user\` | Unzip to \`~/plugins/eai-gofer\`, then \`claude plugin marketplace add ~/plugins/eai-gofer --scope user\` |
 | Codex | \`codex plugin marketplace add ${REPOSITORY_URL} --sparse .agents/plugins --sparse plugins/eai-gofer\` then \`codex plugin add eai-gofer@eai-gofer\` | Unzip to \`~/plugins/eai-gofer\`, then \`codex plugin marketplace add ~/plugins/eai-gofer\` |
 | GitHub Copilot CLI | \`copilot plugin marketplace add ${REPOSITORY_URL}\` then \`copilot plugin install eai-gofer@eai-gofer\` | Unzip to \`~/plugins/eai-gofer\`, then \`copilot plugin marketplace add ~/plugins/eai-gofer\` |
-| Gemini CLI | \`gemini extensions install ${REPOSITORY_URL} --auto-update\` | Unzip to \`~/plugins/eai-gofer\`, then \`gemini extensions install ~/plugins/eai-gofer\` |
+| Google Antigravity | \`agy plugin install ${REPOSITORY_URL}\` | Start a new Antigravity session after installation |
 
 ## Download And Replace The Local Bundle Folder
 
@@ -532,6 +1003,17 @@ curl -fsSL ${buildLatestPublicAgentPluginZipUrl()} -o /tmp/eai-gofer-agent-plugi
 
 rm -rf ~/plugins/eai-gofer
 unzip /tmp/eai-gofer-agent-plugin-latest.zip -d ~/plugins
+node ~/plugins/eai-gofer/.specify/scripts/node/gofer-local-settings-cleanup.mjs --workspace . --apply --json
+\`\`\`
+
+Windows PowerShell:
+
+\`\`\`powershell
+Invoke-WebRequest ${buildLatestPublicAgentPluginZipUrl()} -OutFile "$env:TEMP\\eai-gofer-agent-plugin-latest.zip"
+
+Remove-Item "$env:USERPROFILE\\plugins\\eai-gofer" -Recurse -Force -ErrorAction SilentlyContinue
+Expand-Archive "$env:TEMP\\eai-gofer-agent-plugin-latest.zip" "$env:USERPROFILE\\plugins" -Force
+node "$env:USERPROFILE\\plugins\\eai-gofer\\.specify\\scripts\\node\\gofer-local-settings-cleanup.mjs" --workspace . --apply --json
 \`\`\`
 
 ## Claude Code
@@ -566,7 +1048,7 @@ codex plugin marketplace add ~/plugins/eai-gofer
 codex plugin add eai-gofer@eai-gofer
 \`\`\`
 
-The Codex plugin keeps the slash-command stage entrypoints as the primary user surface. The plugin skill registry only exposes the umbrella \`eai-gofer\` skill so Codex does not show both \`/0_gofer_start\` and \`eai-gofer:0_gofer_start\` for every stage.
+The Codex plugin exposes only \`eai\` as the user-facing skill. The numbered stage contracts remain bundled under \`.specify/commands/\` so the public skill can route through the full pipeline without cluttering the picker.
 
 ## Copilot CLI
 
@@ -584,19 +1066,11 @@ copilot plugin marketplace add ~/plugins/eai-gofer
 copilot plugin install eai-gofer@eai-gofer
 \`\`\`
 
-## Gemini CLI
-
-Recommended public install:
-
-\`\`\`bash
-gemini extensions install ${REPOSITORY_URL} --auto-update
-\`\`\`
+## Legacy Gemini File-Format Compatibility
 
-Downloaded bundle install:
+Existing Gemini file-format repositories can retain the generated \`.gemini/\` files. New installation and update actions use Google Antigravity and \`agy\`.
 
-\`\`\`bash
-gemini extensions install ~/plugins/eai-gofer
-\`\`\`
+Do not identify Gemini as a current Gofer host in new documentation or metadata.
 `;
 }
 
@@ -612,10 +1086,10 @@ After bootstrap, each repository gets a user-owned model policy at:
 \`\`\`
 
 The shipped default is copied from \`.specify/templates/gofer-model-policy.yaml\`
-and is not overwritten by bootstrap. Use it to tune simple, medium, hard, and
-arbiter model routes for Claude, Codex/OpenAI, Gemini, and Copilot. Copilot
-defaults to \`Auto\` for simple/default work because exact model availability is
-controlled by the Copilot client, plan, and organization policy.
+and is not overwritten by bootstrap. Use it only to constrain cost, quality, and
+capability classes. Fresh signed host receipts and independent benchmark evidence
+select the model for Claude, Codex/OpenAI, Google Antigravity, Copilot, Grok,
+and VS Code. No static provider default qualifies a model for execution.
 `;
 }
 
@@ -789,21 +1263,29 @@ async function writePluginFolder(pluginRoot, root, version, stages) {
     buildBundleCodexMarketplace(version)
   );
 
-  await writeText(path.join(pluginRoot, 'skills', 'eai-gofer', 'SKILL.md'), buildUmbrellaSkill(version, stages));
-  await writeText(
-    path.join(pluginRoot, UMBRELLA_SKILLS_DIR, 'eai-gofer', 'SKILL.md'),
-    buildUmbrellaSkill(version, stages)
-  );
-  for (const stage of stages) {
-    await writeText(path.join(pluginRoot, 'skills', stage.stem, 'SKILL.md'), buildStageSkill(stage));
+  for (const entry of PUBLIC_ENTRYPOINTS) {
+    const skill = withFirstConversationGuidance(
+      withEaiAppTemplateGate(withTenantContextErrorGuidance(buildUmbrellaSkill(version, stages, entry)))
+    );
+    await writeText(path.join(pluginRoot, 'skills', entry.stem, 'SKILL.md'), skill);
+    await writeText(path.join(pluginRoot, UMBRELLA_SKILLS_DIR, entry.stem, 'SKILL.md'), skill);
   }
+  await copyIfExistsAs(
+    root,
+    '.claude/skills/gofer-documentation',
+    path.join(UMBRELLA_SKILLS_DIR, 'gofer-documentation'),
+    pluginRoot
+  );
 
   await writeText(path.join(pluginRoot, 'README.md'), buildPluginReadme(version));
   await writeText(path.join(pluginRoot, '.eai-gofer-plugin-version'), `${version}\n${GENERATED_MARKER}\n`);
 
   const copiedResources = [
     '.specify/commands',
+    '.specify/config',
+    '.specify/contracts',
     '.specify/references',
+    '.specify/schemas',
     '.specify/templates',
     '.specify/scripts/bash',
     '.specify/scripts/node',
@@ -813,8 +1295,9 @@ async function writePluginFolder(pluginRoot, root, version, stages) {
     '.github/agents',
     '.github/skills',
     '.claude/skills',
+    '.claude-plugin/hooks',
     '.gemini',
-    '.vscode/mcp.json',
+    '.grok',
     'AGENTS.md',
     'LICENSE',
     'NOTICE',
@@ -847,7 +1330,7 @@ async function syncRepoManifests(root, version, stages, stagedPluginRoot) {
   await writeJson(
     path.join(root, '.codex-plugin', 'plugin.json'),
     buildCodexManifest(version, stages, {
-      skills: `./${UMBRELLA_SKILLS_DIR}/`,
+      skills: './skills/',
       icon: './assets/eai-gofer-icon.png',
     })
   );
@@ -875,16 +1358,25 @@ async function syncRepoManifests(root, version, stages, stagedPluginRoot) {
   await writeJson(
     path.join(root, '.claude-plugin', 'plugin.json'),
     buildClaudeManifest(version, {
-      skills: './.agents/skills/',
+      skills: `./${UMBRELLA_SKILLS_DIR}/`,
     })
   );
   await writeJson(path.join(root, '.claude-plugin', 'marketplace.json'), buildRepoMarketplace(version));
   await writeJson(path.join(root, '.gemini', 'extension.json'), buildGeminiManifest(version));
   await writeJson(path.join(root, 'gemini-extension.json'), buildGeminiManifest(version));
-  await writeText(
-    path.join(root, UMBRELLA_SKILLS_DIR, 'eai-gofer', 'SKILL.md'),
-    buildUmbrellaSkill(version, stages)
-  );
+  for (const staleName of ['eai-gofer', 'gofer']) {
+    await fs.rm(path.join(root, UMBRELLA_SKILLS_DIR, staleName), { recursive: true, force: true });
+    await fs.rm(path.join(root, 'skills', staleName), { recursive: true, force: true });
+  }
+  for (const entry of PUBLIC_ENTRYPOINTS) {
+    const rootUmbrellaSkill = entry.name === 'eai'
+      ? withFirstConversationGuidance(
+          withEaiAppTemplateGate(withTenantContextErrorGuidance(buildUmbrellaSkill(version, stages, entry)))
+        )
+      : buildUmbrellaSkill(version, stages, entry);
+    await writeText(path.join(root, UMBRELLA_SKILLS_DIR, entry.stem, 'SKILL.md'), rootUmbrellaSkill);
+    await writeText(path.join(root, 'skills', entry.stem, 'SKILL.md'), rootUmbrellaSkill);
+  }
 
   const iconSource = path.join(root, PLUGIN_ICON_SOURCE);
   const iconTarget = path.join(root, PLUGIN_ICON_TARGET);