Skip to content

allium-swarm: reports for run 54c0b15d-6adf-4ef3-89ed-ebd989e12ce3#112

Open
refset wants to merge 1 commit into
masterfrom
allium-swarm/reports/54c0b15d-6adf-4ef3-89ed-ebd989e12ce3
Open

allium-swarm: reports for run 54c0b15d-6adf-4ef3-89ed-ebd989e12ce3#112
refset wants to merge 1 commit into
masterfrom
allium-swarm/reports/54c0b15d-6adf-4ef3-89ed-ebd989e12ce3

Conversation

@refset
Copy link
Copy Markdown
Member

@refset refset commented May 1, 2026

allium-swarm reports — run 54c0b15d-6adf-4ef3-89ed-ebd989e12ce3

Auto-generated by stage 05c_publish_reports. Files staged under .allium-swarm/54c0b15d-6adf-4ef3-89ed-ebd989e12ce3/:

  • ci_baseline.json
  • full_report.md
  • juxt-site-full-2013/README.md
  • juxt-site-full-2013/api_behaviour.allium
  • juxt-site-full-2013/core_domain.allium
  • juxt-site-full-2013/data_flows.allium
  • juxt-site-full-2013/data_model.allium
  • juxt-site-full-2013/error_handling.allium
  • juxt-site-full-2013/external_contracts.allium
  • nvd_scan_index.json
  • project_breakdown.json
  • summary_report.md

How to use

  • Do not merge unless you want these reports committed to the default branch. The PR exists for review surface only.
  • The branch will be force-pushed by subsequent stages adding more reports (test_concerns, nvd_upgrades_report, …).
  • Refusing the relevant manual gate via allium-swarm refuse <run-id> <stage-id> aborts the pipeline; the branch and PR remain for inspection.

@refset refset force-pushed the allium-swarm/reports/54c0b15d-6adf-4ef3-89ed-ebd989e12ce3 branch from 8d5d6a0 to 3511ef8 Compare May 5, 2026 08:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant