Skip to content

Status slide: generated progress.svg (owner-reviewed design) in the CICS-to-Java README, refreshed nightly #5286

Closed

Description

@squid-protocol

Owner-approved 2026-10-16: "lets post this". This includes the workflow edit below: a nightly schedule.

Turn the owner-reviewed prototype into a generated SVG that the CICS-to-Java README shows as a picture.

Prototype (reviewed design, two rounds of owner feedback): /srv/storage_16tb/projects/gitgalaxy/handoffs/progress-slide-prototype/

  • render_slide.py, stdlib only;
  • the inputs it ran on: progress.json, cobolrt_rules.json, milestones.json, issue_counts.json;
  • the output, slide.svg, plus light and dark screenshots.

Keep the design exactly: section order, the level and status colours (validated for colour-vision deficiency in both modes), the level and status definitions, segment labels like "L3 · 13", the total row aligned with the cobolrt family bars, and the big numbers in the runtimes rows.

Do

  1. Port it to tests/tools/progress_slide.py, rendering docs/language_status/progress.svg as a generated_docs.PAGES entry on the generated branch, next to progress.md.
  2. README: in gitgalaxy/tools/cobol_to_java/README.md (and the CICS-to-Java section of README.md), add the picture linking to the full page: [![CICS to Java: where we stand](https://raw.githubusercontent.com/squid-protocol/gitgalaxy/generated/docs/language_status/progress.svg)](<the generated progress.md link #5281 uses>). Keep test_evidence_report_single_source.py and Generated progress page: burned-estate ladder, components, eras, burn-down, Gap Atlas; READMEs link it (Part of #5280) #5281's README guard green; extend them for the image link if needed, and say why.
  3. Refresh: add schedule: - cron: "17 5 * * *" (nightly) to .github/workflows/generated-docs.yml, next to the existing push trigger and path filter. Add the new inputs to the path filter. A docs run on main re-renders the page and the SVG.
  4. Tests:
    • it renders from fixtures, and the output is valid XML;
    • every number on the slide equals the matching progress.json value;
    • the offline "not measured" path;
    • both colour schemes are present;
    • the image link in the README.

Acceptance: after merge, the generated branch has progress.svg, both READMEs show it, the nightly run re-renders it, and the gates are green.

Metadata

Metadata

Assignees

No one assigned

    Labels

    scope:infraCI, tooling, churn/factory, docs infrastructuretier:customerChurn tier 2: front-facing customer items

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions