/sap-stms

name: sap-stms
description: |
  Moves a released transport request through the landscape (DEV → QAS → PRD) and
  reads its import status / return code via STMS. Four modes: status (default,
  READ-ONLY — a target's import queue, or where a TR sits on the route); logs
  (READ-ONLY — import log + step RC mapped to OK / WARN / ERROR / FATAL); import
  (WRITE, gated — import one released TR; a PRODUCTION target needs a typed-SID
  echo + second confirmation, the most outward-facing action in the toolset; never
  imports an unreleased/NO-GO TR without --force); import-all (WRITE, double-gated,
  off without --all). Missing import authorization → COULD_NOT_IMPORT (never a
  faked success); RC 8/12 = failure even if the queue row looks "done". The import
  VBS is a recording-gated scaffold that fails SAFE — run /sap-gui-probe --record on
  STMS_IMPORT once per release first.
  Prerequisites: active /sap-login GUI session; QA/PROD imports need TMS import
  authorization (status/logs work without it).
argument-hint: "[status] [<TR>] [--system SID] [--route] | logs <TR> --system SID | import <TR> --to SID [--client NNN] [--immediate] [--leave-in-queue] [--force] | import-all --to SID --all  [--connection PROFILE] [--report] [--out PATH]"

SAP STMS - Transport Landscape Movement Skill

You move a **released** transport request through the transport landscape and read its import status. You are READ-ONLY by default; any import is opt-in, gated, and — for a production target — the most strongly-guarded action in the whole toolset. You never import an unreleased or NO-GO TR without `--force`, and you report return codes truthfully (RC 8/12 = failure, even if the row looks done).

Task: $ARGUMENTS

This skill observes `shared/rules/skill_operating_rules.md` (Rule 2 — no unsolicited write). It is the downstream of the release chain: `/sap-transport-readiness` (GO/NO-GO) -> `/sap-se01 release` -> **`/sap-stms`**. `/sap-fix-incident` hands off here after a DEV fix.

---

Shared Resources

| File / token | Path | Purpose | |---|---|---| | `skill_operating_rules.md` | `<SAP_DEV_CORE_SHARED_DIR>\rules\skill_operating_rules.md` | Rule 2 confirmation gate | | `language_independence_rules.md` | `<SAP_DEV_CORE_SHARED_DIR>\rules\language_independence_rules.md` | IDs + `MessageType`, never displayed text | | `settings_lookup.md` | `<SAP_DEV_CORE_SHARED_DIR>\rules\settings_lookup.md` | per-key settings merge; per-connection pin | | `sap_settings_lib.ps1` + `sap_connection_lib.ps1` | `<SAP_DEV_CORE_SHARED_DIR>\scripts\` | `Get-SapWorkDir`, `Get-SapCurrentSessionPath` | | `sap_rfc_lib.ps1` (`%%RFC_LIB_PS1%%`) | `<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_rfc_lib.ps1` | E070 released-status read (RFC) | | `sap_attach_lib.vbs` (`%%ATTACH_LIB_VBS%%`) | `<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_attach_lib.vbs` | `AttachSapSession` for every VBS | | `sap_session_lock.vbs` (`%%SESSION_LOCK_VBS%%`) | `<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_session_lock.vbs` | lock the session around the import write | | `<SKILL_DIR>\references\sap_stms_queue_read.vbs` | *(reader)* | STMS import-queue scrape (read-only) | | `<SKILL_DIR>\references\sap_stms_log_read.vbs` | *(reader)* | import log + RC scrape (read-only) | | `<SKILL_DIR>\references\sap_stms_import.vbs` | *(writer)* | import one TR into a target (gated; recording-calibrated) | | `sap_log_helper.ps1` | `<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_log_helper.ps1` | structured logging |

**Skills referenced**: `/sap-transport-readiness` (optional pre-flight gate), `/sap-se01` (release — the step before import), `/sap-se16n` (manual E070 check).

`<SAP_DEV_CORE_SHARED_DIR>` = `plugins/sap-dev-core/shared` — 3 levels up from `<SKILL_DIR>`, then into `sap-dev-core\shared`.

---

Step 0 — Resolve Work Directory and Settings

powershell -NoProfile -ExecutionPolicy Bypass -Command ". '<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_settings_lib.ps1'; . '<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_connection_lib.ps1'; Write-Output ('WORK_DIR=' + (Get-SapWorkDir)); Write-Output ('PROD_IDS=' + (Get-SapSettingValue 'prod_system_ids' ''))"

Settings reads follow `settings_lookup.md`. Read `prod_system_ids` (optional comma-separated allow-list of production SIDs — see PROD detection in Step 3); saved profiles in `connections.json` whose `environment=PRD` (Rule 0 classification, `safety_policy.md`) count as a PROD signal for their `system_name` too. Set `{WORK_TEMP}` = `{work_dir}\temp`; `{RUN}` = `{WORK_TEMP}\stms\<run>`:

cmd /c if not exist "{WORK_TEMP}\stms" mkdir "{WORK_TEMP}\stms"

Set `{RUN_TEMP}` = the per-run scratch dir (`Get-SapRunTemp` mints + creates `{work_dir}\temp\run_<id>`):

powershell -NoProfile -ExecutionPolicy Bypass -Command ". '<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_connection_lib.ps1'; Write-Output ('RUN_TEMP=' + (Get-SapRunTemp))"

Per the CLAUDE.md "Two-bucket temp model" write this skill's `_run.json` log state under `{RUN_TEMP}` (the working files already live in the per-run `{RUN}`); keep `{WORK_TEMP}` (base) only for `Get-SapCurrentSessionPath -WorkTemp`.

Step 0.5 — Start Logging (best-effort)

powershell -ExecutionPolicy Bypass -File "<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_log_helper.ps1" -Action start -StateFile "{RUN_TEMP}\sap_stms_run.json" -Skill sap-stms -ParamsJson "{}"

---

Step 1 — Mode Dispatch

| First token / flags | Mode | Section | |---|---|---| | `import-all --all` | IMPORT-ALL | Import-All Mode | | `import <TR> --to <SID>` | IMPORT | Import Mode | | `logs <TR> --system <SID>` | LOGS | Logs Mode | | `status` / none | STATUS | Status Mode (default) |

`--to` / `--system` is **mandatory for any write** — there is no default target. Validate the TR format (`<SID>K<digits>`).

---

Status Mode (default, read-only)

S1 — Resolve target(s)

`--system <SID>` for one system; `--route` to walk every system on the TR's transport route. If a `<TR>` is given, also locate where it sits.

S2 — Read the queue (GUI)

Sub