@enterpriseai/cli 3.19.2 → 3.19.4

package/resources/gofer/instruction-templates/base/claude-base.md

@@ -5,3 +5,21 @@ See @AGENTS.md for project conventions, commands, and code style. {{workflow}}
 ## Gofer Pipeline
 
 {{goferCommands}}
+
+## Support after an unresolved EAI error
+
+After an `eai` command fails, run `eai errors explain <code-or-reason> --format json`.
+Follow its diagnostics, approval requirements, and fixes once. Stop at its retry limit.
+If the command still fails, prepare a report with
+`eai support --source harness --tool <current-tool> --format json`.
+Use `codex`, `claude`, `vscode`, `grok`, or `antigravity` for `<current-tool>`.
+This command previews the locally redacted bundle in a noninteractive harness.
+Show the person the bundle summary and ask for explicit consent in the chat.
+Only after they approve that bundle, repeat the command with `--yes --no-open` and give them the returned link.
+If the bundle changes, show it again and ask for fresh consent. Never assume consent or run `--yes` automatically.
+Keep secrets, tokens, raw logs, and local `.env` values out of the chat.
+The CLI creates the draft; the AI never calls the support API itself.
+Report content stays in the draft body. The Support link fragment carries only its id and token.
+If sign-in is unavailable, give the person the plain Support page link returned by the CLI.
+In the welcome reply, say: If anything fails, say "get help" or type `eai support`; I can prepare a report for you to approve.
+If the person asks for help with a silent failure, start with the same report preview.

package/resources/gofer/instruction-templates/base/copilot-base.md

@@ -24,3 +24,21 @@
 - **Simplicity First**: Make every change as simple as possible. Impact minimal code.
 - **No Laziness**: Find root causes. No temporary fixes. Senior developer standards.
 - **Minimal Impact**: Changes should only touch what's necessary. Avoid introducing bugs.
+
+## Support after an unresolved EAI error
+
+After an `eai` command fails, run `eai errors explain <code-or-reason> --format json`.
+Follow its diagnostics, approval requirements, and fixes once. Stop at its retry limit.
+If the command still fails, prepare a report with
+`eai support --source harness --tool <current-tool> --format json`.
+Use `codex`, `claude`, `vscode`, `grok`, or `antigravity` for `<current-tool>`.
+This command previews the locally redacted bundle in a noninteractive harness.
+Show the person the bundle summary and ask for explicit consent in the chat.
+Only after they approve that bundle, repeat the command with `--yes --no-open` and give them the returned link.
+If the bundle changes, show it again and ask for fresh consent. Never assume consent or run `--yes` automatically.
+Keep secrets, tokens, raw logs, and local `.env` values out of the chat.
+The CLI creates the draft; the AI never calls the support API itself.
+Report content stays in the draft body. The Support link fragment carries only its id and token.
+If sign-in is unavailable, give the person the plain Support page link returned by the CLI.
+In the welcome reply, say: If anything fails, say "get help" or type `eai support`; I can prepare a report for you to approve.
+If the person asks for help with a silent failure, start with the same report preview.

package/resources/gofer/instruction-templates/gofer/gofer-claude.md

@@ -5,3 +5,7 @@ gate. Before EAI readiness, app delivery continues directly, while clear non-app
 work asks once before skipping EAI tenant/app setup. Checkpointing, branding,
 tests, stakeholder communications, first-run setup, and diagnostics remain
 internal contracts routed by Gofer. Artifacts go to `.specify/specs/{feature}/`.
+
+For unresolved CLI errors and requests to "get help", follow
+`.specify/references/platform/eai-support.md`. Prepare reports with `eai support`
+and require the person's explicit consent before sending the previewed bundle.

package/resources/gofer/node-scripts/generate-commands.mjs

@@ -439,6 +439,26 @@ For app delivery, make EAI Platform choices for the business user.
 15. Ask the user only for material business, security, cost, deployment, destructive, or external-system decisions.`;
 }
 
+function buildSupportReportContract() {
+  return `## Support after an unresolved EAI error
+
+After an \`eai\` command fails, run \`eai errors explain <code-or-reason> --format json\`.
+Follow its diagnostics, approval requirements, and fixes once. Stop at its retry limit.
+If the command still fails, prepare a report with
+\`eai support --source harness --tool <current-tool> --format json\`.
+Use \`codex\`, \`claude\`, \`vscode\`, \`grok\`, or \`antigravity\` for \`<current-tool>\`.
+This command previews the locally redacted bundle in a noninteractive harness.
+Show the person the bundle summary and ask for explicit consent in the chat.
+Only after they approve that bundle, repeat the command with \`--yes --no-open\` and give them the returned link.
+If the bundle changes, show it again and ask for fresh consent. Never assume consent or run \`--yes\` automatically.
+Keep secrets, tokens, raw logs, and local \`.env\` values out of the chat.
+The CLI creates the draft; the AI never calls the support API itself.
+Report content stays in the draft body. The Support link fragment carries only its id and token.
+If sign-in is unavailable, give the person the plain Support page link returned by the CLI.
+In the welcome reply, say: If anything fails, say "get help" or type \`eai support\`; I can prepare a report for you to approve.
+If the person asks for help with a silent failure, start with the same report preview.`;
+}
+
 function buildPublicEntrypointMarkdown(entry, stages, host) {
   if (entry.name === 'eai-update') {
     return buildEaiUpdateEntrypointMarkdown(host);
@@ -526,6 +546,8 @@ ${buildAuthAccessDecisionContract()}
 7. After any \`eai\` error, run \`eai errors explain <code-or-reason> --format json\` when available before guessing remediation.
 8. Do not write tokens, secrets, private workspace IDs, Entra/CIAM authority tenant IDs, or local \`.env\` values into artifacts.
 
+${buildSupportReportContract()}
+
 ${buildVerifiedEaiCliCommandContract()}
 
 ${buildEaiPlatformDecisionSection()}
@@ -553,6 +575,8 @@ The EAI Platform supports every step with secure data, identity, multi-tenancy,
 
 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.”**
 
+If anything fails, say "get help" or type \`eai support\`; I can prepare a report for you to approve.
+
 **First question:** What process would you like to improve, or what would you like the application to help people do?
 \`\`\`
 
@@ -1917,6 +1941,8 @@ ${buildAlwaysEaiSection()}
 
 ${buildVerifiedEaiCliCommandContract()}
 
+${buildSupportReportContract()}
+
 ## EAI CLI Discovery And Recovery
 
 - Classify work before EAI readiness: app delivery continues directly; clear non-app work asks once before skipping EAI workspace/app setup.

package/resources/gofer/references/platform/eai-support.md

@@ -0,0 +1,19 @@
+# EAI support reports
+
+## Support after an unresolved EAI error
+
+After an `eai` command fails, run `eai errors explain <code-or-reason> --format json`.
+Follow its diagnostics, approval requirements, and fixes once. Stop at its retry limit.
+If the command still fails, prepare a report with
+`eai support --source harness --tool <current-tool> --format json`.
+Use `codex`, `claude`, `vscode`, `grok`, or `antigravity` for `<current-tool>`.
+This command previews the locally redacted bundle in a noninteractive harness.
+Show the person the bundle summary and ask for explicit consent in the chat.
+Only after they approve that bundle, repeat the command with `--yes --no-open` and give them the returned link.
+If the bundle changes, show it again and ask for fresh consent. Never assume consent or run `--yes` automatically.
+Keep secrets, tokens, raw logs, and local `.env` values out of the chat.
+The CLI creates the draft; the AI never calls the support API itself.
+Report content stays in the draft body. The Support link fragment carries only its id and token.
+If sign-in is unavailable, give the person the plain Support page link returned by the CLI.
+In the welcome reply, say: If anything fails, say "get help" or type `eai support`; I can prepare a report for you to approve.
+If the person asks for help with a silent failure, start with the same report preview.

package/resources/gofer/specify-commands/0_gofer_start.md

@@ -333,6 +333,24 @@ in `{FEATURE_DIR}/service-fit-matrix.md` as `unavailable without new platform
 work`, `operator_required`, or `upgrade_required`. Do not silently replace it
 with an unrelated non-EAI stack.
 
+## Support after an unresolved EAI error
+
+After an `eai` command fails, run `eai errors explain <code-or-reason> --format json`.
+Follow its diagnostics, approval requirements, and fixes once. Stop at its retry limit.
+If the command still fails, prepare a report with
+`eai support --source harness --tool <current-tool> --format json`.
+Use `codex`, `claude`, `vscode`, `grok`, or `antigravity` for `<current-tool>`.
+This command previews the locally redacted bundle in a noninteractive harness.
+Show the person the bundle summary and ask for explicit consent in the chat.
+Only after they approve that bundle, repeat the command with `--yes --no-open` and give them the returned link.
+If the bundle changes, show it again and ask for fresh consent. Never assume consent or run `--yes` automatically.
+Keep secrets, tokens, raw logs, and local `.env` values out of the chat.
+The CLI creates the draft; the AI never calls the support API itself.
+Report content stays in the draft body. The Support link fragment carries only its id and token.
+If sign-in is unavailable, give the person the plain Support page link returned by the CLI.
+In the welcome reply, say: If anything fails, say "get help" or type `eai support`; I can prepare a report for you to approve.
+If the person asks for help with a silent failure, start with the same report preview.
+
 ### EAI Preflight Checks
 
 1. **Classify the build path**

package/resources/gofer/specify-commands/gofer_eai_first_run.md

@@ -340,6 +340,24 @@ Specifically note whether the installed CLI advertises the commands needed for:
 - AI-agent guidance via `eai agent guide`
 - error recovery guidance via `eai errors explain`
 
+## Support after an unresolved EAI error
+
+After an `eai` command fails, run `eai errors explain <code-or-reason> --format json`.
+Follow its diagnostics, approval requirements, and fixes once. Stop at its retry limit.
+If the command still fails, prepare a report with
+`eai support --source harness --tool <current-tool> --format json`.
+Use `codex`, `claude`, `vscode`, `grok`, or `antigravity` for `<current-tool>`.
+This command previews the locally redacted bundle in a noninteractive harness.
+Show the person the bundle summary and ask for explicit consent in the chat.
+Only after they approve that bundle, repeat the command with `--yes --no-open` and give them the returned link.
+If the bundle changes, show it again and ask for fresh consent. Never assume consent or run `--yes` automatically.
+Keep secrets, tokens, raw logs, and local `.env` values out of the chat.
+The CLI creates the draft; the AI never calls the support API itself.
+Report content stays in the draft body. The Support link fragment carries only its id and token.
+If sign-in is unavailable, give the person the plain Support page link returned by the CLI.
+In the welcome reply, say: If anything fails, say "get help" or type `eai support`; I can prepare a report for you to approve.
+If the person asks for help with a silent failure, start with the same report preview.
+
 ## Step 5: Login, Workspace, And Account Readiness
 
 Run:

package/resources/gofer/system-skills/eai/SKILL.md

@@ -185,6 +185,24 @@ Confirm the sign-in method separately: EAI sign-in or client SSO through EAI. Ve
 7. After any `eai` error, run `eai errors explain <code-or-reason> --format json` when available before guessing remediation.
 8. Do not write tokens, secrets, private workspace IDs, Entra/CIAM authority tenant IDs, or local `.env` values into artifacts.
 
+## Support after an unresolved EAI error
+
+After an `eai` command fails, run `eai errors explain <code-or-reason> --format json`.
+Follow its diagnostics, approval requirements, and fixes once. Stop at its retry limit.
+If the command still fails, prepare a report with
+`eai support --source harness --tool <current-tool> --format json`.
+Use `codex`, `claude`, `vscode`, `grok`, or `antigravity` for `<current-tool>`.
+This command previews the locally redacted bundle in a noninteractive harness.
+Show the person the bundle summary and ask for explicit consent in the chat.
+Only after they approve that bundle, repeat the command with `--yes --no-open` and give them the returned link.
+If the bundle changes, show it again and ask for fresh consent. Never assume consent or run `--yes` automatically.
+Keep secrets, tokens, raw logs, and local `.env` values out of the chat.
+The CLI creates the draft; the AI never calls the support API itself.
+Report content stays in the draft body. The Support link fragment carries only its id and token.
+If sign-in is unavailable, give the person the plain Support page link returned by the CLI.
+In the welcome reply, say: If anything fails, say "get help" or type `eai support`; I can prepare a report for you to approve.
+If the person asks for help with a silent failure, start with the same report preview.
+
 ## Verified EAI CLI Command Contract
 
 Do not invent, guess, or complete EAI CLI commands from memory.
@@ -277,6 +295,8 @@ The EAI Platform supports every step with secure data, identity, multi-tenancy,
 
 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.”**
 
+If anything fails, say "get help" or type `eai support`; I can prepare a report for you to approve.
+
 **First question:** What process would you like to improve, or what would you like the application to help people do?
 ```
 

package/resources/linked-sources.json

@@ -7,8 +7,8 @@
   },
   "appTemplate": {
     "repo": "https://github.com/eai-support/eai-app-template.git",
-    "version": "v1.0.10",
-    "commit": "3a117e2cd12ef2375a80ebdc6031927b2da2be78",
+    "version": "v1.0.13",
+    "commit": "623c4430ba017b8da5b36e84e2fcafd819f79169",
     "packageLockSha256": "5b04e0be44ef93a817e4dc5076914d0f0684712b41155ee2934ce42f184df415",
     "enterpriseRegistry": "https://enterpriseaigroup.github.io/enterpriseai-packages/registry",
     "enterprisePackageFingerprint": "3286fdf91d6a25a55a4d84de21bf5c592bcf11abffb96dc2be90e93414eeb646",