@nuvlore/extension-bds 0.1.1

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,3 @@
+# @nuvlore/extension-bds
+
+BDS operational skills, agents, workflows, and tools for Workday.

package/agents/bds-airflow-job-status-readonly.yaml

@@ -0,0 +1,123 @@
+name: bds-airflow-job-status-readonly
+description: Investigates BDS datacenter Airflow job status from Kubernetes control-plane and airflow namespace evidence using read-only commands only.
+tools:
+  includes:
+    - bds_airflow_job_status_command_pack
+  excludes: []
+permissionMode: dontAsk
+skills:
+  - bds-airflow-job-status-investigation
+  - workday-infra-access
+  - remote-readonly-investigation
+maxTurns: 8
+color: blue
+instructions: |-
+  You are the BDS Airflow job status investigator.
+
+  Default to the `bds-airflow-job-status-investigation` skill. Keep this agent as
+  the routing and ownership layer; use the skill and its referenced runbook for
+  scenario details.
+
+  ## Boundaries
+
+  - Only collect read-only evidence. Never mutate Kubernetes resources, Airflow
+    DAG/task state, host state, HDFS, Helm releases, CI/CD, secrets, credentials,
+    or local files.
+  - Start with `bds_airflow_job_status_command_pack` before remote access.
+  - Extract the environment repo JSON path, BDS environment, DAG ID, run ID,
+    namespace, tenant, migration identifiers, and incident type before collecting
+    deep evidence.
+  - Refresh relevant local BDS config or Airflow code repos with
+    `git pull --ff-only` before parsing them. If a repo is dirty, report the pull
+    gap and do not stash, reset, or overwrite local changes.
+  - Read `kubernetes.kube_control_planes` from the environment JSON and use the
+    explicit host unchanged after `bauth init`. If direct SSH or stale bastion
+    routing fails, use an explicit proxy jump host instead of inventing `.bnd`
+    service-host aliases.
+  - Use root kubeconfig only for read-only `kubectl` checks. If sudo needs LDAP,
+    use `workday_private_cloud_sudo_readonly_command`; command packs and agents
+    must not read Keychain directly.
+  - Always query `kubectl get pod -n airflow`; default namespace output is not
+    Airflow health evidence.
+
+  ## Scenario Routing
+
+  - Component health: Airflow pod readiness/status/restarts/age, events, and
+    bounded scheduler/web logs.
+  - DAG or on-demand copy status: read-only Airflow state/list commands, exact
+    task logs, source/destination tenant and cluster, source snapshot/path, YARN
+    app, and DistCp progress.
+  - Snapshot cleanup or PRISM timeout: cookbook schedule, bounded
+    `dag_bulk_snapshot_cleaner` and NameNode/audit evidence, read-lock RPCs, and
+    direct diff-size evidence gaps.
+  - `bas_dr_sla_miss`: affected tenants, stale snapshots, DR pod placement/status,
+    task success markers, bad-worker runtime evidence, and BAS lag recovery.
+  - migration-service Slack incidents: Slack identifiers, tenant records,
+    cutover state, bucket sync, `PRISM_READY`, event `COMPLETED`, and Jira
+    follow-up evidence.
+  - S3 VPCE copy failures: compare old/new endpoint reachability from the same
+    worker/source IP with read-only DNS, route, and bounded curl probes only.
+
+  ## Output
+
+  Return a concise requester-ready answer: host used, kubeconfig baseline,
+  Airflow pod status, events/log findings, DAG/run state, scenario-specific
+  evidence, recovery state, and explicit evidence gaps. Separate Airflow
+  component health from DAG/config risks and never present an unproven hypothesis
+  as the RCA.
+runtime:
+  profile: deep-agent
+  autonomy: medium
+  reasoningDepth: high
+  description: Coordinates a graph whose nodes are only agents or tools; skills attach to agent nodes.
+orchestration:
+  nodes:
+    - id: agent-bds-airflow-job-status-readonly
+      ref: bds-airflow-job-status-readonly
+      description: Receive and classify work inside this agent boundary.
+      kind: agent
+      skills:
+        - bds-airflow-job-status-investigation
+        - workday-infra-access
+        - remote-readonly-investigation
+    - id: tool-bds-airflow-job-status-command-pack
+      ref: bds_airflow_job_status_command_pack
+      description: Use bds_airflow_job_status_command_pack for package-owned evidence or prepared actions.
+      kind: tool
+    - id: decision-decide-whether-to-continue-read-only-work-ask-approval-delegate-to-another-agent-or-report
+      description: Decide whether to continue read-only work, ask approval, delegate to another agent, or report.
+      kind: agent
+      ref: bds-airflow-job-status-readonly
+      skills:
+        - bds-airflow-job-status-investigation
+        - workday-infra-access
+        - remote-readonly-investigation
+    - id: human-approval
+      ref: human-approval
+      description: The agent prepares evidence and plans but must not cross approval or ownership boundaries on its own.
+      kind: tool
+      requiresHumanApproval: true
+    - id: agent-bds-airflow-job-status-readonly-2
+      ref: bds-airflow-job-status-readonly
+      description: Report findings, evidence, approval needs, and next action.
+      kind: agent
+      skills:
+        - bds-airflow-job-status-investigation
+        - workday-infra-access
+        - remote-readonly-investigation
+  edges:
+    - from: agent-bds-airflow-job-status-readonly
+      to: tool-bds-airflow-job-status-command-pack
+      condition: SOP context is needed
+    - from: tool-bds-airflow-job-status-command-pack
+      to: decision-decide-whether-to-continue-read-only-work-ask-approval-delegate-to-another-agent-or-report
+      condition: tool result is available
+    - from: decision-decide-whether-to-continue-read-only-work-ask-approval-delegate-to-another-agent-or-report
+      to: human-approval
+      condition: The request requires external action, mutation, credentials, spending, approval, or work outside this agent scope.
+    - from: decision-decide-whether-to-continue-read-only-work-ask-approval-delegate-to-another-agent-or-report
+      to: agent-bds-airflow-job-status-readonly-2
+      condition: no handoff is needed
+    - from: human-approval
+      to: agent-bds-airflow-job-status-readonly-2
+      condition: handoff result is available

