feature/pp-58-runtime-image-contract (#68)
CICD Start / Sanity and Base Decision (push) Successful in 18s
Renovate Dependency Updates / Renovate Dependencies (push) Failing after 7m19s

## Summary

This PR tightens repository quality enforcement around markdown and documentation. It adds `markdownlint` to the `cicd-checks` workflow, expands pre-commit coverage so markdown files are checked repo-wide, and cleans up the PP-58 documentation set to keep it aligned with the new policy.

## What changed

- Added a `Markdownlint Check` entry to `.gitea/workflows/cicd-checks.yaml`
- Added `markdownlint` to pre-commit and widened prettier coverage to include markdown files across the repo
- Updated `README.md` to satisfy markdownlint line-length rules
- Normalized the PP-58 documentation set:
  - `docs/DEPLOYABLE_RUNTIME_CONTRACT.md`
  - `docs/adr/ADR003-deployable_runtime_image_contract.md`
  - `docs/DEVELOPMENT.md`
  - `docs/CICD_MULTI_STAGE_BUILD.md`
  - `docs/CICD_TROUBLESHOOTING_GUIDE.md`
  - `docs/SECURE_DOCKER_CICD.md`

## Validation

- `pre-commit run markdownlint --files README.md docs/DEPLOYABLE_RUNTIME_CONTRACT.md`
- `pre-commit run prettier --files README.md docs/DEPLOYABLE_RUNTIME_CONTRACT.md`
- Workflow YAML validation returned no errors

## Notes

This change does not alter application runtime behavior. It only strengthens CI and documentation quality enforcement.

Co-authored-by: copilotcoder <copilotcoder@darkhelm.org>
Reviewed-on: #68
This commit was merged in pull request #68.
This commit is contained in:
2026-06-19 17:00:57 -04:00
co-authored by copilotcoder
parent 48a37b943f
commit 9b742a5a6d
28 changed files with 733 additions and 398 deletions
+9 -7
View File
@@ -6,13 +6,13 @@
## 📊 **Performance Metrics - Validated Results**
| Metric | Before Optimization | After Optimization | Improvement |
|--------|-------------------|------------------|------------|
| **Total Pipeline Time** | 15-25 minutes | 3-5 minutes | **85% faster** |
| **Build Success Rate** | ~70% (various failures) | **100%** | **30% improvement** |
| **E2E Test Reliability** | ~60% (browser issues) | **100%** | **40% improvement** |
| **Resource Efficiency** | High CPU/memory load | Optimized usage | **Significant** |
| **Developer Experience** | Frequent CI failures | Reliable pipeline | **Excellent** |
| Metric | Before Optimization | After Optimization | Improvement |
| ------------------------ | ----------------------- | ------------------ | ------------------- |
| **Total Pipeline Time** | 15-25 minutes | 3-5 minutes | **85% faster** |
| **Build Success Rate** | ~70% (various failures) | **100%** | **30% improvement** |
| **E2E Test Reliability** | ~60% (browser issues) | **100%** | **40% improvement** |
| **Resource Efficiency** | High CPU/memory load | Optimized usage | **Significant** |
| **Developer Experience** | Frequent CI failures | Reliable pipeline | **Excellent** |
## 🔧 **Key Technical Achievements**
@@ -37,6 +37,7 @@
## 🛠️ **Critical Issues Resolved**
### **Build Phase Issues**
1. **✅ README.md Dependency Error**
- **Problem**: Local package build failed during dependency-only phase
- **Solution**: Dummy file creation for minimal package structure
@@ -53,6 +54,7 @@
- **Impact**: 100% reliable frontend dependency management
### **Test Phase Issues**
1. **✅ E2E Docker Pull Complexity**
- **Problem**: Over-engineered retry logic for E2E tests only
- **Solution**: Use same simple approach as all other successful tests