Development updates

The production path gained focused compatibility and failure-mode improvements after the initial deployment foundation.

• Fixed terminal log ordering so runner output remains easier to follow.
• Improved compatibility with the Echo deployment environment.
• Added a branded maintenance fallback for periods when the application is unavailable.

This milestone moved PatchProof from the verification core toward a production-ready operator experience.

• Added operator registration, verification, recovery, workspace roles, invitations, settings, and a first-proof dashboard.
• Added the production container and deployment stack with release checks, queue, scheduler, PostgreSQL, Redis, and durable evidence storage boundaries.
• Added a Gitea verification workflow for Node and Laravel tests plus deterministic brand validation.
• Introduced the PatchProof colour system, themed application shell, and generated brand assets.
• Hardened OPcache runtime verification and aligned CI with the preinstalled Node runtime.

A broad set of small, test-backed changes established the current evidence model and local verification loop.

• Expanded local scan, run, doctor, and report workflows with merge recommendations and structured concerns.
• Added explicit health and browser checks, runner readiness detection, and starter configuration across common language and frontend stacks.
• Added artifact metadata, bounded content upload and download, retention pruning, and proof-level artifact evidence.
• Deepened deterministic rules for dependencies, test integrity, CI, authorization, environment, Docker, and PatchProof policy changes.
• Strengthened redaction across CLI, runner, cloud API, logs, report metadata, URLs, and user-facing summaries.
• Made local reports easier to find and filter by verdict, risk, and changed file while safely ignoring malformed report entries.