/sap-dev-status

name: sap-dev-status
description: |
  Read-only status report for the sap-dev-init artefacts: transport
  request, package, function group, the wrapper FM
  Z_GENERIC_RFC_WRAPPER_TBL plus its DDIC parameter structure /
  table type, and the ZCMRUPDATE_ADDON_TABLE utility program.
  Queries via RFC (TLIBG, TDEVC, TFDIR, DD02L, DD40L, PROGDIR, E070,
  TADIR) and emits one parseable line per artefact plus a summary
  STATUS line.
  Auto-invokable as a pre-flight from any sap-dev skill — exit code
  0 = healthy, 1 = gaps, 2 = RFC failure, 3 = config mismatch (anchor
  gate — destructive callers must refuse).
  Pure read-only; never modifies the SAP system.
  Prerequisites: SAP NCo 3.1 (32-bit, .NET 4.0) in GAC.
argument-hint: "[--quiet]"

SAP Dev Environment Status Skill

You report on the health of the artefacts `/sap-dev-init` is responsible for. Designed to run in well under a second over RFC, so other skills can call it as a pre-flight.

Task: $ARGUMENTS

---

Shared Resources

| File | Token | Purpose | |---|---|---| | `<SAP_DEV_CORE_SHARED_DIR>/rules/skill_operating_rules.md` | *(rule)* | Mandatory operating rules | | `<SAP_DEV_CORE_SHARED_DIR>/rules/language_independence_rules.md` | *(rule)* | GUI-scripting language independence — RFC-only skill, but rule applies to any downstream skill this is invoked from | | `<SAP_DEV_CORE_SHARED_DIR>/scripts/sap_dev_artefacts.ps1` | many | RFC artefact checker (also used by `/sap-dev-clean` and `/sap-dev-init`). |

---

Step 0 — Resolve Work Directory and Settings

**Resolve `work_dir` via the env-aware helper** — do NOT take `work_dir` from a direct `settings.json` read (that ignores the `SAPDEV_AI_WORK_DIR` env var and `userconfig.json`). Use the `WORK_DIR=` value printed by:

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))"

The settings note below still applies to the OTHER keys.

**Settings reads/writes follow `shared/rules/settings_lookup.md`** — merge per-key on the `.value` field (env var → `settings.local.json` → `userconfig.json` → `settings.json`); non-per-connection writes go to `userconfig.json`. Read `sap_dev_transport_request`, `sap_dev_package`, `sap_dev_function_group`, plus the standard SAP RFC connection keys.

**Per-connection keys (Phase 4.4)**: `sap_dev_transport_request`, `sap_dev_package`, `sap_dev_function_group` are SAP-system-specific. Per `settings_lookup.md` § Per-connection exception, read them from `connections.json[pinned-profile].dev_defaults` FIRST (resolve the pin via `{work_dir}\runtime\session_registry.json` `ai_sessions[<id>]`); only fall back to the two-file merge when `dev_defaults` is empty.

**Target the connection named in the Task argument.** If the Task argument names a SAP connection (SID / description substring / UUID), resolve it and pin this AI session to it so the RFC checker (and the per-connection `dev_defaults` read above) target the *named* system, not whatever is currently pinned (the default). This skill is read-only, so a mismatch only mis-reports the wrong system — but `/sap-dev-clean` calls this as its pre-flight, where targeting the wrong system is a safety issue.

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'; $m=@(Resolve-SapProfileHint -Hint '<TASK_ARG>'); if($m.Count -ne 1){ Write-Output ('TARGET=NEEDS_USER count='+$m.Count); return }; $rt=Join-Path (Get-SapWorkDir) 'runtime'; $aid=Get-SapAiSessionId -RuntimeDir $rt; & '<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_session_broker.ps1' -Action pin -WorkTemp ((Get-SapWorkDir)+'\temp') -AiSessionId $aid -ConnectionId $m[0].id -PinReason user_switched | Out-Null; Write-Output ('TARGET='+$m[0].system_name+'/'+$m[0].client)"

If `TARGET=NEEDS_USER`, ask the user which connection (the hint matched 0 or several profiles).

Set `{WORK_TEMP}` = `{work_dir}\temp`. Ensure it exists:

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

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 generated scratch (`*_run.ps1` / `*_run.vbs` and the `_run.json` state) under `{RUN_TEMP}`; keep `{WORK_TEMP}` (base) only for `Get-SapCurrentSessionPath -WorkTemp`.

---

Step 0.5 — Start Logging

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

---

Step 1 — Generate and Run the Checker

Fill the shared artefacts script:

$shared   = '<SAP_DEV_CORE_SHARED_DIR>'
$ps       = Get-Content "$shared\scripts\sap_dev_artefacts.ps1" -Raw -Encoding UTF8
$ps       = $ps.Replace('%%SAP_SERVER%%',     '')
$ps       = $ps.Replace('%%SAP_SYSNR%%',      '')
$ps       = $ps.Replace('%%SAP_CLIENT%%',     '')
$ps       = $ps.Replace('%%SAP_USER%%',       '')
$ps       = $ps.Replace('%%SAP_PASSWORD%%',   '')
$ps       = $ps.Replace('%%SAP_LANGUAGE%%',   '')
$ps       = $ps.Replace('%%RFC_LIB_PS1%%',    "$shared\scripts\sap_rfc_lib.ps1")
$ps       = $ps.Replace('%%TR%%',             'THE_TR')
$ps       = $ps.Replace('%%PACKAGE%%',        'THE_PKG')
$ps       = $ps.Replace('%%FUGR%%',           'THE_FG')
$ps       = $ps.Replace('%%WRAPPER_FM%%',     '')
$ps       = $ps.Replace('%%WRAPPER_STRUCT%%', '')
$ps       = $ps.Replace('%%WRAPPER_TT%%',     '')
$ps       = $ps.Replace('%%UTIL_PROGRAM%%',   '')
[System.IO.File]::WriteAllText('{RUN_TEMP}\sap_dev_status_run.ps1', $ps, [