Unity-Customer-Template/docs
Frank Harris 28c15035a4
All checks were successful
Code Documentation / code-docs (push) Successful in 6s
Project Report / project-report (push) Successful in 4s
Validate Code / validate (push) Successful in 3s
added unity files
2026-06-15 12:03:33 -05:00
..
ARCHITECTURE.md added unity files 2026-06-15 12:03:33 -05:00
AUTOMATION.md added unity files 2026-06-15 12:03:33 -05:00
CODEX_INSTRUCTIONS.md added unity files 2026-06-15 12:03:33 -05:00
README.md added unity files 2026-06-15 12:03:33 -05:00
REPORTS.md added unity files 2026-06-15 12:03:33 -05:00
REPOSITORY_MAP.md added unity files 2026-06-15 12:03:33 -05:00
VALIDATORS.md added unity files 2026-06-15 12:03:33 -05:00
WORKFLOWS.md added unity files 2026-06-15 12:03:33 -05:00

Customer-Test Documentation

Purpose of Repository

This repository is the master template for Runlevel Systems DevPlus1 customer debugging and analysis projects.

Customers are expected to upload code that may already be broken. The repository automation is designed to inspect that code, generate reports, and keep the workflows green when the automation itself succeeds.

Purpose of DevPlus1 Customer Debugging

DevPlus1 customer debugging projects need fast, repeatable automation that:

  • validates customer code where supported
  • reports errors clearly
  • analyzes project structure
  • generates documentation-friendly markdown output
  • does not confuse customer code problems with automation failures

Repository Goals

  • Make Forgejo Actions useful for debugging projects.
  • Generate reports on every push and pull request when possible.
  • Keep customer code errors visible in logs and markdown.
  • Reserve red workflows for automation failures only.
  • Provide documentation that future Codex sessions can read first.

High-Level Workflow

  1. Customer code is pushed to the repository.
  2. validate.yml runs validation and writes reports/errors.md.
  3. project-report.yml generates structure and flow reports in reports/.
  4. Forgejo logs print report summaries directly.
  5. A developer or future Codex session reviews the reports before deeper work.

Documentation Index