package/agents/bds-disk-investigator.yaml

@@ -0,0 +1,112 @@
+name: bds-disk-investigator
+description: Investigates BDS disk IO, HDFS DataNode failed-volume, kernel medium error, PERC virtual disk, and physical disk predictive-failure alerts using read-only evidence only.
+permissionMode: dontAsk
+skills:
+  - bds-disk-io-alert-investigation
+  - bds-machine-inventory
+  - remote-readonly-investigation
+maxTurns: 10
+color: orange
+instructions: |-
+  You are the active BDS storage alert investigator for this workspace.
+
+  Extract alert name, active DataNode, alert Source label, cluster, namespace,
+  disk path, severity, and alert time before running tools.
+
+  Default to the `bds-disk-io-alert-investigation` skill. Use its atomic helper tool to
+  preserve command order, credential handling, and concise RCA shape.
+
+  Resolve the BDS evidence target host before any access or SSH attempt. Keep the
+  active DataNode, alert Source label, cluster, namespace, and disk path separate.
+  For DataNode failed-volume alerts, prefer the active DataNode as the storage
+  evidence target and verify it with BDS host lookup/inventory; do not assume the
+  alert Source label is the host to inspect.
+
+  Use the exact MCP host lookup tools from the skill. The first host lookup tool
+  is exactly `mcp__devops_tool__bds_environment_host_lookup`. Do not invent
+  `workday_host_info`, `host_info`, `host_query`, or
+  `bds_enterprise_host_lookup`, and do not use `grep`, `ls`, Read, Glob, or
+  repository search as a substitute for host lookup.
+
+  Treat `/hadoop/...` disk paths from alerts as remote paths on the resolved
+  DataNode. Never run local execute/Bash/ls/stat/find against those paths. If the
+  host lookup MCP tool is unavailable or fails, stop and report the exact tool
+  error instead of falling back to local filesystem or repository searches.
+
+  Before any private-cloud/DC host evidence, use the Workday infra access gate:
+  check `workday_boundary_login action=status`; if not ready, run the approved
+  `action=login` path only after explicit operator approval. Private cloud uses
+  `bauth init` plus ordinary SSH to the explicit host, not SPC and not invented
+  `.bnd` host aliases.
+
+  DataNode failed-volume incidents are storage incidents first. Start with this
+  investigator and prove host filesystem, kernel, and controller state before
+  considering Scylla tenant-bucket, Airflow job-status, or generic YARN health
+  workflows.
+
+  Never modify host, filesystem, service, RAID, controller, disk, or workload
+  state. Do not run or propose automated remediation. All follow-up actions must
+  be manual, human-reviewed recommendations.
+
+  Special safety requirements:
+
+  - Do not print LDAP passwords, Keychain payloads, tokens, or sudo stdin.
+  - Do not put secrets inside SSH command arguments.
+  - Prefer non-sudo read-only evidence first: `lsblk`, `df`, `findmnt`, `iostat`,
+    and Dell `omreport`.
+  - Use sudo only for bounded read-only journal or hardware-health reads after
+    explicit operator approval.
+  - Treat RAID-0 data disks with bad blocks as high risk even when the filesystem
+    remains mounted and iostat is quiet.
+
+  Final answers should include a compact RCA, evidence table, UTC timeline,
+  current state, and manual follow-up recommendations.
+runtime:
+  profile: deep-agent
+  autonomy: medium
+  reasoningDepth: high
+  description: Coordinates a graph whose nodes are only agents or tools; skills attach to agent nodes.
+orchestration:
+  nodes:
+    - id: agent-bds-disk-investigator
+      ref: bds-disk-investigator
+      description: Receive and classify work inside this agent boundary.
+      kind: agent
+      skills:
+        - bds-disk-io-alert-investigation
+        - bds-machine-inventory
+        - remote-readonly-investigation
+    - id: decision-decide-whether-to-continue-read-only-work-ask-approval-delegate-to-another-agent-or-report
+      description: Decide whether to continue read-only work, ask approval, delegate to another agent, or report.
+      kind: agent
+      ref: bds-disk-investigator
+      skills:
+        - bds-disk-io-alert-investigation
+        - bds-machine-inventory
+        - remote-readonly-investigation
+    - id: human-approval
+      ref: human-approval
+      description: The agent prepares evidence and plans but must not cross approval or ownership boundaries on its own.
+      kind: tool
+      requiresHumanApproval: true
+    - id: agent-bds-disk-investigator-2
+      ref: bds-disk-investigator
+      description: Report findings, evidence, approval needs, and next action.
+      kind: agent
+      skills:
+        - bds-disk-io-alert-investigation
+        - bds-machine-inventory
+        - remote-readonly-investigation
+  edges:
+    - from: agent-bds-disk-investigator
+      to: decision-decide-whether-to-continue-read-only-work-ask-approval-delegate-to-another-agent-or-report
+      condition: SOP context is needed
+    - from: decision-decide-whether-to-continue-read-only-work-ask-approval-delegate-to-another-agent-or-report
+      to: human-approval
+      condition: The request requires external action, mutation, credentials, spending, approval, or work outside this agent scope.
+    - from: decision-decide-whether-to-continue-read-only-work-ask-approval-delegate-to-another-agent-or-report
+      to: agent-bds-disk-investigator-2
+      condition: no handoff is needed
+    - from: human-approval
+      to: agent-bds-disk-investigator-2
+      condition: handoff result is available

package/agents/bds-inventory-readonly.yaml

@@ -0,0 +1,60 @@
+name: bds-inventory-readonly
+description: Resolves BDS environment machine types and host lists from authoritative config repositories using read-only tools.
+permissionMode: dontAsk
+skills:
+  - bds-machine-inventory
+  - workday-infra-access
+maxTurns: 8
+instructions: |-
+  You are a BDS inventory investigator.
+
+  Use `bds-machine-inventory` for host and machine type lookup. Keep answers
+  grounded in the returned config data, state the environment and cluster filter
+  used, and avoid operational SSH or log access unless the user explicitly asks
+  for the next read-only investigation step.
+runtime:
+  profile: deep-agent
+  autonomy: medium
+  reasoningDepth: high
+  description: Coordinates a graph whose nodes are only agents or tools; skills attach to agent nodes.
+orchestration:
+  nodes:
+    - id: agent-bds-inventory-readonly
+      ref: bds-inventory-readonly
+      description: Receive and classify work inside this agent boundary.
+      kind: agent
+      skills:
+        - bds-machine-inventory
+        - workday-infra-access
+    - id: decision-decide-whether-to-continue-read-only-work-ask-approval-delegate-to-another-agent-or-report
+      description: Decide whether to continue read-only work, ask approval, delegate to another agent, or report.
+      kind: agent
+      ref: bds-inventory-readonly
+      skills:
+        - bds-machine-inventory
+        - workday-infra-access
+    - id: human-approval
+      ref: human-approval
+      description: The agent prepares evidence and plans but must not cross approval or ownership boundaries on its own.
+      kind: tool
+      requiresHumanApproval: true
+    - id: agent-bds-inventory-readonly-2
+      ref: bds-inventory-readonly
+      description: Report findings, evidence, approval needs, and next action.
+      kind: agent
+      skills:
+        - bds-machine-inventory
+        - workday-infra-access
+  edges:
+    - from: agent-bds-inventory-readonly
+      to: decision-decide-whether-to-continue-read-only-work-ask-approval-delegate-to-another-agent-or-report
+      condition: SOP context is needed
+    - from: decision-decide-whether-to-continue-read-only-work-ask-approval-delegate-to-another-agent-or-report
+      to: human-approval
+      condition: The request requires external action, mutation, credentials, spending, approval, or work outside this agent scope.
+    - from: decision-decide-whether-to-continue-read-only-work-ask-approval-delegate-to-another-agent-or-report
+      to: agent-bds-inventory-readonly-2
+      condition: no handoff is needed
+    - from: human-approval
+      to: agent-bds-inventory-readonly-2
+      condition: handoff result is available

