[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-azure-sdaf-media-diagnostics":3,"mdc-smow54-key":35,"related-repo-azure-sdaf-media-diagnostics":640,"related-org-azure-sdaf-media-diagnostics":724},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":12,"stars":24,"repoUrl":25,"updatedAt":26,"license":27,"forks":28,"topics":29,"repo":30,"sourceUrl":33,"mdContent":34},"sdaf-media-diagnostics","diagnose SDAF media and BOM processing","Diagnose SDAF software-download and BOM-processing failures after a BOM is already selected. Covers the documented local media path, SAP download, storage-account upload\u002Fdownload, checksum validation, and `SAPCAR` \u002F `.EXE` extraction. Use when a user says \"download_menu failed\", \"BOM downloader 404\", \"missing archive\", \"checksum mismatch\", \"SAPCAR failed\", \"bom-processing-done missing\", or \"my SPS07 media run can't find a file\". Do NOT use to choose a BOM (see `sdaf-bom-selection`), to run a clean first-time media download with no failure, or to diagnose a later non-media install failure.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},"azure","Azure (Microsoft)","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fazure.png","Azure",[13,15,18,21],{"name":11,"slug":8,"type":14},"tag",{"name":16,"slug":17,"type":14},"Diagnostics","diagnostics",{"name":19,"slug":20,"type":14},"Storage","storage",{"name":22,"slug":23,"type":14},"SAP","sap",143,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fsap-automation","2026-09-02T07:48:06.369058","MIT",173,[],{"repoUrl":25,"stars":24,"forks":28,"topics":31,"description":32},[],"This is the repository supporting the SAP deployment automation framework on Azure","https:\u002F\u002Fgithub.com\u002FAzure\u002Fsap-automation\u002Ftree\u002FHEAD\u002Fskills\u002Fsdaf-media-diagnostics","---\nname: sdaf-media-diagnostics\ndescription: >\n  Diagnose SDAF software-download and BOM-processing failures after a BOM is\n  already selected. Covers the documented local media path, SAP download,\n  storage-account upload\u002Fdownload, checksum validation, and\n  `SAPCAR` \u002F `.EXE` extraction. Use when a user says \"download_menu failed\",\n  \"BOM downloader 404\", \"missing archive\", \"checksum mismatch\", \"SAPCAR\n  failed\", \"bom-processing-done missing\", or \"my SPS07 media run can't find\n  a file\". Do NOT use to choose a BOM (see `sdaf-bom-selection`), to run a\n  clean first-time media download with no failure, or to diagnose a later\n  non-media install failure.\nallowed-tools: shell\nlicense: MIT\n---\n\n# SDAF Media Diagnostics\n\nAction-loop skill. Diagnoses failures on the local software path after the\noperator already chose the BOM and started either `download_menu.sh` or BOM\nprocessing from `configuration_menu.sh`. Grounded in\n`docs\u002Flocal\u002F06-00-software-and-installation.md`,\n`docs\u002Flocal\u002Ftroubleshooting.md`, and `docs\u002FPLUGINS.md`. No invented recovery\npaths.\n\n## When to invoke\n\nTrigger on: \"download_menu failed\", \"BOM downloader 404\", \"missing archive\",\n\"checksum mismatch\", \"SAPCAR failed\", \"bom-processing-done missing\",\n\"SPS07 media file missing\".\n\nDo NOT trigger on: choosing a BOM\u002Fversion, running a clean first download, or\na later DB\u002FSAP install failure after media staging.\n\n## Preconditions\n\n- Collect the exact failing command or menu step, exit code, and last 200 lines\n  of output.\n- Identify whether the failure happened in:\n  - the documented media acquisition step; or\n  - BOM processing during configuration and installation.\n- If the operator only says \"SPS07\" or similar product\u002Fversion words, ask\n  whether this is a BOM-choice question or a concrete failing file.\n\n## Recipe\n\n### Step 1 — Classify the failing lane\n\n- **Acquisition lane** — use\n  `docs\u002Flocal\u002F06-00-software-and-installation.md § Download software` and its\n  documented inputs.\n- **Processing lane** — use\n  `§ Run configuration and installation` and its safe-retry guidance.\n- If the failure is in a later numbered install playbook rather than BOM\n  acquisition \u002F processing, stop and route to `sdaf-sap-installation`\n  or `sdaf-failure-triage` if the install-stage owner is still ambiguous.\n\n### Step 2 — Walk the symptom map\n\nUse [`references\u002Fmedia-symptom-map.md`](references\u002Fmedia-symptom-map.md) and\nmatch the *exact* signature before suggesting any retry. The map covers:\n\n- missing `sap-parameters.yaml` \u002F `BOM_CATALOG`\n- BOM not found\n- `s_user` \u002F `s_password` or storage-account auth failures\n- archive `404` \u002F missing blob\n- checksum mismatch\n- `SAPCAR` \u002F `.EXE` extraction failures\n- missing `.progress\u002Fbom-processing-done`\n- offline \u002F air-gapped asks that the repo does not document\n\nIf nothing matches, say the shipped docs\u002Fcode do not describe this media\nfailure and stop.\n\n### Step 3 — Re-read the current BOM and documented inputs\n\nThe authoritative inputs are the current `sap-parameters.yaml`, the selected\nBOM YAML, and the operator documentation:\n\n- `docs\u002Flocal\u002F06-00-software-and-installation.md § Inputs and BOM ownership` —\n  `BOM_CATALOG` must point at the samples root; `download_menu.sh` requires\n  `application_bom_name`, `database_bom_name`, `sap_kernel_bom_name`, and\n  `save_bom_as`.\n- `docs\u002Flocal\u002F06-00-software-and-installation.md § Configuration preparation`\n  — review the current BOM's URLs, archive names, checksums, and target\n  product versions.\nDo not rename files, replace URLs, or invent checksums from memory.\n\n### Step 4 — Retry only the minimal documented step\n\n- For acquisition-lane failures, fix the matched precondition or BOM\u002Finput\n  issue, then rerun **BOM Downloader** from `download_menu.sh`.\n- For processing-lane failures, rerun the smallest applicable playbook from\n  `configuration_menu.sh`;\n  `docs\u002Flocal\u002F06-00-software-and-installation.md § Safe retry` says to review\n  the failed numbered playbook, output, and progress marker first.\n- Use the documented completion evidence; do not create or delete progress\n  markers manually.\n\n## Special boundary: SPS-level questions\n\nThe local docs tell operators to review BOM names, URLs, archive names,\nchecksums, and target product versions, but they do **not** ship an\nSPS07-specific troubleshooting runbook. Use this rule:\n\n- \"Which BOM\u002Fversion do I need for SPS07?\" → `sdaf-bom-selection`.\n- \"The already-selected SPS07 media set is failing with a missing archive,\n  checksum, or extract error\" → stay here and work the exact failing file\u002Flog\n  through the symptom map.\n\n## Hard rules\n\n- Documented behaviour only. `docs\u002FPLUGINS.md` explicitly says air-gapped \u002F\n  offline media is outside shipped guidance.\n- Do not invent new BOM contents, replacement URLs, checksums, or SPS mappings.\n- Do not treat a generic later install failure as a media problem without a\n  matching acquisition \u002F processing anchor.\n- Do not delete `.progress` markers or storage blobs merely to force a rerun.\n\n## See also\n\n- `sdaf-bom-selection` — choose product vs component BOMs and compatibility\n  guardrails.\n- `sdaf-media-acquisition` — clean first-time media download once the failure\n  boundary is gone.\n- `sdaf-failure-triage` — non-media or ambiguous stage failures.\n- `docs\u002Flocal\u002F06-00-software-and-installation.md`,\n  `docs\u002Flocal\u002Ftroubleshooting.md`,\n  `docs\u002FPLUGINS.md`.\n",{"data":36,"body":38},{"name":4,"description":6,"allowed-tools":37,"license":27},"shell",{"type":39,"children":40},"root",[41,49,96,103,108,113,119,152,158,165,225,231,256,352,357,363,375,445,451,497,503,515,535,541,579,585],{"type":42,"tag":43,"props":44,"children":45},"element","h1",{"id":4},[46],{"type":47,"value":48},"text","SDAF Media Diagnostics",{"type":42,"tag":50,"props":51,"children":52},"p",{},[53,55,62,64,70,72,78,80,86,88,94],{"type":47,"value":54},"Action-loop skill. Diagnoses failures on the local software path after the\noperator already chose the BOM and started either ",{"type":42,"tag":56,"props":57,"children":59},"code",{"className":58},[],[60],{"type":47,"value":61},"download_menu.sh",{"type":47,"value":63}," or BOM\nprocessing from ",{"type":42,"tag":56,"props":65,"children":67},{"className":66},[],[68],{"type":47,"value":69},"configuration_menu.sh",{"type":47,"value":71},". Grounded in\n",{"type":42,"tag":56,"props":73,"children":75},{"className":74},[],[76],{"type":47,"value":77},"docs\u002Flocal\u002F06-00-software-and-installation.md",{"type":47,"value":79},",\n",{"type":42,"tag":56,"props":81,"children":83},{"className":82},[],[84],{"type":47,"value":85},"docs\u002Flocal\u002Ftroubleshooting.md",{"type":47,"value":87},", and ",{"type":42,"tag":56,"props":89,"children":91},{"className":90},[],[92],{"type":47,"value":93},"docs\u002FPLUGINS.md",{"type":47,"value":95},". No invented recovery\npaths.",{"type":42,"tag":97,"props":98,"children":100},"h2",{"id":99},"when-to-invoke",[101],{"type":47,"value":102},"When to invoke",{"type":42,"tag":50,"props":104,"children":105},{},[106],{"type":47,"value":107},"Trigger on: \"download_menu failed\", \"BOM downloader 404\", \"missing archive\",\n\"checksum mismatch\", \"SAPCAR failed\", \"bom-processing-done missing\",\n\"SPS07 media file missing\".",{"type":42,"tag":50,"props":109,"children":110},{},[111],{"type":47,"value":112},"Do NOT trigger on: choosing a BOM\u002Fversion, running a clean first download, or\na later DB\u002FSAP install failure after media staging.",{"type":42,"tag":97,"props":114,"children":116},{"id":115},"preconditions",[117],{"type":47,"value":118},"Preconditions",{"type":42,"tag":120,"props":121,"children":122},"ul",{},[123,129,147],{"type":42,"tag":124,"props":125,"children":126},"li",{},[127],{"type":47,"value":128},"Collect the exact failing command or menu step, exit code, and last 200 lines\nof output.",{"type":42,"tag":124,"props":130,"children":131},{},[132,134],{"type":47,"value":133},"Identify whether the failure happened in:\n",{"type":42,"tag":120,"props":135,"children":136},{},[137,142],{"type":42,"tag":124,"props":138,"children":139},{},[140],{"type":47,"value":141},"the documented media acquisition step; or",{"type":42,"tag":124,"props":143,"children":144},{},[145],{"type":47,"value":146},"BOM processing during configuration and installation.",{"type":42,"tag":124,"props":148,"children":149},{},[150],{"type":47,"value":151},"If the operator only says \"SPS07\" or similar product\u002Fversion words, ask\nwhether this is a BOM-choice question or a concrete failing file.",{"type":42,"tag":97,"props":153,"children":155},{"id":154},"recipe",[156],{"type":47,"value":157},"Recipe",{"type":42,"tag":159,"props":160,"children":162},"h3",{"id":161},"step-1-classify-the-failing-lane",[163],{"type":47,"value":164},"Step 1 — Classify the failing lane",{"type":42,"tag":120,"props":166,"children":167},{},[168,187,204],{"type":42,"tag":124,"props":169,"children":170},{},[171,177,179,185],{"type":42,"tag":172,"props":173,"children":174},"strong",{},[175],{"type":47,"value":176},"Acquisition lane",{"type":47,"value":178}," — use\n",{"type":42,"tag":56,"props":180,"children":182},{"className":181},[],[183],{"type":47,"value":184},"docs\u002Flocal\u002F06-00-software-and-installation.md § Download software",{"type":47,"value":186}," and its\ndocumented inputs.",{"type":42,"tag":124,"props":188,"children":189},{},[190,195,196,202],{"type":42,"tag":172,"props":191,"children":192},{},[193],{"type":47,"value":194},"Processing lane",{"type":47,"value":178},{"type":42,"tag":56,"props":197,"children":199},{"className":198},[],[200],{"type":47,"value":201},"§ Run configuration and installation",{"type":47,"value":203}," and its safe-retry guidance.",{"type":42,"tag":124,"props":205,"children":206},{},[207,209,215,217,223],{"type":47,"value":208},"If the failure is in a later numbered install playbook rather than BOM\nacquisition \u002F processing, stop and route to ",{"type":42,"tag":56,"props":210,"children":212},{"className":211},[],[213],{"type":47,"value":214},"sdaf-sap-installation",{"type":47,"value":216},"\nor ",{"type":42,"tag":56,"props":218,"children":220},{"className":219},[],[221],{"type":47,"value":222},"sdaf-failure-triage",{"type":47,"value":224}," if the install-stage owner is still ambiguous.",{"type":42,"tag":159,"props":226,"children":228},{"id":227},"step-2-walk-the-symptom-map",[229],{"type":47,"value":230},"Step 2 — Walk the symptom map",{"type":42,"tag":50,"props":232,"children":233},{},[234,236,246,248,254],{"type":47,"value":235},"Use ",{"type":42,"tag":237,"props":238,"children":240},"a",{"href":239},"references\u002Fmedia-symptom-map.md",[241],{"type":42,"tag":56,"props":242,"children":244},{"className":243},[],[245],{"type":47,"value":239},{"type":47,"value":247}," and\nmatch the ",{"type":42,"tag":249,"props":250,"children":251},"em",{},[252],{"type":47,"value":253},"exact",{"type":47,"value":255}," signature before suggesting any retry. The map covers:",{"type":42,"tag":120,"props":257,"children":258},{},[259,278,283,301,314,319,337,347],{"type":42,"tag":124,"props":260,"children":261},{},[262,264,270,272],{"type":47,"value":263},"missing ",{"type":42,"tag":56,"props":265,"children":267},{"className":266},[],[268],{"type":47,"value":269},"sap-parameters.yaml",{"type":47,"value":271}," \u002F ",{"type":42,"tag":56,"props":273,"children":275},{"className":274},[],[276],{"type":47,"value":277},"BOM_CATALOG",{"type":42,"tag":124,"props":279,"children":280},{},[281],{"type":47,"value":282},"BOM not found",{"type":42,"tag":124,"props":284,"children":285},{},[286,292,293,299],{"type":42,"tag":56,"props":287,"children":289},{"className":288},[],[290],{"type":47,"value":291},"s_user",{"type":47,"value":271},{"type":42,"tag":56,"props":294,"children":296},{"className":295},[],[297],{"type":47,"value":298},"s_password",{"type":47,"value":300}," or storage-account auth failures",{"type":42,"tag":124,"props":302,"children":303},{},[304,306,312],{"type":47,"value":305},"archive ",{"type":42,"tag":56,"props":307,"children":309},{"className":308},[],[310],{"type":47,"value":311},"404",{"type":47,"value":313}," \u002F missing blob",{"type":42,"tag":124,"props":315,"children":316},{},[317],{"type":47,"value":318},"checksum mismatch",{"type":42,"tag":124,"props":320,"children":321},{},[322,328,329,335],{"type":42,"tag":56,"props":323,"children":325},{"className":324},[],[326],{"type":47,"value":327},"SAPCAR",{"type":47,"value":271},{"type":42,"tag":56,"props":330,"children":332},{"className":331},[],[333],{"type":47,"value":334},".EXE",{"type":47,"value":336}," extraction failures",{"type":42,"tag":124,"props":338,"children":339},{},[340,341],{"type":47,"value":263},{"type":42,"tag":56,"props":342,"children":344},{"className":343},[],[345],{"type":47,"value":346},".progress\u002Fbom-processing-done",{"type":42,"tag":124,"props":348,"children":349},{},[350],{"type":47,"value":351},"offline \u002F air-gapped asks that the repo does not document",{"type":42,"tag":50,"props":353,"children":354},{},[355],{"type":47,"value":356},"If nothing matches, say the shipped docs\u002Fcode do not describe this media\nfailure and stop.",{"type":42,"tag":159,"props":358,"children":360},{"id":359},"step-3-re-read-the-current-bom-and-documented-inputs",[361],{"type":47,"value":362},"Step 3 — Re-read the current BOM and documented inputs",{"type":42,"tag":50,"props":364,"children":365},{},[366,368,373],{"type":47,"value":367},"The authoritative inputs are the current ",{"type":42,"tag":56,"props":369,"children":371},{"className":370},[],[372],{"type":47,"value":269},{"type":47,"value":374},", the selected\nBOM YAML, and the operator documentation:",{"type":42,"tag":120,"props":376,"children":377},{},[378,434],{"type":42,"tag":124,"props":379,"children":380},{},[381,387,389,394,396,401,403,409,411,417,418,424,426,432],{"type":42,"tag":56,"props":382,"children":384},{"className":383},[],[385],{"type":47,"value":386},"docs\u002Flocal\u002F06-00-software-and-installation.md § Inputs and BOM ownership",{"type":47,"value":388}," —\n",{"type":42,"tag":56,"props":390,"children":392},{"className":391},[],[393],{"type":47,"value":277},{"type":47,"value":395}," must point at the samples root; ",{"type":42,"tag":56,"props":397,"children":399},{"className":398},[],[400],{"type":47,"value":61},{"type":47,"value":402}," requires\n",{"type":42,"tag":56,"props":404,"children":406},{"className":405},[],[407],{"type":47,"value":408},"application_bom_name",{"type":47,"value":410},", ",{"type":42,"tag":56,"props":412,"children":414},{"className":413},[],[415],{"type":47,"value":416},"database_bom_name",{"type":47,"value":410},{"type":42,"tag":56,"props":419,"children":421},{"className":420},[],[422],{"type":47,"value":423},"sap_kernel_bom_name",{"type":47,"value":425},", and\n",{"type":42,"tag":56,"props":427,"children":429},{"className":428},[],[430],{"type":47,"value":431},"save_bom_as",{"type":47,"value":433},".",{"type":42,"tag":124,"props":435,"children":436},{},[437,443],{"type":42,"tag":56,"props":438,"children":440},{"className":439},[],[441],{"type":47,"value":442},"docs\u002Flocal\u002F06-00-software-and-installation.md § Configuration preparation",{"type":47,"value":444},"\n— review the current BOM's URLs, archive names, checksums, and target\nproduct versions.\nDo not rename files, replace URLs, or invent checksums from memory.",{"type":42,"tag":159,"props":446,"children":448},{"id":447},"step-4-retry-only-the-minimal-documented-step",[449],{"type":47,"value":450},"Step 4 — Retry only the minimal documented step",{"type":42,"tag":120,"props":452,"children":453},{},[454,472,492],{"type":42,"tag":124,"props":455,"children":456},{},[457,459,464,466,471],{"type":47,"value":458},"For acquisition-lane failures, fix the matched precondition or BOM\u002Finput\nissue, then rerun ",{"type":42,"tag":172,"props":460,"children":461},{},[462],{"type":47,"value":463},"BOM Downloader",{"type":47,"value":465}," from ",{"type":42,"tag":56,"props":467,"children":469},{"className":468},[],[470],{"type":47,"value":61},{"type":47,"value":433},{"type":42,"tag":124,"props":473,"children":474},{},[475,477,482,484,490],{"type":47,"value":476},"For processing-lane failures, rerun the smallest applicable playbook from\n",{"type":42,"tag":56,"props":478,"children":480},{"className":479},[],[481],{"type":47,"value":69},{"type":47,"value":483},";\n",{"type":42,"tag":56,"props":485,"children":487},{"className":486},[],[488],{"type":47,"value":489},"docs\u002Flocal\u002F06-00-software-and-installation.md § Safe retry",{"type":47,"value":491}," says to review\nthe failed numbered playbook, output, and progress marker first.",{"type":42,"tag":124,"props":493,"children":494},{},[495],{"type":47,"value":496},"Use the documented completion evidence; do not create or delete progress\nmarkers manually.",{"type":42,"tag":97,"props":498,"children":500},{"id":499},"special-boundary-sps-level-questions",[501],{"type":47,"value":502},"Special boundary: SPS-level questions",{"type":42,"tag":50,"props":504,"children":505},{},[506,508,513],{"type":47,"value":507},"The local docs tell operators to review BOM names, URLs, archive names,\nchecksums, and target product versions, but they do ",{"type":42,"tag":172,"props":509,"children":510},{},[511],{"type":47,"value":512},"not",{"type":47,"value":514}," ship an\nSPS07-specific troubleshooting runbook. Use this rule:",{"type":42,"tag":120,"props":516,"children":517},{},[518,530],{"type":42,"tag":124,"props":519,"children":520},{},[521,523,529],{"type":47,"value":522},"\"Which BOM\u002Fversion do I need for SPS07?\" → ",{"type":42,"tag":56,"props":524,"children":526},{"className":525},[],[527],{"type":47,"value":528},"sdaf-bom-selection",{"type":47,"value":433},{"type":42,"tag":124,"props":531,"children":532},{},[533],{"type":47,"value":534},"\"The already-selected SPS07 media set is failing with a missing archive,\nchecksum, or extract error\" → stay here and work the exact failing file\u002Flog\nthrough the symptom map.",{"type":42,"tag":97,"props":536,"children":538},{"id":537},"hard-rules",[539],{"type":47,"value":540},"Hard rules",{"type":42,"tag":120,"props":542,"children":543},{},[544,556,561,566],{"type":42,"tag":124,"props":545,"children":546},{},[547,549,554],{"type":47,"value":548},"Documented behaviour only. ",{"type":42,"tag":56,"props":550,"children":552},{"className":551},[],[553],{"type":47,"value":93},{"type":47,"value":555}," explicitly says air-gapped \u002F\noffline media is outside shipped guidance.",{"type":42,"tag":124,"props":557,"children":558},{},[559],{"type":47,"value":560},"Do not invent new BOM contents, replacement URLs, checksums, or SPS mappings.",{"type":42,"tag":124,"props":562,"children":563},{},[564],{"type":47,"value":565},"Do not treat a generic later install failure as a media problem without a\nmatching acquisition \u002F processing anchor.",{"type":42,"tag":124,"props":567,"children":568},{},[569,571,577],{"type":47,"value":570},"Do not delete ",{"type":42,"tag":56,"props":572,"children":574},{"className":573},[],[575],{"type":47,"value":576},".progress",{"type":47,"value":578}," markers or storage blobs merely to force a rerun.",{"type":42,"tag":97,"props":580,"children":582},{"id":581},"see-also",[583],{"type":47,"value":584},"See also",{"type":42,"tag":120,"props":586,"children":587},{},[588,598,609,619],{"type":42,"tag":124,"props":589,"children":590},{},[591,596],{"type":42,"tag":56,"props":592,"children":594},{"className":593},[],[595],{"type":47,"value":528},{"type":47,"value":597}," — choose product vs component BOMs and compatibility\nguardrails.",{"type":42,"tag":124,"props":599,"children":600},{},[601,607],{"type":42,"tag":56,"props":602,"children":604},{"className":603},[],[605],{"type":47,"value":606},"sdaf-media-acquisition",{"type":47,"value":608}," — clean first-time media download once the failure\nboundary is gone.",{"type":42,"tag":124,"props":610,"children":611},{},[612,617],{"type":42,"tag":56,"props":613,"children":615},{"className":614},[],[616],{"type":47,"value":222},{"type":47,"value":618}," — non-media or ambiguous stage failures.",{"type":42,"tag":124,"props":620,"children":621},{},[622,627,628,633,634,639],{"type":42,"tag":56,"props":623,"children":625},{"className":624},[],[626],{"type":47,"value":77},{"type":47,"value":79},{"type":42,"tag":56,"props":629,"children":631},{"className":630},[],[632],{"type":47,"value":85},{"type":47,"value":79},{"type":42,"tag":56,"props":635,"children":637},{"className":636},[],[638],{"type":47,"value":93},{"type":47,"value":433},{"items":641,"total":723},[642,653,668,683,694,707,716],{"slug":528,"name":528,"fn":643,"description":644,"org":645,"tags":646,"stars":24,"repoUrl":25,"updatedAt":652},"select SAP Bill of Materials","Pick the right SDAF BOM for a target SAP product \u002F release \u002F DB platform \u002F version \u002F kernel \u002F topology. Explains where BOMs live in the samples repo (`SAP\u002F` for whole products, `BOM\u002F` for components), decodes the `ms`, `v####`, and `latest` suffix conventions, points at the compatibility guardrails (`supportedPlatforms`, `supportedDBVersions`, `supportedKernels`), and reminds the operator that the download flow needs four explicit BOM keys in `sap-parameters.yaml`. Use when a user says \"which BOM do I use\", \"product BOM vs component BOM\", \"SAP samples BOM catalog\", \"BOM_CATALOG\", \"S4\u002F2023 BOM\", \"HANA BOM\", or \"how do I pick a BOM for HANA\u002FOracle\u002FDB2\u002FASE\". Do NOT use to author a new BOM, to acquire media (`sdaf-media-acquisition`), or to troubleshoot a checksum \u002F 404 (`sdaf-media-diagnostics`).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[647,648,651],{"name":11,"slug":8,"type":14},{"name":649,"slug":650,"type":14},"Configuration","configuration",{"name":22,"slug":23,"type":14},"2026-09-02T07:47:45.597063",{"slug":654,"name":654,"fn":655,"description":656,"org":657,"tags":658,"stars":24,"repoUrl":25,"updatedAt":667},"sdaf-control-plane-bootstrap","deploy SDAF control plane infrastructure","Deploy the SDAF control plane locally: prepare DEPLOYER and LIBRARY tfvars, review the plan, run `deploy_controlplane.sh` per `docs\u002Flocal\u002F03-00-control-plane.md § Run`, and validate the deployer + library + state hand-off. Grounded in `docs\u002Flocal\u002F03-00-control-plane.md`. Use when a user says \"deploy the SDAF control plane\", \"run deploy_controlplane.sh\", \"bootstrap SDAF from an empty subscription\", \"install the deployer\" or \"create the SAP library\". Do NOT use for workload zone (see sdaf-workload-zone), SAP system (see sdaf-sap-system), removal (`sdaf-safe-removal`), or Azure Government \u002F sovereign-cloud deltas (`sdaf-sovereign-cloud`).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[659,660,663,666],{"name":11,"slug":8,"type":14},{"name":661,"slug":662,"type":14},"Deployment","deployment",{"name":664,"slug":665,"type":14},"Infrastructure","infrastructure",{"name":22,"slug":23,"type":14},"2026-09-02T07:46:51.573641",{"slug":222,"name":222,"fn":669,"description":670,"org":671,"tags":672,"stars":24,"repoUrl":25,"updatedAt":682},"triage failed SAP automation runs","Triage a failed or suspicious SDAF run: distinguish a real failure from a green no-op or a clean plan reported as failure, map the observed symptom to a documented cause in `docs\u002Flocal\u002Ftroubleshooting.md`, and hand off to the stage-owning skill for retry. Use when a user says \"SDAF run failed\", \"my deploy exited non-zero\", \"the plan was clean but exit 1\", \"the run said success but nothing was deployed\", \"state lock error\", \"unexpected replacement\", \"control plane stopped partway\", \"generated hosts.yaml missing\", \"workload-zone private endpoint failure\", \"workload-zone subnet policy failure\", or \"SDAF exit 2\". Do NOT use to actually deploy or to redesign the workspace layout.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[673,674,675,678,679],{"name":11,"slug":8,"type":14},{"name":16,"slug":17,"type":14},{"name":676,"slug":677,"type":14},"Operations","operations",{"name":22,"slug":23,"type":14},{"name":680,"slug":681,"type":14},"Triage","triage","2026-09-02T07:47:40.607437",{"slug":684,"name":684,"fn":685,"description":686,"org":687,"tags":688,"stars":24,"repoUrl":25,"updatedAt":693},"sdaf-ha-diagnostics","diagnose SDAF high-availability cluster failures","Diagnose a live or recently failed SDAF high-availability cluster without changing cluster state. Start read-first: capture `crm status full` or `pcs status --full`, inspect SBD or fencing evidence, confirm current resource placement, and reuse existing quality-assurance or HCMT artifacts. Grounded in `docs\u002Flocal\u002F07-10-quality-assurance.md`, the shipped Pacemaker role vars\u002Ftasks, and the SAP Automation QA setup role. Use when a user says \"diagnose my HANA failover\", \"crm status\", \"pcs status\", \"check fencing\", \"why is the SCS\u002FERS cluster unhealthy\", \"offline_validation\u002Fcib\", or \"review an HCMT result zip\". Do NOT use for pre-deploy topology or design choices (see `sdaf-ha-topology`), fresh installation\u002Fdeploy, or disruptive failover\u002Ffencing exercises (see `sdaf-quality-assurance`).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[689,690,691,692],{"name":11,"slug":8,"type":14},{"name":16,"slug":17,"type":14},{"name":676,"slug":677,"type":14},{"name":22,"slug":23,"type":14},"2026-09-02T07:48:04.154501",{"slug":695,"name":695,"fn":696,"description":697,"org":698,"tags":699,"stars":24,"repoUrl":25,"updatedAt":706},"sdaf-ha-topology","design high-availability SAP topologies","Choose the documented SDAF high-availability design before SAP-system deployment. Use when a user asks which HA topology to deploy, whether to use AFA or SBD, AFS or ANF, HANA scale-up or scale-out, whether ANGI is allowed, or which HA inputs must be set before deployment. Ground answers in the current support matrix, Ansible roles, sample tfvars, and validation logic. Do NOT use for live cluster diagnosis (sdaf-ha-diagnostics) or for running the installers (sdaf-sap-installation).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[700,703,704,705],{"name":701,"slug":702,"type":14},"Architecture","architecture",{"name":11,"slug":8,"type":14},{"name":664,"slug":665,"type":14},{"name":22,"slug":23,"type":14},"2026-09-02T07:47:43.405138",{"slug":606,"name":606,"fn":708,"description":709,"org":710,"tags":711,"stars":24,"repoUrl":25,"updatedAt":715},"acquire SAP installation media","Acquire approved SAP media into the SDAF library after SAP-system infrastructure exists. Drives local `deploy\u002Fansible\u002Fdownload_menu.sh` per `docs\u002Flocal\u002F06-00-software-and-installation.md § Download software`, enforces the documented `BOM_CATALOG` root and the four required `sap-parameters.yaml` BOM keys (`application_bom_name`, `database_bom_name`, `sap_kernel_bom_name`, `save_bom_as`), and explains the documented download and validation flow. Use for \"download SAP media\", \"run download_menu.sh\", \"acquire software into the library\", \"BOM Downloader\", \"BOM_CATALOG\", or \"assemble application\u002Fdatabase\u002Fkernel BOMs for download\". Do NOT use to choose a BOM, troubleshoot a failed download, or run installation playbooks.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[712,713,714],{"name":11,"slug":8,"type":14},{"name":676,"slug":677,"type":14},{"name":22,"slug":23,"type":14},"2026-09-02T07:46:44.504107",{"slug":4,"name":4,"fn":5,"description":6,"org":717,"tags":718,"stars":24,"repoUrl":25,"updatedAt":26},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[719,720,721,722],{"name":11,"slug":8,"type":14},{"name":16,"slug":17,"type":14},{"name":22,"slug":23,"type":14},{"name":19,"slug":20,"type":14},18,{"items":725,"total":856},[726,745,762,768,775,783,790,797,803,810,823,843],{"slug":727,"name":727,"fn":728,"description":729,"org":730,"tags":731,"stars":742,"repoUrl":743,"updatedAt":744},"azure-arg-external-evaluation-policy-author","author and test Azure Resource Graph policies","Use when the user wants to author, design, or test an Azure Policy that queries Azure Resource Graph (ARG) at request-time — i.e. a policy whose deny\u002Faudit decision depends on data from elsewhere in the subscription (sibling\u002Fparent resource state, RG-wide invariants, multi-hop relationships, etc.). Formally called Azure Policy External Evaluation; sometimes referred to colloquially as \"Invoke\". Drives an iterative KQL co-design loop against the user's real subscription via `az graph query`, then emits a policy definition, assignment, `.http` test flow, and an `EXPLANATION.md` companion. Read-only; never provisions anything.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[732,733,736,739],{"name":11,"slug":8,"type":14},{"name":734,"slug":735,"type":14},"Compliance","compliance",{"name":737,"slug":738,"type":14},"Governance","governance",{"name":740,"slug":741,"type":14},"Policy","policy",1689,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-policy","2026-07-12T08:17:48.378432",{"slug":746,"name":746,"fn":747,"description":748,"org":749,"tags":750,"stars":759,"repoUrl":760,"updatedAt":761},"azure-blueprints-migration","migrate Azure Blueprints to Template Specs","Use when a user needs to migrate off Azure Blueprints (definitions and\u002For assignments) to Template Specs and Deployment Stacks before the January 31, 2027 retirement. Covers inventory, export, conversion to Bicep, policy decoupling, Template Spec publishing, Deployment Stack deployment with deny-settings, validation, and cutover.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[751,752,753,756],{"name":11,"slug":8,"type":14},{"name":661,"slug":662,"type":14},{"name":754,"slug":755,"type":14},"Infrastructure as Code","infrastructure-as-code",{"name":757,"slug":758,"type":14},"Migration","migration",261,"https:\u002F\u002Fgithub.com\u002FAzure\u002Fazure-blueprints","2026-08-20T03:28:18.136156",{"slug":528,"name":528,"fn":643,"description":644,"org":763,"tags":764,"stars":24,"repoUrl":25,"updatedAt":652},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[765,766,767],{"name":11,"slug":8,"type":14},{"name":649,"slug":650,"type":14},{"name":22,"slug":23,"type":14},{"slug":654,"name":654,"fn":655,"description":656,"org":769,"tags":770,"stars":24,"repoUrl":25,"updatedAt":667},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[771,772,773,774],{"name":11,"slug":8,"type":14},{"name":661,"slug":662,"type":14},{"name":664,"slug":665,"type":14},{"name":22,"slug":23,"type":14},{"slug":222,"name":222,"fn":669,"description":670,"org":776,"tags":777,"stars":24,"repoUrl":25,"updatedAt":682},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[778,779,780,781,782],{"name":11,"slug":8,"type":14},{"name":16,"slug":17,"type":14},{"name":676,"slug":677,"type":14},{"name":22,"slug":23,"type":14},{"name":680,"slug":681,"type":14},{"slug":684,"name":684,"fn":685,"description":686,"org":784,"tags":785,"stars":24,"repoUrl":25,"updatedAt":693},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[786,787,788,789],{"name":11,"slug":8,"type":14},{"name":16,"slug":17,"type":14},{"name":676,"slug":677,"type":14},{"name":22,"slug":23,"type":14},{"slug":695,"name":695,"fn":696,"description":697,"org":791,"tags":792,"stars":24,"repoUrl":25,"updatedAt":706},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[793,794,795,796],{"name":701,"slug":702,"type":14},{"name":11,"slug":8,"type":14},{"name":664,"slug":665,"type":14},{"name":22,"slug":23,"type":14},{"slug":606,"name":606,"fn":708,"description":709,"org":798,"tags":799,"stars":24,"repoUrl":25,"updatedAt":715},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[800,801,802],{"name":11,"slug":8,"type":14},{"name":676,"slug":677,"type":14},{"name":22,"slug":23,"type":14},{"slug":4,"name":4,"fn":5,"description":6,"org":804,"tags":805,"stars":24,"repoUrl":25,"updatedAt":26},{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[806,807,808,809],{"name":11,"slug":8,"type":14},{"name":16,"slug":17,"type":14},{"name":22,"slug":23,"type":14},{"name":19,"slug":20,"type":14},{"slug":811,"name":811,"fn":812,"description":813,"org":814,"tags":815,"stars":24,"repoUrl":25,"updatedAt":822},"sdaf-orientation-and-surface","orient users to SDAF architecture","Orient a newcomer to the SAP Deployment Automation Framework (SDAF): explain the spine (control plane → workload zone → SAP system → software → install → operate\u002Fremove), summarise the three execution surfaces (Local, Azure DevOps, GitHub Actions), and print the install command for the matching surface bootstrap plugin — as documented in this repository's `docs\u002FPLUGINS.md` — so the operator can run it manually. Use when a user says \"what is SDAF\", \"how is SDAF structured\", \"where do I start with SDAF\", \"which surface should I use\", \"SDAF Local vs ADO vs GitHub\", \"workstation vs Azure Pipelines vs GitHub workflows\", \"how do I install the SDAF ADO\u002FGitHub plugin\", or \"I'm new to SDAF\". Do NOT use for readiness pre-flight (see sdaf-readiness-check), workspace\u002Ftfvars layout (see sdaf-workspace-and-tfvars), or troubleshooting a failed run (see sdaf-failure-triage).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[816,817,818,821],{"name":701,"slug":702,"type":14},{"name":11,"slug":8,"type":14},{"name":819,"slug":820,"type":14},"Documentation","documentation",{"name":22,"slug":23,"type":14},"2026-09-02T07:46:52.116557",{"slug":824,"name":824,"fn":825,"description":826,"org":827,"tags":828,"stars":24,"repoUrl":25,"updatedAt":842},"sdaf-plan-and-test-semantics","manage SDAF plan and test semantics","Explain SDAF plan-only \u002F test \u002F apply semantics without pretending they are universal. Compares the documented Local commands, Azure DevOps wrapper pipelines, and GitHub Actions workflows for control plane, workload zone, and SAP system: local stage commands show Terraform plans and then apply after approval; ADO\u002FGitHub workload-zone and SAP-system test runs stop after the plan; the current hosted control-plane test options do not provide a plan-only run. Use when a user says \"what does test do in SDAF\", \"is this a real dry run\", \"plan-only vs apply\", \"workflow 01 dry-run\", \"pipeline 02 test\", or \"TEST_ONLY\". Do NOT use to actually deploy a stage or to triage a failed run (see sdaf-control-plane-bootstrap \u002F sdaf-workload-zone \u002F sdaf-sap-system \u002F sdaf-failure-triage).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[829,832,833,836,839],{"name":830,"slug":831,"type":14},"Automation","automation",{"name":11,"slug":8,"type":14},{"name":834,"slug":835,"type":14},"Azure DevOps","azure-devops",{"name":837,"slug":838,"type":14},"CI\u002FCD","ci-cd",{"name":840,"slug":841,"type":14},"GitHub Actions","github-actions","2026-09-02T07:48:08.951811",{"slug":844,"name":844,"fn":845,"description":846,"org":847,"tags":848,"stars":24,"repoUrl":25,"updatedAt":855},"sdaf-quality-assurance","validate deployed SDAF SAP systems","Validate a deployed SDAF SAP system through the SDAF-owned QA entry points: the local quality-assurance menu and the documented Azure DevOps pipeline 13 path. Choose configuration checks vs functional tests, apply `TEST_GROUPS` \u002F `TEST_CASES` safely, interpret `quality_assurance\u002F` and `logs\u002F`, and enforce the documented boundary that the GitHub Actions wrapper is still pending. Use when a user says \"run quality assurance\", \"run configuration checks\", \"pipeline 13 QA\", \"offline HA validation\", or \"why does the report say No test results found\". Do NOT use to deploy the SAP system or generate `sap-parameters.yaml` \u002F `\u003CSID>_hosts.yaml` (see `sdaf-sap-system`), or for a generic failed-run report with no QA-stage context (see `sdaf-failure-triage`).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":11},[849,850,851,854],{"name":830,"slug":831,"type":14},{"name":11,"slug":8,"type":14},{"name":852,"slug":853,"type":14},"Quality Assurance","quality-assurance",{"name":22,"slug":23,"type":14},"2026-09-02T07:46:49.932123",145]