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/Scanner/__Libraries/StellaOps.Scanner.Diff/AGENTS.md

@@ -1,20 +1,31 @@
-# StellaOps.Scanner.Diff — Agent Charter
-
-## Mission
-Deliver deterministic image-to-image component diffs grouped by layer with provenance signals that power policy previews, UI surfacing, and downstream scheduling.
-
-## Responsibilities
-- Maintain diff computation pipelines for inventory and usage SBOM views.
-- Ensure ordering, hashing, and serialization are stable across runs and hosts.
-- Capture layer provenance, usage flags, and supporting evidence for every change.
-- Provide JSON artifacts and helper APIs consumed by the Scanner WebService, Worker, CLI, and UI.
-
-## Interfaces & Dependencies
-- Consumes normalized component fragments emitted by analyzers and usage signals from EntryTrace.
-- Emits diff models used by `StellaOps.Scanner.WebService` and persisted by `StellaOps.Scanner.Storage`.
-- Shares deterministic primitives from `StellaOps.Scanner.Core` once extended with component contracts.
-
-## Testing Expectations
-- Golden diff fixtures for add/remove/version-change flows.
-- Determinism checks comparing shuffled inputs.
-- Layer attribution regression tests to guard provenance correctness.
+# StellaOps.Scanner.Diff — Agent Charter
+
+## Mission
+Deliver deterministic image-to-image component diffs grouped by layer with provenance signals that power policy previews, UI surfacing, and downstream scheduling.
+
+## Responsibilities
+- Maintain diff computation pipelines for inventory and usage SBOM views.
+- Ensure ordering, hashing, and serialization are stable across runs and hosts.
+- Capture layer provenance, usage flags, and supporting evidence for every change.
+- Provide JSON artifacts and helper APIs consumed by the Scanner WebService, Worker, CLI, and UI.
+
+## Interfaces & Dependencies
+- Consumes normalized component fragments emitted by analyzers and usage signals from EntryTrace.
+- Emits diff models used by `StellaOps.Scanner.WebService` and persisted by `StellaOps.Scanner.Storage`.
+- Shares deterministic primitives from `StellaOps.Scanner.Core` once extended with component contracts.
+
+## Testing Expectations
+- Golden diff fixtures for add/remove/version-change flows.
+- Determinism checks comparing shuffled inputs.
+- Layer attribution regression tests to guard provenance correctness.
+
+## Required Reading
+- `docs/modules/scanner/architecture.md`
+- `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.