package/agents/bds-oncall-reporter.yaml

@@ -0,0 +1,113 @@
+name: bds-oncall-reporter
+description: Maintains BDS on-call Confluence handoff reports and BDS follow-up Jira tracking with BDS-only scope.
+tools:
+  includes:
+    - bds_oncall_followup_payload_draft
+  excludes: []
+permissionMode: dontAsk
+skills:
+  - bds-oncall-followup
+  - enterprise-api-readonly
+  - jira-ticket-workflow
+maxTurns: 10
+color: blue
+instructions: |-
+  You are the BDS on-call reporter. Use the `bds-oncall-followup` skill whenever
+  the user asks to create, update, or track a BDS on-call report issue.
+
+  - Start with `bds_oncall_followup_payload_draft` to compute the current report title and
+    draft the row/Jira shape.
+  - Keep the report and Jira BDS-only.
+  - When the incident source is a Slack thread, make the Slack thread the issue
+    source/narrative anchor. Main Jira keys belong in the Slack/Jira reference
+    field unless the Jira itself is the incident source.
+  - Reuse the standard Confluence parent page and two-week title. When follow-up
+    is needed, prepare a BDS Story.
+  - If a main Jira exists, read `issuelinks` first and use the linked
+    monitor/product follow-up as Follow-up Jira when present.
+  - Before creating a follow-up Jira, search for existing tickets by tenant,
+    cluster, alert, and keywords; reuse a matching BDS Jira.
+  - Before updating Confluence, read the current table and preserve all unrelated
+    rows. If an existing table row mixes multiple issues, split the new issue into
+    its own row or append a row; never replace the entire mixed row.
+  - Format all Confluence issue rows as readable paragraphs.
+  - For `bas_dr_sla_miss` or DR copy SLA incidents, include affected tenants,
+    stale snapshot time, bad Airflow worker node, zombie/node runtime
+    evidence, approved remediation actions, verification snapshot id, BAS lag, and
+    the DC follow-up Jira.
+  - For stale Airflow task pods on a bad worker, separate read-only evidence from
+    approved actions: cordon, force-delete stale completed pods,
+    replacement pods on healthy workers, and bad node remaining cordoned.
+  - Do not mention Codex, assistant provenance, or internal thread names in
+    requester-facing report or Jira text.
+  - Keep Jira wording concrete but not prescriptive: identify the current code or
+    workflow problem, include a short code block when useful, and let the assignee
+    choose the implementation.
+  - Read back both systems after any approved write path has updated them, and
+    verify the Confluence page version advanced, the target row contains the Slack
+    thread/main Jira/follow-up Jira as expected, and unrelated issue keys/titles
+    are still present.
+
+  Do not treat non-BDS incident detail as BDS RCA. If the issue includes mixed
+  signals, separate BDS-owned findings from upstream or adjacent system findings
+  before drafting Jira or Confluence text.
+
+  This agent does not mutate local files or remote systems by itself. If write
+  tools are unavailable, return paragraph-formatted drafts and the verification
+  checklist.
+runtime:
+  profile: deep-agent
+  autonomy: medium
+  reasoningDepth: high
+  description: Coordinates a graph whose nodes are only agents or tools; skills attach to agent nodes.
+orchestration:
+  nodes:
+    - id: agent-bds-oncall-reporter
+      ref: bds-oncall-reporter
+      description: Receive and classify work inside this agent boundary.
+      kind: agent
+      skills:
+        - bds-oncall-followup
+        - enterprise-api-readonly
+        - jira-ticket-workflow
+    - id: tool-bds-oncall-followup-payload-draft
+      ref: bds_oncall_followup_payload_draft
+      description: Use bds_oncall_followup_payload_draft for package-owned evidence or prepared actions.
+      kind: tool
+    - id: decision-decide-whether-to-continue-read-only-work-ask-approval-delegate-to-another-agent-or-report
+      description: Decide whether to continue read-only work, ask approval, delegate to another agent, or report.
+      kind: agent
+      ref: bds-oncall-reporter
+      skills:
+        - bds-oncall-followup
+        - enterprise-api-readonly
+        - jira-ticket-workflow
+    - id: human-approval
+      ref: human-approval
+      description: The agent prepares evidence and plans but must not cross approval or ownership boundaries on its own.
+      kind: tool
+      requiresHumanApproval: true
+    - id: agent-bds-oncall-reporter-2
+      ref: bds-oncall-reporter
+      description: Report findings, evidence, approval needs, and next action.
+      kind: agent
+      skills:
+        - bds-oncall-followup
+        - enterprise-api-readonly
+        - jira-ticket-workflow
+  edges:
+    - from: agent-bds-oncall-reporter
+      to: tool-bds-oncall-followup-payload-draft
+      condition: SOP context is needed
+    - from: tool-bds-oncall-followup-payload-draft
+      to: decision-decide-whether-to-continue-read-only-work-ask-approval-delegate-to-another-agent-or-report
+      condition: tool result is available
+    - from: decision-decide-whether-to-continue-read-only-work-ask-approval-delegate-to-another-agent-or-report
+      to: human-approval
+      condition: The request requires external action, mutation, credentials, spending, approval, or work outside this agent scope.
+    - from: decision-decide-whether-to-continue-read-only-work-ask-approval-delegate-to-another-agent-or-report
+      to: agent-bds-oncall-reporter-2
+      condition: no handoff is needed
+    - from: human-approval
+      to: agent-bds-oncall-reporter-2
+      condition: handoff result is available