القائمة
Use when designing or implementing a devcontainer workflow for OpenADT where configuration may live in Linux or WSL but SAP JCo and SNC may still need to execute on the host OS.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user invokes /act on a PR/MR or /act <context> with context ∈ {pr, plan, backlog, harvest}. Resolves threads in product code (or posts a substantive in-thread reply), commits, then closes threads. Never resolve-only. Harvest (collecting threads) lives in /harvest; triage (priority / grouping / wontfix) lives in /backlog. /act is the fix loop, not the collect or triage.
Domain-agnostic AI-native scenario runner (e2e-agent CLI). Scenarios are markdown prompts; evidence is written by the CLI. Use when the user invokes /e2e or asks to run a live scenario test and collect evidence under .e2e/results/. Agents use only e2e-agent commands — never import internal framework modules.
Use when the user invokes /harvest on a PR or runs `harvest:pr` / `harvest:batch`. Collects unresolved PR review threads into .agents/review-debt/harvests/*.jsonl on PR merge (or via workflow_dispatch). Does not run during /act and does not open a harvest bot PR — new files are append-only paths pushed straight to main. Downstream consumers: /backlog (triage), /act (batch fix). Harvest is a one-way collect, not a fix loop.
Actionable improvement items derived from experience and retrospectives. Items live in .agents/backlog/.
Unified agent memory. Use /remember to store facts, experience, observations, and mental-models in .agents/memory/.
Reflect on current session and record experience. /retrospect = remember. --plan = + backlog item. --fix = + implement now.
| name | openadt-devcontainer-host-runtime |
| description | Use when designing or implementing a devcontainer workflow for OpenADT where configuration may live in Linux or WSL but SAP JCo and SNC may still need to execute on the host OS. |
Config can live in Linux/WSL/devcontainer; JCo + SNC + Secure Login Web Adapter execute in the Java process that loads the native libraries.
Mounted Windows paths are not enough to run Windows sapjco3.dll from Linux Java.
| Step | Where | Tool |
|---|---|---|
| Detect SAP landscape, write TOML | WSL or devcontainer | ./dev-openadt setup, devcontainer bootstrap |
fetch / proxy with SDK+JCo | Host Windows (or Linux with Linux natives) | ./dev-openadt / scripts/openadt-sdk.ps1 (from clone) or packaged openadt |
| IDE proxy target | Host loopback | ./dev-openadt proxy / openadt proxy on 127.0.0.1 |
Generated paths (see docs/superpowers/specs/2026-05-21-devcontainer-native-runtime-design.md):
.devcontainer/openadt-config.toml.devcontainer/runtime.openadt.toml.openadt/destinations/generated-*.openadt.tomlBootstrap: tools/devcontainer-bootstrap (Bun/TS), not shell-only.
SetupAnalyzer / detectors may read:
/mnt/c/Users/<user>/SAP/... landscape XMLsaprules.xml, Eclipse workspace under /mnt/c/...That populates config only. It does not make container Java load Windows DLLs.
https://127.0.0.1:34443 is on the host where Secure Login Client runsfetch cannot rely on host hub unless port-forwarded and the same Java process uses host-native SNC (usually wrong)For MVP, run SDK transport on the host after setup in WSL wrote config to a shared path (~/.openadt/config.toml visible from both).
On the host OS (from clone: ./dev-openadt …; installed CLI: openadt …):
./dev-openadt fetch <SID> /sap/bc/adt/core/http/systeminformation --json
Must use SapDestinationResolver + AdtSdkTransportClient (not HTTP transport), with Eclipse destination when workspace is on a mounted path detectors can scan.
jco_native_dir on the host (common)Devcontainer bootstrap may set runtime.jco_native_dir to .devcontainer/dist/jco (Linux libsapjco3.so). If the user later runs ./dev-openadt fetch on Windows host Java, JCo fails with no sapjco3 in java.library.path even though ./dev-openadt setup --check already detects the correct Windows directory elsewhere.
Fix on the host OS: ./dev-openadt setup (or setup --check then setup --skip-build) so ~/.openadt/local.openadt.toml lists a directory that contains sapjco3.dll, not only libsapjco3.so.
Agents: compare configured jco_native_dir to the native file for the OS running the command before debugging destinations or SSO.
.devcontainer/dist/jco in local.openadt.toml while running fetch/proxy on Windows host Javaopenadt-sdk.ps1 inside Linux container against Windows .p2 paths without Windows Javatransport=http + MYSAPSSO2 equals Eclipse ADT behavior.devcontainer/dist JCo natives as a substitute for host SAP installationopenadt-local-sap-runtime — JCo jar naming, classpath order, Secure Login profiles, Eclipse destinations.