Issues are grouped by the layer they affect, making it easier to understand which part of the system each problem belongs to.
Concepts carrying app concerns, conflation of identity spaces, and global mutable state.
Stage gating, failure propagation, registration-order sensitivity, and missing rebuild triggers.
Evidence matching, frame query determinism, failure isolation, and registration semantics.
Previously tracked binary copy and clean-URL reload issues are fixed.
Regex-based template parsing, CLI argument validation, frontmatter detection, and mode validation.
Open issue pages keep the same shape:
The findings cluster around four themes.
| Theme | What it means |
|---|---|
| Concept independence | Concepts should not carry app-specific template or runtime semantics. |
| Sync gating | Success actions must not run just because they appear later in a then list. |
| Engine determinism | Matching, consumption, ordering, and failure handling need sharper invariants. |
| Runtime boundaries | Filesystem and browser-facing adapters should preserve safety and feedback. |
Start with Concept Design for independence problems, or Engine Core for the deepest framework-level bugs.