@codyswann/lisa 2.225.5 → 2.226.1

package/plugins/src/base/skills/lisa-generate-claude-remote-build-script/SKILL.md

@@ -71,9 +71,9 @@ tracker/source, plus the host project's own package manager and tooling — not
    include `JAM_PAT`, `SONAR_TOKEN`, or similar documented substrate env vars
    only as optional secrets, with their acquire/scope comments when the analysis
    supplied them. Never invent values or promote dormant substrates to required.
-   When AWS entries are present, list `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, optional
-   `AWS_SESSION_TOKEN`, and `AWS_DEFAULT_REGION` exactly as the analysis reported. State that these
-   bootstrap credentials are for STS assume-role only; do not emit or recommend `aws sso login`.
+   When AWS entries are present, list only `LISA_AWS_BOOTSTRAP_JSON` as the
+   required secret and `LISA_REMOTE_AGENT=claude` as plain configuration. Never
+   emit standard `AWS_ACCESS_KEY_ID` variables and never recommend `aws sso login`.
 
 3a. **Emit substrate setup snippets.** When the inventory marks an MCP
    `headlessUsable: true` through a documented substrate, render the matching
@@ -91,18 +91,11 @@ tracker/source, plus the host project's own package manager and tooling — not
      transport supports static-token auth. Do not print a Jam `.mcp.json` header snippet because
      Jam's preferred headless substrate is its PAT-authenticated CLI.
 
-3b. **Emit AWS assume-role profile setup.** When the inventory includes `awsProfiles`, write an
-   idempotent `~/.aws/config` block gated on `[ -n "${AWS_ACCESS_KEY_ID:-}" ]`. The generated block
-   must:
-   - `mkdir -p "$HOME/.aws"` and create or append profile stanzas without writing secrets.
-   - Emit one `[profile <name>]` stanza per inventory profile with `role_arn`,
-     `credential_source = Environment`, `region` when present, and `external_id` when present.
-   - Keep regions and ExternalIds as non-secret project metadata from the inventory; never invent
-     account IDs, role names, profile names, regions, or ExternalIds.
-   - Warn and skip profile writing when AWS profile metadata is absent, while still listing the
-     required `AWS_*` env var names in the secret template.
-   - Include a comment that agents should use `aws --profile <name> ...` and must not run
-     `aws sso login` in headless routines.
+3b. **Install the shared AWS bootstrap.** When AWS is present, invoke
+   `/lisa:setup-remote-aws --platform=claude`. Reuse the resulting
+   `scripts/remote-agent-aws-setup.sh`; do not generate a second credential or
+   profile implementation. Add `bash scripts/remote-agent-aws-setup.sh` to the
+   generated cloud setup after required package installation.
 
 4. **Emit the allowlist + gaps notice.** List any custom domains the setup or runtime reaches
    (from `networkAccess.allowlistDomains`, falling back to legacy `allowlistDomains`) that the user
@@ -139,9 +132,9 @@ shape, not a fixed payload):
 #   # Note: GH_TOKEN is for gh CLI only. Raw git uses Claude's connected-GitHub proxy/identity;
 #   # sibling repos reached only by raw git do not need to be in this token scope.
 #   - GH_TOKEN=<token>                          # REQUIRED, github is the active tracker+source
-#   - AWS_ACCESS_KEY_ID=<access-key-id>          # REQUIRED when AWS inventory is active
-#   - AWS_SECRET_ACCESS_KEY=<secret-access-key>  # REQUIRED when AWS inventory is active
-#   - AWS_SESSION_TOKEN=<session-token>          # OPTIONAL for temporary bootstrap creds
+#   - LISA_AWS_BOOTSTRAP_JSON=<complete SecretString> # REQUIRED for AWS
+# PLAIN:
+#   - LISA_REMOTE_AGENT=claude
 # NETWORK: set the environment to Custom and allowlist these non-default domains if not on Full:
 #   - <networkAccess.allowlistDomains, if any>
 set -uo pipefail
@@ -184,13 +177,8 @@ need gh || (sudo apt-get update -y && sudo apt-get install -y gh)
 need jq || sudo apt-get install -y jq
 require gh; require jq
 
-# --- AWS assume-role profiles, when inventory includes awsProfiles ---
-if [ -n "${AWS_ACCESS_KEY_ID:-}" ]; then
-  mkdir -p "$HOME/.aws"
-  # Generated stanzas use credential_source=Environment and contain no secrets.
-  # Agents should run: aws --profile <profile> ...
-  # Do not run aws sso login in headless routines; SSO requires an interactive browser/device flow.
-fi
+# --- AWS assume-role profiles, when AWS inventory is active ---
+bash scripts/remote-agent-aws-setup.sh
 
 # --- optional, only with --include-optional ---
 # (docker / ruby / chromium / etc., guarded)
@@ -213,8 +201,8 @@ to stop are: the analysis could not run, or the `--out` path is not writable.
   raw git/cross-repo clone guidance must not expand the token scope to sibling repositories.
 - Never emit an install for a tool the analysis did not surface, and never install `OPTIONAL` tools
   unless `--include-optional` is set.
-- When AWS is in the inventory, generate environment-backed assume-role profile stanzas from
-  `awsProfiles`; never emit `aws sso login` as a remote setup step.
+- When AWS is in the inventory, reuse `/lisa:setup-remote-aws` and its shared
+  setup script; never emit a second profile implementation or `aws sso login`.
 - Prefer `networkAccess.allowlistDomains` over legacy top-level `allowlistDomains`; never emit
   domains already covered by the routine environment's default Trusted list.
 - Keep the script idempotent and detect-before-install so it is safe to re-run and cache.

package/plugins/src/base/skills/lisa-setup-remote-aws/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: lisa-setup-remote-aws
+description: "Install and validate Lisa's drop-in AWS CLI bootstrap for remote coding environments. Supports Claude, Codex, Cursor, GitHub Copilot, Antigravity on user-managed hosts, OpenCode on user-managed hosts, and future Linux remote agents through one capability contract. Writes no secrets; it installs the common setup script, merges native Cursor/Copilot adapters, and emits exact operator guidance for the selected platform."
+allowed-tools: ["Bash", "Read", "Write", "Glob", "Grep"]
+---
+
+# Set up remote-agent AWS access: $ARGUMENTS
+
+Install the vendor-neutral AWS bootstrap into the current repository.
+
+## Arguments
+
+- `--platform=all|claude|codex|cursor|copilot|agy|opencode` (default `all`)
+- `--project=<path>` (default current working directory)
+- `--secret-name=<name>` (default `remote-agent-credentials`)
+
+## Procedure
+
+1. Resolve the plugin root from `PLUGIN_ROOT`, `CLAUDE_PLUGIN_ROOT`,
+   `CURSOR_PLUGIN_ROOT`, or the installed `@codyswann/lisa/plugins/lisa` package.
+2. Run:
+
+   ```bash
+   node "$PLUGIN_ROOT/scripts/install-remote-agent-aws.mjs" $ARGUMENTS
+   ```
+
+3. Inspect every path returned by the installer. It must install
+   `scripts/remote-agent-aws-setup.sh`; for Cursor it merges
+   `.cursor/environment.json`; for Copilot it creates or merges
+   `.github/workflows/copilot-setup-steps.yml`; and it always writes
+   `docs/remote-agent-aws.md`.
+4. Run `bash -n scripts/remote-agent-aws-setup.sh`.
+5. Never write or request the actual bootstrap SecretString in repository
+   files. Tell the operator to retrieve the `remote-agent-credentials` secret
+   from the shared AWS account and paste its complete SecretString into the
+   platform secret named `LISA_AWS_BOOTSTRAP_JSON`. The default cdkstarter
+   secret name is `remote-agent-credentials`; downstream infrastructure may
+   configure a different name. Pass that name with `--secret-name` so the
+   generated runbook contains the exact retrieval command.
+6. Report the external step that remains: configure that one secret in the
+   remote environment and launch a smoke session.
+
+## Contract
+
+A future coding agent is supported without an AWS change when its remote
+environment provides a Linux shell, a setup/start hook, one opaque secret,
+a writable home directory, and HTTPS access to AWS STS plus the allowed service
+endpoints. Set `LISA_REMOTE_AGENT` to a stable lowercase platform label; it is
+used only as `role_session_name`.
+
+Do not create per-repository or per-agent IAM users. Do not expose the bootstrap
+key through standard `AWS_ACCESS_KEY_ID` variables. Do not add production repair
+permissions; production repair is a human-driven local-workstation workflow.

package/scripts/claude-remote-setup.sh

@@ -23,6 +23,9 @@
 #     #          Pull requests R/W, Metadata R (+Workflows R/W if editing .github/workflows,
 #     #          +Projects R/W if using ProjectV2). Identity needs WRITE+ on the repo.
 #     - GH_TOKEN=<token>        # REQUIRED unless the routine's repo connection already auths `gh`
+#   AWS (when this routine needs account access):
+#     - LISA_AWS_BOOTSTRAP_JSON=<complete remote-agent-credentials SecretString>
+#     - LISA_REMOTE_AGENT=claude
 #   Dormant (set ONLY if you switch .lisa.config.json tracker/source):
 #     - JIRA_API_TOKEN / JIRA_SERVER / JIRA_LOGIN / JIRA_PROJECT   # tracker=jira
 #     - ATLASSIAN_API_TOKEN                                        # source=confluence (8 Confluence scopes)
@@ -70,6 +73,12 @@ fi
 require jq
 require gh
 
+# --- AWS CLI + renewable role profiles (when configured) ---
+if [ -n "${LISA_AWS_BOOTSTRAP_JSON:-}" ]; then
+  LISA_REMOTE_AGENT="${LISA_REMOTE_AGENT:-claude}" \
+    bash scripts/remote-agent-aws-setup.sh
+fi
+
 # --- gitleaks (REQUIRED: pre-commit secret scan) ---
 if ! need gitleaks; then
   echo "Installing gitleaks..."
@@ -133,8 +142,6 @@ if [ "$INCLUDE_OPTIONAL" = "1" ]; then
   # Chromium for Lighthouse/Playwright (heavy — can strain the cache budget)
   npx playwright install chromium || echo "WARN: chromium install failed (optional)"
 
-  # aws CLI (cleanup scripts)
-  need aws || apt_get install -y awscli || echo "WARN: awscli install failed (optional)"
 fi
 
 echo "claude-remote-setup: done."

package/scripts/remote-agent-aws-setup.sh

@@ -0,0 +1,17 @@
+#!/usr/bin/env bash
+# Package-level convenience wrapper. The implementation is authored upstream
+# in plugins/src/base and copied into plugins/lisa by build:plugins.
+
+set -euo pipefail
+
+REPOSITORY_ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
+for candidate in \
+  "$REPOSITORY_ROOT/plugins/lisa/scripts/remote-agent-aws-setup.sh" \
+  "$REPOSITORY_ROOT/plugins/src/base/scripts/remote-agent-aws-setup.sh"; do
+  if [ -x "$candidate" ]; then
+    exec "$candidate" "$@"
+  fi
+done
+
+echo "remote-agent-aws-setup: Lisa plugin script is missing; run bun run build:plugins" >&2
+exit 1