Repository navigation
release: publish and smoke-test the CyberBattleSim adapter profile #31
Description
Objective
Publish the first installed CyberBattleSim adapter profile that supports the milestone's documented example and reproduction workflow.
Scope
- Integrate the
cyberbattlesimextra, public module, command profile, support/limitations table, source attribution, and example-pack release reference into Release Please. - Build reproducible wheel/sdist artifacts and validate metadata, README rendering, license/notices, imports, entry points, dependency isolation, and source/profile resolution.
- Publish through the existing OIDC Trusted Publishing path.
- From the public index, install
raes-adapters[cyberbattlesim]in a clean supported environment. - Run adapter inspection, pack acquisition/validation, one short episode, conformance smoke, portable-output leakage checks, and artifact validation.
- Publish checksums/attestations, exact source/profile/pack identities, known limitations, and rollback/yank guidance.
Acceptance criteria
- Public-index installation resolves the qualified source profile.
- The example pack short path completes against the released version.
- Installed conformance and leakage smoke checks pass.
- Unrelated extras remain installable/testable according to declared conflicts.
- Release artifacts and documentation contain no simulator-native portable data or unsupported claims.
- The release is linked as an apparatus-readiness sub-issue of RAESystem/research#14.
- Protected branches are resynchronized through the governed reviewed back-merge.
- The CyberBattleSim manual native-readiness protocol is updated for the released adapter profile, run from the public-index installation against the real CyberBattleSim adapter path, and recorded as passing.
Activity
Brad-Edwards commentedon Aug 14, 2026
🛠️ Picked up by /implement - driver codex, branch
31-publish-cyberbattlesim-profile, 2026-08-14T16:46:04.645Z.Brad-Edwards commentedon Aug 14, 2026
gc workflow phase recorded:
preflight(issue #31). Posted by the MCP server to enforce ordering between workflow steps (issue #794 MVP-2). Do not edit or delete — used by downstream tools to gate phase prerequisites.Brad-Edwards commentedon Aug 14, 2026
Execution obligation ISSUE-31-CAPTURE-ADMISSION — Opened
Category: workflow
Observed state: The CyberBattleSim task requires attacker-action-log and availability-series evidence, but RAES 3.3 cannot admit the required field/artifact witnesses; adapter validate/run fail closed before effects. #86 is explicitly blocked pending the naming decision and OpenRAE/rae#1112.
Impact: Issue 31 cannot truthfully complete its required public-index short episode, installed conformance/leakage smoke, or passing native-readiness record, and publication before remediation could create an irreversible release that fails readiness.
Current obligation: Land and publish the upstream RAES capture-capability contract and naming decision, implement #86 against that contract, then resume issue 31's release implementation and public smoke.
Evidence
Brad-Edwards commentedon Aug 14, 2026
Execution obligation ISSUE-31-CAPTURE-ADMISSION — Escalated
Category: workflow
Observed state: The CyberBattleSim task requires attacker-action-log and availability-series evidence, but RAES 3.3 cannot admit the required field/artifact witnesses; adapter validate/run fail closed before effects. #86 is explicitly blocked pending the naming decision and OpenRAE/rae#1112.
Impact: Issue 31 cannot truthfully complete its required public-index short episode, installed conformance/leakage smoke, or passing native-readiness record, and publication before remediation could create an irreversible release that fails readiness.
Current obligation: Land and publish the upstream RAES capture-capability contract and naming decision, implement #86 against that contract, then resume issue 31's release implementation and public smoke.
Evidence
Pause class: hard_external_dependency
Decision request: Unblock and complete OpenRAE/rae#1112 plus the pending naming decision, then authorize/resume #86. Re-run /implement 31 after #86 lands so the release can proceed against an admissible task.
This obligation remains open while the decision is pending.