Skip to content

Bootstrap repository readiness artifacts - #61

Open
codepress-dev[bot] wants to merge 1 commit into
masterfrom
codepress/dev@codepress.dev/you-are-orchestrating-repository-7844f333
Open

Bootstrap repository readiness artifacts#61
codepress-dev[bot] wants to merge 1 commit into
masterfrom
codepress/dev@codepress.dev/you-are-orchestrating-repository-7844f333

Conversation

@codepress-dev

@codepress-dev codepress-dev Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Summary

This prepares the repository for dependable CodePress development workflows: pull requests can carry useful frontend screenshots, the React app can be started in a repeatable container, and future sessions have a local verification contract to check the public Home experience.

Technical details

Added generated repository skills for PR screenshots, app-server startup, and local verification. The screenshot workflow maps the single public React route (/) and validates a real Chromium render. The app-server path adds a self-contained Node 18/Yarn 1 image for the legacy Create React App frontend, a root ignore file, and a schema-versioned recipe on port 3000; it deliberately preserves the existing Live Dev Server artifacts and does not pretend the separate legacy Django service has a canonical combined start command. The verify-local skill documents that scope and covers the live HTML shell, JavaScript bundle, public manifest, browser render, and log review.

The main compatibility choice is to run the 2017 CRA toolchain with Node 18 and Yarn 1.22.22, with dependencies installed during image build and the server bound to 0.0.0.0. The remaining reviewer concern is the separate Django 1.11/Pipenv service, which still needs its own runtime/bootstrap decision before it can be included in a full-stack verification path.

Generated with CodePress

Changes

  • Add the generated PR screenshot skill for the public React Home route.
  • Add Dockerfiles and .dockerignore for repeatable CRA app-server startup.
  • Add the app-server recipe and generated start-app-server skill.
  • Add the generated verify-local contract for the frontend surface.

Test plan

  • Run the recipe-backed app server and verify GET / returns HTTP 200 with the CRA HTML shell.
  • Verify GET /static/js/bundle.js and GET /manifest.json return HTTP 200 with the expected content types.
  • Run the local verification skill and confirm Chromium renders the React logo, the Welcome to React heading, and starter content without flow-related log errors.

Open items

  • The generated recipe intentionally targets only the React frontend. The separate Django 1.11 backend remains outside the local contract until a canonical combined start path and compatible runtime are defined.

Authors

Generated with CodePress · View the chat session

Co-authored-by: dev@codepress.dev dev@codepress.dev

Co-authored-by: dev@codepress.dev <dev@codepress.dev>
@codepress-dev codepress-dev Bot added the cp:in-progress CodePress: still being worked on label Aug 6, 2026
@codepress-dev

codepress-dev Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor Author

@codepress /judge-verification can you judge this verification?

Local Verification — django-react-intro

PR Head SHA: 210da28ec4a686380660c65b42fbae86d01be7c2

Environment artifact: /tmp/codepress-qa-verifier-runs/verify-env-no-pr-210da28ec4a686380660c65b42fbae86d01be7c2-setup-20260806T212046Z.json

Diff Trigger Inventory

Surface Location Contract item
Local app-server recipe .codepress/start-app-server/recipe.json 1–6
Container build/runtime Dockerfile, Dockerfile.codepress, .dockerignore 1–5
Verification workflow .claude/skills/verify-local/SKILL.md, .claude/skills/start-app-server/SKILL.md 1–6
CRA public frontend web/ served by the recipe 1–4
Legacy Django/auth surface server/ Explicitly out of scope; not started by this recipe

Verification Contract Results

