Software Development
Penguin Harness Dev
Use when developing PenguinHarness itself — changing packages/{core,server,web,cli,desktop,landing,docs,skills}, the built-in model catalog, the installers or the release workflow; writing or auditing changelog entries; writing a blog post or capturing release screenshots; running the test suite here or, when asked, on another machine; reading a prompt-cache regression out of the core suites; deciding what to do about data already on disk; auditing prose that reads like a leaked authoring session; or changing anything a user sees or reads — a component, a style, UI strings, docs, landing copy — which must not read as AI slop. Covers the two-repo symlink layout, the CI-parity verification chain, the record-and-ship contract, where blog media is hosted, and the seams that are intentional.
- Publisher / source
- Prism-Shadow/penguin-harness (found on GitHub top repositories)
- Upstream record
- Prism-Shadow/penguin-harness
- Version
- Version 1
- Published
- Publication review
- Approved for publication
- Content fingerprint
7a74c5bf5c1fe462f3c3b8fce2661097042845cb37fafac29f2a2707e9e56261