docs(ci): clarifier la règle temporaire vs persistée pour l'entrypoint

Author: raidos23

docs/ci_cd_ark_cli.md

@@ -8,6 +8,11 @@ Use this document as the single source of truth for ARK CI/CD behavior and examp
 When pipeline behavior changes (flags, exit codes, fail-fast rules, JSON contracts),
 update this page first and keep other references aligned to it.
 
+Scope boundary:
+
+- CI/CD persistence must be explicit through CLI commands (for example `workspace entrypoint-set`).
+- GUI temporary selections are not a CI contract and must not be treated as persisted workspace state.
+
 ## Goal
 
 Automate the following steps for a workspace:
@@ -89,6 +94,12 @@ $ARK_BIN workspace entrypoint-set "$WORKSPACE_DIR" src/main.py --json
 $ARK_BIN workspace entrypoint-clear "$WORKSPACE_DIR" --json
 ```
 
+Important:
+
+- In Engines standalone GUI, selecting a file is a temporary build/session choice.
+- It can read `ARK_Main_Config.yml`, but it does not write entrypoint changes back to config files.
+- For reproducible CI, persist entrypoint only with `workspace entrypoint-set`.
+
 ## Command Breakdown
 
 - `workspace apply --with-venv --strict`

docs/contributing.md

@@ -78,6 +78,7 @@ Release-oriented checks should follow the CLI examples in this guide and the REA
 - If you change the command hierarchy (`gui`, `engine`, `workspace`, `init`, `config-auto`, `check`, `scaffold`) or JSON outputs, update the CLI docs.
 - Keep CI-facing exit codes stable, or document the change explicitly in the README.
 - For CI/CD behavior, keep [`docs/ci_cd_ark_cli.md`](./ci_cd_ark_cli.md) as the single source of truth and align other docs/examples to it.
+- For GUI behavior that impacts CI expectations (entrypoint, workspace persistence, engine config), explicitly state whether behavior is temporary session state or persisted workspace state.
 - If you change IDE/classic behavior, update the IDE docs when appropriate.
 
 ## Documentation expectations

docs/dedicated_cli.md

@@ -104,4 +104,7 @@ ark-cli> exit
 - When a GUI command is executed (`main`, `bcasl`, `engines`), control returns to the prompt after the GUI is closed.
 - If Rich is installed, output is colorized. If not, the CLI still works in plain mode.
 - `engine compile` validates the target file path before running the engine command.
+- In Engines standalone GUI, file selection is temporary for the current build/session.
+- Engines standalone GUI may read workspace config (`ARK_Main_Config.yml`) but does not persist entrypoint changes.
+- To persist entrypoint in workspace config, use `workspace entrypoint-set`.
 - For automation, prefer the top-level commands documented in the README (`engine`, `workspace`, `doctor`, `scaffold`, `gui`).