@copado/agentia-cli 0.122.0-alpha.1 → 1.0.0-beta.1

package/dist/lib/setup-templates.js

@@ -1,215 +1,12 @@
-import { QUALITY_GATES_SCRIPT_UNIX, QUALITY_GATES_SCRIPT_WINDOWS } from './local-quality-gates.js';
-export const AGENTIA_GITIGNORE_ENTRY = '.agentia/config.user.json';
-export const AGENTIA_IDEX_GITIGNORE_ENTRY = '.agentia/idex';
-export const AGENTIA_GITIGNORE_ENTRIES = [AGENTIA_GITIGNORE_ENTRY, AGENTIA_IDEX_GITIGNORE_ENTRY];
-export const AGENTIA_AGENTS_START_MARKER = '<!-- agentia:managed:start -->';
-export const AGENTIA_AGENTS_END_MARKER = '<!-- agentia:managed:end -->';
-/** Legacy whole-directory ignores that should be migrated to {@link AGENTIA_GITIGNORE_ENTRY}. */
-export const AGENTIA_DIR_GITIGNORE_ENTRIES = ['.agentia', '.agentia/', '/.agentia', '/.agentia/'];
-export const SAMPLE_QUALITY_GATES_UNIX = `#!/usr/bin/env bash
-set -euo pipefail
-
-# Local Agentia quality gates (macOS / Linux).
-# Edit this script to match your project. Agentia runs it from the repo root during
-# \`agentia cicd work test\` (local by default) and \`agentia cicd work submit\` (unless --skip-local-tests).
-# The script must exit non-zero if any check fails.
-
-echo "## Running Code Analyzer"
-sf code-analyzer run
-
-if [[ -n "\${AGENTIA_APEX_TEST_CLASSES:-}" ]]; then
-  agentia cicd work test apex -t "\${AGENTIA_APEX_TEST_CLASSES}"
-fi
-
-echo "## Running LWC tests"
-npx sfdx-lwc-jest -- # --passWithNoTests
-`;
-export const SAMPLE_QUALITY_GATES_WINDOWS = `@echo off
-setlocal EnableExtensions EnableDelayedExpansion
-REM Local Agentia quality gates (Windows).
-REM Edit this script to match your project. Agentia runs it from the repo root during
-REM \`agentia cicd work test\` (local by default) and \`agentia cicd work submit\` (unless --skip-local-tests).
-REM The script must exit non-zero if any check fails.
-
-echo ## Running Code Analyzer
-sf code-analyzer run
-if errorlevel 1 exit /b %errorlevel%
-
-if defined AGENTIA_APEX_TEST_CLASSES (
-  agentia cicd work test apex -t "!AGENTIA_APEX_TEST_CLASSES!"
-  if errorlevel 1 exit /b %errorlevel%
-)
-
-echo ## Running LWC tests
-npx sfdx-lwc-jest --
-if errorlevel 1 exit /b %errorlevel%
-`;
-/** Bundled AGENTS.md template (mirrors docs/AGENTS.sample.md). Used when DEFAULT_AGENTS_MD_URL is unset or download fails. */
-export const BUNDLED_AGENTS_MD = `# Agentia CLI for AI Agents
-
-Use Agentia to manage Copado user stories end-to-end: pick work, prepare a git branch, push changes, submit for review, and promote.
-
-**Prefer the Agentia MCP server when it is available.** If tools such as \`agentia_work_list\`, \`agentia_work_set\`, \`agentia_work_commit\`, \`agentia_work_publish\`, and \`agentia_work_submit\` are registered, call those instead of shelling out to the \`agentia\` CLI. Fall back to CLI commands only when MCP is not configured.
-
-When using the CLI, prefer \`--json\` on every command so you can parse structured output instead of terminal tables.
-
-Authentication must already be configured (\`agentia auth set\` / keychain, or local gateway mode). Run from a git repository that is a Copado-managed project.
-
-## Typical workflow
-
-\`\`\`text
-list → get → set → (implement & commit or cloud commit) → publish → submit [--done]
-\`\`\`
-
-| Step | MCP tool (preferred) | CLI fallback | Purpose |
-| --- | --- | --- | --- |
-| 1 | \`agentia_work_list\` (\`assignedToMe: true\`) | \`agentia cicd work list --assigned-to-me --json\` | Show user stories assigned to you |
-| 2 | \`agentia_work_get\` | \`agentia cicd work get [id] --json\` | Read user story details (omit id after \`work set\`) |
-| 3 | \`agentia_work_set\` | \`agentia cicd work set <id> --json\` | Mark in progress and prepare the feature branch |
-| 4 | *(your edits + \`git commit\`)* or \`agentia_work_commit\` | *(your edits + \`git commit\`)* or \`agentia cicd work commit --cloud --json\` | Implement the story or create a Copado cloud metadata commit |
-| 5 | \`agentia_work_publish\` | \`agentia cicd work publish --json\` | Publish local Git commits and register them with Copado |
-| 6 | \`agentia_work_submit\` | \`agentia cicd work submit --json\` | Flag ready for review (pipeline quality gates / validation) |
-| 7 | \`agentia_work_submit\` (\`done: true\` or \`deploy: true\`) | \`agentia cicd work submit --done --json\` | Promote and deploy to the next stage (Copado UI Submit promote) |
-
-Do not skip \`work set\` before coding. Later steps expect a \`feature/<user-story-name>\` branch and a recorded base branch from \`work set\`.
-
----
-
-## Commands
-
-CLI examples below are the fallback when MCP is unavailable. MCP tool names and arguments mirror these commands (camelCase args instead of flags).
-
-### \`agentia cicd work list\`
-
-Show user stories. For “assigned to me”, always use:
-
-\`\`\`sh
-agentia cicd work list --assigned-to-me --json
-\`\`\`
-
-Useful filters: \`--status\`, \`--project-name\`, \`--name\`, \`--owned-by-me\`. Do not combine \`--assigned-to-me\` with \`--owned-by-me\` or \`--assignee-id\`.
-
-### \`agentia cicd work get [id]\`
-
-Read full details for one user story. After \`work set\`, omit the ID to use the active work item:
-
-\`\`\`sh
-agentia cicd work get --json
-agentia cicd work get a0SKC000000CmZ2AU --json
-\`\`\`
-
-Use this before starting work to understand title, status, acceptance criteria, and related fields.
-
-### \`agentia cicd work set <id>\`
-
-Flag the user story as the active work item (in progress) and prepare the correct git branch:
-
-\`\`\`sh
-agentia cicd work set a0SKC000000CmZ2AU --json
-# or by name:
-agentia cicd work set US-0001 --json
-\`\`\`
-
-What it does:
-
-1. Calls Copado to set the work item and resolve the base branch
-2. Requires a **clean tracked working tree** (stash or commit first if dirty)
-3. Fetches \`origin/<base-branch>\`
-4. Creates or checks out \`feature/<user-story-name>\`
-5. Records the last work item ID, name, and base branch for later commands
-
-Optional: \`--base-branch <name>\` overrides the base branch from the API.
-
-After success, stay on that feature branch for all implementation commits.
-
-### \`agentia cicd work publish\`
-
-Publish committed changes to git and register them with Copado:
-
-\`\`\`sh
-agentia cicd work publish --json
-\`\`\`
-
-\`cicd work push\` / \`agentia_work_push\` remain compatibility aliases of this command.
-
-Prerequisites:
-
-- Current branch is \`feature/US-XXXX\` (from \`work set\`)
-- No uncommitted tracked changes (commit first)
-- \`work set\` was run so a base branch is recorded
-
-Locks the tip commit after fetching \`origin/<lastBaseBranch>\` and collecting \`origin/<lastBaseBranch>..HEAD\`, runs \`git push origin <branch>\`, then registers the commits with Copado.
-
-### \`agentia cicd work commit --cloud\`
-
-Create a Copado cloud commit job for selected metadata:
-
-\`\`\`sh
-agentia cicd work commit --cloud --message "Commit AccountService" --metadata-name AccountService --metadata-type ApexClass --metadata-category SFDX --json
-agentia cicd work commit a0SKC000000CmZ2AU --cloud --file commit-request.json --json
-\`\`\`
-
-Use this when the metadata commit should be performed by Copado rather than by local Git. The command preflights the user story, submits the commit request, and waits for the job by default. For bundled metadata with \`SelectiveCommit\`, include \`--selection\` values for the files inside the bundle. MCP uses camelCase fields such as \`metadataName\`, \`metadataType\`, \`metadataCategory\`, \`selection\`, and \`wait\`. For Salesforce metadata, always set \`--metadata-category SFDX\` or MCP \`metadataCategory: "SFDX"\` (maps to change field \`c\`). Without \`c:SFDX\`, Copado SFDX deploy logs "Salesforce changes not found." and skips the deploy.
-
-### \`agentia cicd work test --local\`
-
-Run local project quality gates without submitting:
-
-\`\`\`sh
-agentia cicd work test --local --json
-agentia cicd work test --local --apex-test-classes=MyTest,OtherTest --json
-\`\`\`
-
-If the project root contains \`${QUALITY_GATES_SCRIPT_UNIX}\` (macOS/Linux) or \`${QUALITY_GATES_SCRIPT_WINDOWS}\` (Windows), that script runs and the command stops on failure. If no project script exists, \`work test\` warns, runs the same sample script offered by \`agentia setup\` from a temporary file (then deletes it), and does not write those files into the repository. Only \`--local\` is supported for now. Optional \`--apex-test-classes=class1,class2\` is passed to the script as \`AGENTIA_APEX_TEST_CLASSES\` (MCP: \`apexTestClasses\`). Sample scripts call \`agentia cicd work test apex\` for that Apex step.
-
-### \`agentia cicd work test apex\`
-
-Run named Apex test classes. This is the usual Apex step inside project-root local quality gates (\`${QUALITY_GATES_SCRIPT_UNIX}\` / \`${QUALITY_GATES_SCRIPT_WINDOWS}\`) when those scripts are configured; \`work test\` and \`work submit\` pass \`--apex-test-classes\` into the script as \`AGENTIA_APEX_TEST_CLASSES\`. Invoke it directly for a targeted rerun without the rest of the gates.
-
-\`\`\`sh
-agentia cicd work test apex -t HelloWorldTest --json
-agentia cicd work test apex --apex-test-classes=MyTest,OtherTest -w 10 --json
-\`\`\`
-
-Required \`--apex-test-classes\` (or \`-t\`) is comma-separated. Optional \`--wait\` (or \`-w\`) is minutes and defaults to 60. The command runs \`sf apex run test --class-names <names> -c --json --wait <minutes>\` without a shell. Human output shows the test-run summary on pass, or failing tests with Message and StackTrace on failure. \`--json\` omits Salesforce org and user Ids. MCP: \`agentia_work_test_apex\`.
-
-### \`agentia cicd work submit\`
-
-Flag the user story as ready for review. Runs local project quality gates (when present), then pipeline quality gates and validation:
-
-\`\`\`sh
-agentia cicd work submit --json
-agentia cicd work submit --apex-test-classes=MyTest,OtherTest --json
-agentia cicd work submit --skip-local-tests --json
-agentia cicd work submit --done --json
-agentia cicd work submit --deploy --json
-agentia cicd work submit --done --skip-nested-metadata-detection --json
-\`\`\`
-
-Same branch/clean-tree rules as \`work publish\`. If the project root contains \`${QUALITY_GATES_SCRIPT_UNIX}\` (macOS/Linux) or \`${QUALITY_GATES_SCRIPT_WINDOWS}\` (Windows), that script runs first and submit stops on failure. Unlike \`work test\`, submit does not run stock sample gates when those files are missing. Use \`--apex-test-classes=class1,class2\` to pass Apex test classes to the script as \`AGENTIA_APEX_TEST_CLASSES\` (MCP: \`apexTestClasses\`). Use \`--skip-local-tests\` to skip local gates. After that, submit fetches \`origin/<lastBaseBranch>\` and counts \`origin/<lastBaseBranch>..HEAD\` before checking origin. No commits is an error unless the Story has a \`Data Set - Salesforce\` or \`Data Template - Salesforce\` deployment step. When commits exist, unpushed work is still pushed even if those data steps are present, then submit continues. With \`--done\` or \`--deploy\` (MCP: \`done\` or \`deploy\`), submit matches Copado UI Submit when promoting (validate=false / headless work/done) and honors \`--skip-nested-metadata-detection\`. Prefer \`submit --done\` (or \`--deploy\`) over the compatibility alias \`cicd work done\`.
-
----
-
-## Agent rules
-
-1. **Prefer MCP over CLI.** When Agentia MCP tools are available, use them instead of running \`agentia\` in the shell.
-2. **Discover before acting.** List assigned stories, then \`get\` the chosen ID, then \`set\` before editing files.
-3. **One story, one feature branch.** Do not mix unrelated commits on the same \`feature/US-XXXX\` branch.
-4. **Choose the right commit path.** Use normal \`git add\` / \`git commit\` followed by \`agentia_work_publish\` for local Git work. Use \`agentia_work_commit\` / \`agentia cicd work commit --cloud\` for Copado cloud metadata commits.
-5. **Keep the tree clean** before \`set\`, \`publish\`, and \`submit\`. Those steps fail if tracked changes are pending.
-6. **Prefer structured results.** MCP returns JSON; for CLI, use \`--json\` and do not scrape human table output.
-7. **Order matters.** \`set\` → git commit or cloud commit → \`publish\` when local Git commits exist → \`submit\` (optionally \`--done\`). \`submit\` fetches \`origin/<lastBaseBranch>\` and counts \`origin/<lastBaseBranch>..HEAD\` before checking origin; it auto-publishes only when that feature-only range is non-empty and origin is behind. A Data Set or Data Template deployment step can waive the empty-history error, but not publish validation when commits exist. \`set\` is still required first.
-8. **Confirm intent for \`submit --done\` / \`--deploy\`.** Promotion deploys to the next stage; do not run it unless the user asked to promote/deploy.
-`;
-export function qualityGatesExplanation(bin = 'agentia') {
-    return [
-        'Local quality gates:',
-        `  • ${QUALITY_GATES_SCRIPT_UNIX} runs on macOS/Linux; ${QUALITY_GATES_SCRIPT_WINDOWS} on Windows.`,
-        `  • ${bin} work test runs the platform script from the repo root when present; if it is missing, work test warns and runs the stock setup sample from a temporary file.`,
-        `  • ${bin} work submit runs the platform script from the repo root when present and does not use the stock fallback.`,
-        `  • Use ${bin} work submit --skip-local-tests to bypass them for a single submit.`,
-        '  • Edit the scripts to add or remove checks; they must exit non-zero on failure.',
-        '  • Sample scripts call Salesforce CLI code analyzer, `agentia cicd work test apex` when AGENTIA_APEX_TEST_CLASSES is set, and LWC tests — replace with your project gates.',
-    ].join('\n');
-}
-//# sourceMappingURL=setup-templates.js.map
+import {modules} from './runtime.js';
+const AGENTIA_AGENTS_END_MARKER = modules["setup-templates.js"]["AGENTIA_AGENTS_END_MARKER"]
+const AGENTIA_AGENTS_START_MARKER = modules["setup-templates.js"]["AGENTIA_AGENTS_START_MARKER"]
+const AGENTIA_DIR_GITIGNORE_ENTRIES = modules["setup-templates.js"]["AGENTIA_DIR_GITIGNORE_ENTRIES"]
+const AGENTIA_GITIGNORE_ENTRIES = modules["setup-templates.js"]["AGENTIA_GITIGNORE_ENTRIES"]
+const AGENTIA_GITIGNORE_ENTRY = modules["setup-templates.js"]["AGENTIA_GITIGNORE_ENTRY"]
+const AGENTIA_IDEX_GITIGNORE_ENTRY = modules["setup-templates.js"]["AGENTIA_IDEX_GITIGNORE_ENTRY"]
+const BUNDLED_AGENTS_MD = modules["setup-templates.js"]["BUNDLED_AGENTS_MD"]
+const SAMPLE_QUALITY_GATES_UNIX = modules["setup-templates.js"]["SAMPLE_QUALITY_GATES_UNIX"]
+const SAMPLE_QUALITY_GATES_WINDOWS = modules["setup-templates.js"]["SAMPLE_QUALITY_GATES_WINDOWS"]
+const qualityGatesExplanation = modules["setup-templates.js"]["qualityGatesExplanation"]
+export {AGENTIA_AGENTS_END_MARKER, AGENTIA_AGENTS_START_MARKER, AGENTIA_DIR_GITIGNORE_ENTRIES, AGENTIA_GITIGNORE_ENTRIES, AGENTIA_GITIGNORE_ENTRY, AGENTIA_IDEX_GITIGNORE_ENTRY, BUNDLED_AGENTS_MD, SAMPLE_QUALITY_GATES_UNIX, SAMPLE_QUALITY_GATES_WINDOWS, qualityGatesExplanation};