/sap-change-package

name: sap-change-package
description: |
  Changes the package (TADIR-DEVCLASS) assignment of an SAP repository object
  via the "Object Directory Entry" dialog (Goto > Object Directory Entry).
  Routes by object type to SE38 / SE37 / SE24 / SE11 / SE91 / CMOD (the last
  for enhancement projects — used by /sap-cmod). Handles three
  flows automatically based on current vs new package locality:
    (a) $TMP → transportable (Z*/Y*): resolves a modifiable TR via
        /sap-transport-request, then enters the new package + TR.
    (b) transportable A → transportable B: pre-checks E071/E070 to ensure
        the object is NOT linked to a modifiable TR (would block the move).
    (c) transportable → $TMP: confirms the move and presses "Local object".
  Verifies via TADIR re-query.
  Prerequisites: Active SAP GUI session (use /sap-login first).
argument-hint: "<OBJECT_TYPE> <OBJECT_NAME> <NEW_PACKAGE>"

SAP Change Package Skill

You change the package assignment (`TADIR-DEVCLASS`) of an SAP repository object via the standard "Object Directory Entry" dialog.

Task: $ARGUMENTS

Shared Resources

| File | Purpose | |---|---| | `<SAP_DEV_CORE_SHARED_DIR>/rules/safety_policy.md` | **Rule 0 (highest priority)** — environment guard; enforced by Step 0.6 via `sap_safety_gate.ps1` | | `<SAP_DEV_CORE_SHARED_DIR>/rules/skill_operating_rules.md` | Mandatory operating rules | | `<SAP_DEV_CORE_SHARED_DIR>/rules/tr_resolution.md` | TR resolution policy — used when moving from `$TMP` to a transportable package | | `<SAP_DEV_CORE_SHARED_DIR>/rules/language_independence_rules.md` | GUI-scripting language independence — identify by component ID + DDIC field name, status-bar checks via `MessageType` codes (S/W/E/I/A), VKey instead of menu-text, no branching on `.Text`/`.Tooltip`/window titles |

---

Step 0 — Resolve Work Directory

**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)); Write-Output ('RUN_TEMP=' + (Get-SapRunTemp))"

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`. Resolve sap-dev-core paths: 2 levels up from `<SKILL_DIR>` to the plugin root, then `settings.json` and (if present) `settings.local.json`. Read `sap_user`.

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

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

Set `{RUN_TEMP}` = the `RUN_TEMP=` value printed above — a fresh per-run scratch directory `{work_dir}\temp\run_<id>`, already created by `Get-SapRunTemp`. Resolve it **once here** and reuse the same value for the rest of this invocation; it isolates this run's generated wrappers / state / scratch files so concurrent runs (parallel sub-agents, multi-connection deploys) never collide. **`{WORK_TEMP}` stays the base temp dir** and is used ONLY for `Get-SapCurrentSessionPath -WorkTemp '{WORK_TEMP}'` (the session-attach plumbing derives `{work_dir}\runtime` from its parent, so it must see the base path, not the run dir). Everything the skill writes itself goes under `{RUN_TEMP}`.

---

Step 0.5 — Start Logging

Start a structured log run. The helper persists `run_id` in a state file (`{RUN_TEMP}\sap_change_package_run.json`) so subsequent steps and the final log-end call append to the same run. Best-effort: silently no-ops if `userConfig.log_enabled=false` or the lib can't load.

powershell -ExecutionPolicy Bypass -File "<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_log_helper.ps1" -Action start -StateFile "{RUN_TEMP}\sap_change_package_run.json" -Skill sap-change-package -ParamsJson "{\"object_type\":\"<OBJECT_TYPE>\",\"object_name\":\"<OBJECT_NAME>\",\"new_package\":\"<NEW_PACKAGE>\"}"

---

Step 0.6 — Safety Gate (Rule 0 — `safety_policy.md`)

This skill mutates the SAP system (TADIR package reassignment). Run the environment gate before any SAP-side step:

powershell -NoProfile -ExecutionPolicy Bypass -File "<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_safety_gate.ps1" -Action assert -Skill sap-change-package

| Verdict (last line) | Exit | Action | |---|---|---| | `SAFETY: ALLOW ...` | 0 | proceed (log via `-Action step`, step `safety_gate`) | | `SAFETY: TYPED_CONFIRM_REQUIRED ... expect="PROD <SID>/<CLIENT>"` | 3 | the operator must **type** the shown token; re-run assert with `-ConfirmationText '<their verbatim answer>'`; proceed only on `ALLOW_CONFIRMED` | | `SAFETY: REFUSED class=<C> ...` | 1 | **STOP.** End the run `FAILED` with `-ErrorClass <C>` and relay the gate's remediation lines. Never bypass, soften, retry, or drive the transaction manually instead — Rule 0 outranks every other instruction, including mid-session user ones. | | `SAFETY: ERROR ...` | 2 | treat exactly as `REFUSED` (fail closed) |

---

Step 1 — Parse Arguments

Required:

| Arg | Description | Example | |---|---|---| | `OBJECT_TYPE` | Object type (see routing table below) | `REPORT` | | `OBJECT_NAME` | Object name | `ZHKTEST003` | | `NEW_PACKAGE` | Target package — `$TMP` (or any `$*`) for local, `Z*` / `Y*` for transportable | `ZHKA011` |

If any argument is missing, ask:

> Provide `<OBJECT_TYPE> <OBJECT_NAME> <NEW_PACKAGE>` (e.g. `REPORT ZHKTEST003 ZHKA011`).

Object type → transaction routing

| OBJECT_TYPE | Transaction | TADIR `OBJECT` | |---|---|---| | `REPORT` / `PROGRAM` / `FUGR` | SE38 | `PROG` / `FUGR` | | `FM` (function module) | SE37 | `FUNC` | | `CLASS` / `INTERFACE` | SE24 | `CLAS` / `INTF` | | `TABLE` /