# Assertion Evidence class Result Details
1 GET / returns an allowed status and CRA HTML shell live-http ✅ PASS Real forward_app_request to container 11636649ed84c97c954926a5378e5be395bf99cb9fa090b1764d90c2db80d6cd: HTTP 200, Content-Type: text/html; charset=UTF-8, CRA shell contains <!doctype html>, #root, /manifest.json, and /static/js/bundle.js. Environment: /tmp/codepress-qa-verifier-runs/verify-env-no-pr-210da28ec4a686380660c65b42fbae86d01be7c2-setup-20260806T212046Z.json.
2 GET /static/js/bundle.js returns JavaScript live-http ✅ PASS Real request returned HTTP 200 with Content-Type: application/javascript; charset=UTF-8 and webpack bundle content beginning with webpackBootstrap. Environment: /tmp/codepress-qa-verifier-runs/verify-env-no-pr-210da28ec4a686380660c65b42fbae86d01be7c2-setup-20260806T212046Z.json.
3 GET /manifest.json returns public CRA JSON live-http ✅ PASS Real request returned HTTP 200 with Content-Type: application/json and valid CRA manifest JSON including short_name: React App, name: Create React App Sample, and start_url. Environment: /tmp/codepress-qa-verifier-runs/verify-env-no-pr-210da28ec4a686380660c65b42fbae86d01be7c2-setup-20260806T212046Z.json.
4 Chromium renders a nonblank Home page with visible welcome content ui-artifact ✅ PASS Real take_app_server_screenshot loaded / in Chromium at 1280×800 after 1000 ms; the 20 KB image visibly shows the React logo, Welcome to React, and the starter content on a nonblank page. The MCP result was returned inline and exposes no filesystem path. Environment: /tmp/codepress-qa-verifier-runs/verify-env-no-pr-210da28ec4a686380660c65b42fbae86d01be7c2-setup-20260806T212046Z.json.
5 Container logs contain no flow-related errors logs ✅ PASS Real get_app_server_logs tail 500 for container 11636649ed84c97c954926a5378e5be395bf99cb9fa090b1764d90c2db80d6cd shows Compiled successfully! and server startup. STDERR contains only Node deprecation and circular-dependency warnings; no error, exception, stack trace, or compile failure related to the flow. Environment: /tmp/codepress-qa-verifier-runs/verify-env-no-pr-210da28ec4a686380660c65b42fbae86d01be7c2-setup-20260806T212046Z.json.
6 Scope declaration for server/Django/auth code-inspection ⚪ NOT COVERED This is a web-only recipe. The separate legacy Django server/auth behavior was not started or claimed as passed because the repository has no canonical combined start command. Environment: /tmp/codepress-qa-verifier-runs/verify-env-no-pr-210da28ec4a686380660c65b42fbae86d01be7c2-setup-20260806T212046Z.json.

Frontend QA

  • Status: PASS for the public CRA Home render.
  • Report: this report.
  • Manifest: not applicable.
  • Artifacts: inline MCP Chromium screenshot from take_app_server_screenshot (20 KB; no filesystem path exposed by the tool).

Log Review

  • Compiled successfully! and CRA development server startup were observed.
  • Warnings: Node http_parser deprecation and legacy circular-dependency property warnings. These are warnings only and did not prevent the tested flow.
  • No flow-related errors, exceptions, stack traces, or compile failures observed.

Container

  • ID: 11636649ed84c97c954926a5378e5be395bf99cb9fa090b1764d90c2db80d6cd
  • Reused from the supplied matching-head environment artifact.
  • Stopped: yes; stop_app_server returned Container 11636649ed84 stopped and removed.

Scope

This verification proves the committed readiness artifacts exercise the real public Create React App frontend. Server/Django/auth behavior is not covered by this web-only recipe because there is no canonical combined start command; it is not claimed as passed.

Overall: ✅ PASS

All five in-scope live frontend contract items passed. Item 6 is an explicit scope limitation, not a passing Django/auth assertion.

@lightninglu10 lightninglu10 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

QA verification review: please confirm the generated repository-readiness setup PR in the originating CodePress bootstrap session.

@lightninglu10 lightninglu10 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

QA verification review: the generated repository-readiness setup PR is ready for the repository-specific workflow review in the originating CodePress bootstrap session.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cp:in-progress CodePress: still being worked on

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant