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/StellaOps.Scanner.Analyzers.Lang.Deno/AGENTS.md

@@ -0,0 +1,27 @@
+# Scanner Deno Analyzer Guild Charter
+
+## Mission
+Deliver deterministic Deno language analyzers that normalise project inputs, reconstruct module graphs, and surface package/runtime metadata for Scanner’s inventory and usage SBOMs. The analyzers must operate offline, respect the Aggregation-Only Contract, and integrate with shared Surface libraries.
+
+## Scope
+- Normaliser, graph builder, and output emitters under `StellaOps.Scanner.Analyzers.Lang.Deno`.
+- Integration with shared Surface libraries (Surface.Env, Surface.FS, Surface.Secrets, Surface.Validation).
+- Fixtures and determinism harness specific to Deno projects (vendor/cache/npm bridge scenarios).
+- Documentation/comments explaining resolution rules and limitations.
+
+## Required Reading
+- `docs/modules/scanner/architecture.md`
+- `docs/modules/scanner/design/surface-env.md`
+- `docs/modules/scanner/design/surface-fs.md`
+- `docs/modules/scanner/design/surface-secrets.md`
+- `docs/modules/scanner/design/surface-validation.md`
+- `docs/modules/scanner/implementation_plan.md` (language analyzer sections)
+- Deno package/docs linked in sprint notes (ensure understanding of import maps, lockfiles, cache behaviour).
+
+## Working Agreement
+1. **State synchronisation**: update task status to `DOING`/`DONE` in both `docs/implplan/SPRINTS.md` and local `TASKS.md` when work starts/finishes.
+2. **Surface integration**: use shared Surface libraries for env detection, cache access, secret retrieval, and validation.
+3. **Deterministic processing**: no network fetches; rely on cached artifacts; stabilise ordering and timestamps.
+4. **SBOM contract**: populate component data (PURLs, versions, relationships) without deriving policy decisions.
+5. **Testing**: extend golden fixtures, determinism harness, and property tests before merging changes.
+6. **Docs & handoff**: update analyzer notes in `docs/modules/scanner/implementation_plan.md` or contribute a Deno-specific design note when behaviour changes.