http service with health, extension listing, profile validation, run planning, async run jobs, job inspection, and report retrieval

docs/CONTAINER.md

@@ -102,14 +102,17 @@ preflight runner, command wrapper, and mappings. It does not include the final
 Apache Chemistry TCK dependency graph. A future CMIS image should add Java/Maven
 and document how the OpenCMIS TCK artifacts are resolved or mounted.
 
-## Service Path
+## Service Mode
 
-A service image should call the same CLI contracts used here:
+The current core image can run the local service API through the same entrypoint:
 
-- validate profiles,
-- build run plans,
-- execute runs,
-- read run metadata, evidence, reports, retention summaries, trends, and gates.
+```sh
+podman run --rm -p 8080:8080 \
+  -v "$PWD/runs:/runs" \
+  guide-board-core:local \
+  --root /opt/guide-board serve --host 0.0.0.0 --port 8080
+```
 
-The service layer may add job tracking and HTTP transport, but it should not
-create separate execution semantics.
+The service layer adds in-memory job tracking and HTTP transport. Execution
+semantics remain the CLI/core semantics documented in
+`docs/LOCAL-SERVICE-API.md`.