Introduce hybrid execution model for Hash/chilli companion with cloud-first degraded local runner

[ProfRandom92]

Motivation

• Provide a documented hybrid execution model that disables heavy local work when the Windows sandbox is unreliable and falls back to Cloud/GitHub CI.
• Surface a clear hard-stop condition for the local runner (CreateProcessAsUserW failed: 5) so local UI and manifest remain usable while execution is cloud-authoritative.

Description

• Add config/hash-companion/hybrid-execution.yaml which defines model: hybrid, status: degraded_local_runner, local component responsibilities, a hard_stop_conditions entry for the CreateProcessAsUserW failed: 5 failure, a validation_runner configured to target cloud_ci with a local_fallback degraded response, Cloud CI github_actions settings and prohibited_local_actions including mutation of C:\Comptextv7.
• Add docs/hash-companion/hybrid-execution-model.md which documents the hybrid model, local and CI responsibilities, degraded-mode behavior, the validation_runner plan, the CI result contract JSON shape, and the criteria required to re-enable local execution.
• Ensure the config explicitly prevents local validation, retries, builds, tests, and file mutations while the hard-stop condition persists.

Testing

• No automated tests were run as part of this change.

---

Codex Task

[gemini-code-assist]

Code Review

This pull request introduces a hybrid execution model for the Hash/chilli companion architecture, shifting heavy tasks like validation and builds to Cloud/GitHub CI due to local Windows sandbox unreliability. The feedback focuses on ensuring consistency between the configuration file and the architectural documentation, specifically regarding error messages and prohibited local actions. Technical improvements were suggested for YAML formatting and naming conventions. Furthermore, a security recommendation was made to incorporate local sanitization of requests before cloud routing to maintain GDPR compliance as per the project's architectural pillars.

[gemini-code-assist]

For consistency with the documentation (see docs/hash-companion/hybrid-execution-model.md line 112), the message should include the instruction to use Cloud/GitHub CI for authoritative validation.

    message: "Local validation is disabled; use Cloud/GitHub CI for authoritative validation."

[gemini-code-assist]

The formatters action is listed as prohibited in the documentation (line 85) but is missing from this configuration list. Adding it ensures the configuration remains synchronized with the documented policy.

  - tests
  - formatters

[gemini-code-assist]

The entry C:\\Comptextv7_source_behavior_mutation uses double backslashes which are interpreted literally in YAML plain scalars (resulting in C:\\). Additionally, using a snake_case identifier would be more consistent with other items in this list like chilli_pet_asset_mutation.

  - comptextv7_source_behavior_mutation

[gemini-code-assist]

The local environment must be responsible for sanitizing requests before they are routed to the cloud. This is critical for maintaining the 'Privacy by design' pillar and ensuring GDPR/DSGVO compliance as specified in the style guide.

Suggested change

	4. Capture user requests and route them to the cloud-backed execution path.
	4. Capture user requests, perform local sanitization (masking/hashing), and route them to the cloud-backed execution path.

[ProfRandom92]

Proceeding direction confirmed.

Next implementation target after this documentation/config PR:

• Wire the Hash companion manifest and chilli/hatch-pet UI to read config/hash-companion/hybrid-execution.yaml.
• Display degraded local runner status when CreateProcessAsUserW failed: 5 is active.
• Surface Cloud/GitHub CI validation results without attempting local execution.
• Keep local mode status-only until an explicit follow-up architecture decision re-enables local execution.

Scope guard:

• No chilli asset changes.
• No local validation execution.
• No source behavior changes in this PR.
• No cleanup/reset/delete operations.

This PR should remain focused on documenting and configuring the hybrid local UI + cloud execution model.