feat(docs): Add comprehensive documentation for Vexer, Vulnerability Explorer, and Zastava modules
- Introduced AGENTS.md, README.md, TASKS.md, and implementation_plan.md for Vexer, detailing mission, responsibilities, key components, and operational notes. - Established similar documentation structure for Vulnerability Explorer and Zastava modules, including their respective workflows, integrations, and observability notes. - Created risk scoring profiles documentation outlining the core workflow, factor model, governance, and deliverables. - Ensured all modules adhere to the Aggregation-Only Contract and maintain determinism and provenance in outputs.
This commit is contained in:
		| @@ -134,13 +134,13 @@ | ||||
| 2. Introduce configuration classes and bind from YAML/environment. | ||||
| 3. Implement nonce store (Redis + in-memory), handler integration, and OpenIddict transaction plumbing. | ||||
| 4. Stamp `cnf.jkt`, audit events, and metrics; update Mongo documents and migrations. | ||||
| 5. Extend docs: `docs/ARCHITECTURE_AUTHORITY.md`, `docs/security/audit-events.md`, `docs/security/rate-limits.md`, CLI/UI references. | ||||
| 5. Extend docs: `docs/modules/authority/architecture.md`, `docs/security/audit-events.md`, `docs/security/rate-limits.md`, CLI/UI references. | ||||
|  | ||||
| **mTLS work-stream** | ||||
| 1. Extend client document/schema and provisioning stores with certificate bindings + sender constraint flag. | ||||
| 2. Configure Kestrel/middleware for optional client certificates and validation service. | ||||
| 3. Update token issuance/introspection to honour certificate bindings and emit `cnf.x5t#S256`. | ||||
| 4. Add auditing/metrics and integration tests (happy path + failure). | ||||
| 5. Refresh operator documentation (`docs/ops/authority-backup-restore.md`, `docs/ops/authority-monitoring.md`, sample `authority.yaml`) to cover certificate lifecycle. | ||||
| 5. Refresh operator documentation (`docs/modules/authority/operations/backup-restore.md`, `docs/modules/authority/operations/monitoring.md`, sample `authority.yaml`) to cover certificate lifecycle. | ||||
|  | ||||
| Both streams should conclude with `dotnet test src/Authority/StellaOps.Authority/StellaOps.Authority.sln` and documentation cross-links so dependent guilds can unblock UI/Signer work. | ||||
|   | ||||
		Reference in New Issue
	
	Block a user