Skip to content

Move Drawing Board maintenance out of template - #7

Merged
raghubetina merged 1 commit into
mainfrom
codex/drawing-board-maintainer-tools
Sep 26, 2026
Merged

raghubetina merged 1 commit into
mainfrom
codex/drawing-board-maintainer-tools

Conversation

@raghubetina

@raghubetina raghubetina commented Sep 26, 2026 •

Copy link
Copy Markdown
Contributor

Drawing Board currently copies its maintainer tests, image build inputs, and investigation reports into every student template checkout. Move those materials into this existing public image repository under drawing-board/, with explicit candidate paths and a complete file inventory.

The public composite action checks the caller's actual Dev Container, stages external checks only in its disposable checkout, and removes them afterward. Separate image build and verification actions preserve the Board's publication job boundary; ordinary CI never publishes. Dependabot scans all composite action directories.

Validation: current destination contract passed; external source checks pass against the original and cleaned Board; workflow/shell/Node checks and documentation links pass. Local qualification includes two complete installation smokes, an ARM64 image build and runtime smoke, and released-CLI root materialization followed by the generated app's complete CI (77 ordinary and 9 browser examples) with its planning archive removed. The qualification receipt records exact revisions and boundaries, including the initial Service-fixture database cleanup barrier. A subsequent authorized, bounded cleanup succeeded; the database is confirmed absent. Independent code/documentation review is complete, including the focused amendment.

Relates to Drawing Board #54; companion Board #59. Land this destination first, then repin all three Board actions to its merged SHA and require the Board's current-candidate check. After Board integration, update both default Board candidate SHAs in this repository's workflow. Board #48 and Service #762 remain separate. No image publication, release, paid Codespaces trial, or Selenium timeout change was performed.

Students should start with planning and runtime files. Keep template
checks, image sources and qualification reports in the public maintainer
repository so the same candidate remains testable without distributing
the harness.

Preserve separate image build and verification jobs because publication
runs in the build action's post phase.
@raghubetina
raghubetina force-pushed the codex/drawing-board-maintainer-tools branch from c8864ae to aa429f9 Compare September 26, 2026 23:04
@raghubetina
raghubetina marked this pull request as ready for review September 26, 2026 23:06
@raghubetina
raghubetina merged commit 84cf8ec into main Sep 26, 2026
1 check passed
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