johannesPettersson80/trust-platform

trust-ci-release-gates

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

trust-remote-builder

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.

trust-lsp-iec

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,…

trust-test-authoring

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…

st-lsp-solid

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…

trust-architecture-automation

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,…

trust-hmi-contracts

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.

trust-release-hygiene

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.

trust-vscode-quality

Implement and verify trust-platform VS Code extension quality gates. Use when adding commands, snippets, webviews, debug flows, extension tests, or CI wiring under editors/vscode.

vscode-capture

Drive and screenshot the real truST VS Code extension. Use for VS Code UI proof, webview/panel screenshots, command-driven extension smoke tests, and browser-visible extension verification.

vscode-ui-acceptance

Maintain and prove truST VS Code UI acceptance journeys. Use for acceptance-board rows, ux_accepted gates, screenshot evidence, journey coverage, and visible workflow review.