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.Ruby/AGENTS.md

@@ -0,0 +1,29 @@
+# Scanner Ruby Analyzer Guild Charter
+
+## Mission
+Provide deterministic Ruby analyzers that interpret bundler/gemspec ecosystems, build dependency graphs, and surface runtime metadata for Scanner SBOM generation. Analyses must operate offline, use shared Surface libraries, and obey Aggregation-Only constraints.
+
+## Scope
+- Normaliser, bundler analyzer, and emitters in `StellaOps.Scanner.Analyzers.Lang.Ruby`.
+- Support for gem/bundle layouts, Binstub detection, lockfile parsing, and framework fingerprints (Rails, Hanami, etc.).
+- Integration with Surface.Env/FS/Secrets/Validation.
+- Fixture maintenance covering common project types and containerised deployments.
+
+## 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)
+- Bundler/gemspec references from sprint tasks.
+
+## Working Agreement
+1. **Synchronise task state** in both `docs/implplan/SPRINTS.md` and local `TASKS.md` when starting/finishing work.
+2. **Offline guarantees**: rely on local gems cache/vendor directories; no network fetches; capture provenance for configs.
+3. **Surface alignment**: route environment/cache/secret access via Surface libraries; run shared validators first.
+4. **Deterministic outputs**: maintain stable ordering, normalised paths, and consistent hashing.
+5. **Testing**: extend golden fixtures and determinism harness; cover edge cases (platform-specific gems, native extensions, Binstubs).
+6. **Documentation**: update analyzer notes in implementation plan or add Ruby-focused design doc when behaviour evolves; coordinate with Docs if CLI/UI guides need updates.
+
+- 1. Update task status to `DOING`/`DONE` in both `docs/implplan/SPRINTS.md` and the local `TASKS.md` when you start or finish work.