johannesPettersson80

CI and release-gate hardening workflow for truST, including exact pre-push parity, cross-platform test harnesses, and artifact-based release gating.

Use when compiling trust-platform, running just/cargo/npm/VS Code gates, synchronizing local work to the shared Hetzner CPU builder, or reporting remote build/test proof.

IEC 61131-3 Structured Text workflow for compliance, language behavior, spec updates, and IEC decision/deviation classification in truST. Use whenever editing docs/IEC_DECISIONS.md or docs/IEC_DEVIATIONS.md; reject IEC-deviation entries for IEC-silent,…

Use for every trust-platform behavior change, bug fix, refactor, malformed input, runtime safety, VS Code, hardware, docs, or supply-chain task that requires a written specification and a native executable test, including honest red-green or behavior-lock…

Enforce SOLID/KISS/DRY architecture in trust-platform when adding features or refactoring runtime/LSP/IDE/CLI AND xtask gate/proof/validator code. Use for module splits, ownership changes, runtime launcher/control/IO/retain/watchdog/debugger flow, any file…

Use when adding, installing, running, or reviewing automated architecture mapping and bug-finding tools in trust-platform, including architecture-doctor, generated software maps, diagram claim checks,…

Implement and review trust-platform HMI schema/value/write contracts with safety guardrails. Use for MP-050..053 features, runtime HMI APIs, widget mapping, HMI web UI, process pages, writes, or authz behavior.

Enforce trust-platform release hygiene for user-visible changes. Use when implementing features, fixes, CLI/runtime behavior changes, documentation updates reflected in release artifacts, changelog/version sync, or tag/release verification.

Use when working with scena Git state, branches, commits, tags, GitHub issues, pull requests, workflow runs, release publication, or when the user asks to verify local state against GitHub.

Use when preparing scena user-visible changes for release, changing crate metadata, versioning, changelog/release notes, public API stability, cargo publish dry runs, semver checks, or v1.0 release evidence.

Use when compiling scena, running cargo fmt/clippy/test/doc/doctor/publish dry-run, synchronizing local work to the Hetzner CPU builder, or reporting remote build/test proof.

Use when adding or reviewing scena tests, visual proof, browser/WASM checks, headless screenshots, color/capability validation, resource lifetime tests, dirty-state tests, allocation gates, or benchmark evidence.

Use when an LLM needs to build, verify, debug, or iterate on a scena application, scene recipe, viewer, CAD inspection workflow, digital twin, product configurator, dashboard, documentation renderer, or agent verification loop using public scena…

Use when adding, changing, or reviewing scena doctor checks, validation gates, silent-failure prevention, source-derived architecture rules, or checklist enforcement.

Use when implementing or refactoring scena renderer architecture, public API, module ownership, typed handles, resource lifetime, prepare/render lifecycle, surface/context recovery, or native/WASM platform boundaries.

Use when implementing or reviewing glTF/GLB loading, KHR extensions, asset cache/dedup/hot reload, anchors/extras, units, coordinate conversion, animation clips, skinning, morph targets, or import rebinding.