Engineering Standards now focuses on lifecycle phases (0, A, B, D, E).
Literate Programming now owns LP structural invariants including tangle-sync.
Changes:
- Removed check-tangle-sync and *enforcement-rules* from org-skill-engineering-standards.org
- Added check-tangle-sync, *tangle-targets*, *lp-project-root* to org-skill-literate-programming.org
- Updated LP skill to check tangle-sync on file modification actions
- Added literate-programming-tests.lisp with tangle-sync and block-balance tests
- Removed tangle-sync tests from engineering-standards-tests.lisp
- Added check-tangle-sync function to detect stale .lisp files
- Added :tangle-synced to *enforcement-rules*
- Updated .asd to include engineering-standards component
- Added tests for check-tangle-sync (detects stale lisp, passes when synced)
- Added test block to Org file (Phase A: test-first)
- Created tests/engineering-standards-tests.lisp
- Tests exist but can't run - tangled lisp is out of sync
LESSON: This demonstrates the LP workflow failure -
the .lisp file wasn't regenerated when the .org was updated.
The enforcement skill itself should catch this: tangled files
must match Org source.
This is exactly what org-skill-enforcement should block.
