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.

samples/AGENTS.md

@@ -0,0 +1,30 @@
+# Samples Guild Charter
+
+## Mission
+Curate and maintain deterministic sample assets (configs, fixtures, walkthrough projects) that demonstrate StellaOps capabilities across modules. Samples must stay aligned with current APIs, schemas, and offline workflows so other guilds can rely on them for documentation, demos, and regression tests.
+
+## Scope
+- Own sample bundles under `samples/` (configuration packs, walkthrough datasets, tutorial projects).
+- Keep sample instructions in sync with latest component behaviour (Policy Engine, Scanner, CLI, UI, Offline Kit).
+- Provide reproducible scripts to set up, execute, and validate each sample.
+- Coordinate with Docs and DevRel to surface sample updates.
+
+## Required Reading
+- `docs/README.md`
+- `docs/quickstart.md`
+- `docs/09_API_CLI_REFERENCE.md`
+- `docs/modules/platform/architecture-overview.md`
+- `docs/modules/cli/architecture.md`
+- `docs/modules/ui/architecture.md`
+- `docs/modules/scanner/architecture.md`
+- `docs/modules/policy/architecture.md`
+- `docs/modules/export-center/architecture.md`
+- `docs/modules/telemetry/architecture.md` (for observability-focused samples)
+
+## Working Agreement
+1. **Before starting a task** update its status to `DOING` in both `docs/implplan/SPRINTS.md` and `samples/TASKS.md`. Revert to `TODO` if you pause, or `DONE` when complete.
+2. **Review this charter & required docs** to confirm conventions (deterministic outputs, offline readiness, security posture) before coding.
+3. **Preserve determinism**: scripts must pin versions, normalise timestamps, and avoid network calls beyond documented mirrors.
+4. **Documentation parity**: every change to a sample must include README/guide updates explaining execution steps and expected results.
+5. **Cross-guild sign-off**: if a sample depends on another module (e.g., Policy, Scanner), sync with that guild before changing APIs or fixtures.
+6. **Telemetry & cleanup**: ensure sample scripts clean up resources and redact secrets; include telemetry hints where valuable for users.