feat: Add guild charters and task boards for various components

- Introduced guild charters for Scanner Deno, PHP, Ruby, Native, WebService, Java, Surface.Env, Surface.FS, Surface.Secrets, Surface.Validation, UI, Zastava Observer, Zastava Webhook, Zastava Core, and Plugin Platform.
- Each charter outlines the mission, scope, required reading, and working agreements for the respective guilds.
- Created task boards for Surface.Env, Surface.FS, Surface.Secrets, Surface.Validation, and Zastava components to track progress and dependencies.
- Ensured all documents emphasize determinism, offline readiness, security, and integration with shared Surface libraries.

src/RiskEngine/StellaOps.RiskEngine/AGENTS.md

@@ -1,23 +1,33 @@
-# Risk Engine Guild Charter
-
-## Mission
-Design, build, and operate the scoring runtime that computes Risk Scoring Profiles across StellaOps deployments while preserving provenance and explainability.
-
-## Scope
-- Scoring workers, job scheduler, provider registry, caching, and explainability artifacts.
-- Integration with Findings Ledger, Conseiller, Excitator, and Policy Engine.
-- Performance, determinism, and observability of scoring jobs.
-- Air-gapped support through offline factor bundles.
-
-## Definition of Done
-- Scoring jobs execute deterministically with audit trails and explainability payloads.
-- Providers registered with TTLs and health checks; missing data surfaced explicitly.
-- Benchmarks and SLO dashboards in place with incident response runbooks.
-
-## Module Layout
-- `StellaOps.RiskEngine.Core/` — scoring orchestrators, provider contracts, explainability models.
-- `StellaOps.RiskEngine.Infrastructure/` — persistence, caching, provider loading, external data connectors.
-- `StellaOps.RiskEngine.WebService/` — APIs for jobs, results, explanations.
-- `StellaOps.RiskEngine.Worker/` — execution loops, provider refreshers, scoring pipelines.
-- `StellaOps.RiskEngine.Tests/` — unit tests for core/infrastructure services.
-- `StellaOps.RiskEngine.sln` — solution unifying module projects.
+# Risk Engine Guild Charter
+
+## Mission
+Design, build, and operate the scoring runtime that computes Risk Scoring Profiles across StellaOps deployments while preserving provenance and explainability.
+
+## Scope
+- Scoring workers, job scheduler, provider registry, caching, and explainability artifacts.
+- Integration with Findings Ledger, Conseiller, Excitator, and Policy Engine.
+- Performance, determinism, and observability of scoring jobs.
+- Air-gapped support through offline factor bundles.
+
+## Definition of Done
+- Scoring jobs execute deterministically with audit trails and explainability payloads.
+- Providers registered with TTLs and health checks; missing data surfaced explicitly.
+- Benchmarks and SLO dashboards in place with incident response runbooks.
+
+## Module Layout
+- `StellaOps.RiskEngine.Core/` — scoring orchestrators, provider contracts, explainability models.
+- `StellaOps.RiskEngine.Infrastructure/` — persistence, caching, provider loading, external data connectors.
+- `StellaOps.RiskEngine.WebService/` — APIs for jobs, results, explanations.
+- `StellaOps.RiskEngine.Worker/` — execution loops, provider refreshers, scoring pipelines.
+- `StellaOps.RiskEngine.Tests/` — unit tests for core/infrastructure services.
+- `StellaOps.RiskEngine.sln` — solution unifying module projects.
+
+## Required Reading
+- `docs/modules/platform/architecture-overview.md`
+
+## Working Agreement
+- 1. Update task status to `DOING`/`DONE` in both `docs/implplan/SPRINTS.md` and the local `TASKS.md` when you start or finish work.
+- 2. Review this charter and the Required Reading documents before coding; confirm prerequisites are met.
+- 3. Keep changes deterministic (stable ordering, timestamps, hashes) and align with offline/air-gap expectations.
+- 4. Coordinate doc updates, tests, and cross-guild communication whenever contracts or workflows change.
+- 5. Revert to `TODO` if you pause the task without shipping changes; leave notes in commit/PR descriptions for context.