Resolve Concelier/Excititor merge conflicts
This commit is contained in:
		
							
								
								
									
										14
									
								
								docs/updates/2025-10-18-docs-guild.md
									
									
									
									
									
										Normal file
									
								
							
							
						
						
									
										14
									
								
								docs/updates/2025-10-18-docs-guild.md
									
									
									
									
									
										Normal file
									
								
							@@ -0,0 +1,14 @@
 | 
			
		||||
# Docs Guild Update — 2025-10-18
 | 
			
		||||
 | 
			
		||||
**Subject:** ADR process + events schema validation shipped  
 | 
			
		||||
**Audience:** Docs Guild, DevEx, Platform Events
 | 
			
		||||
 | 
			
		||||
- Published the ADR contribution guide at `docs/adr/index.md` and enriched the template to capture authorship, deciders, and alternatives. All new cross-module decisions should follow this workflow.
 | 
			
		||||
- Linked the ADR hub from `docs/README.md` so operators and engineers can discover the process without digging through directories.
 | 
			
		||||
- Extended Docs CI (`.gitea/workflows/docs.yml`) to compile event schemas with Ajv (including `ajv-formats`) and documented the local loop in `docs/events/README.md`.
 | 
			
		||||
- Captured the mirror/offline workflow in `docs/ci/20_CI_RECIPES.md` so runners know how to install the Ajv toolchain and publish previews without internet access.
 | 
			
		||||
- Validated `scanner.report.ready@1`, `scheduler.rescan.delta@1`, and `attestor.logged@1` schemas locally to unblock Platform Events acknowledgements.
 | 
			
		||||
 | 
			
		||||
Next steps:
 | 
			
		||||
- Platform Events to confirm Notify/Scheduler consumers have visibility into the schema docs.
 | 
			
		||||
- DevEx to add ADR announcement blurb to the next sprint recap if broader broadcast is needed.
 | 
			
		||||
							
								
								
									
										12
									
								
								docs/updates/2025-10-19-docs-guild.md
									
									
									
									
									
										Normal file
									
								
							
							
						
						
									
										12
									
								
								docs/updates/2025-10-19-docs-guild.md
									
									
									
									
									
										Normal file
									
								
							@@ -0,0 +1,12 @@
 | 
			
		||||
# Docs Guild Update — 2025-10-19
 | 
			
		||||
 | 
			
		||||
**Subject:** Event envelope reference & canonical samples
 | 
			
		||||
**Audience:** Docs Guild, Platform Events, Runtime Guild
 | 
			
		||||
 | 
			
		||||
- Extended `docs/events/README.md` with envelope field tables, offline validation commands, and guidance for optional payload fields.
 | 
			
		||||
- Added canonical sample payloads under `docs/events/samples/` for `scanner.report.ready@1`, `scheduler.rescan.delta@1`, and `attestor.logged@1`; validated them with `ajv-cli` to match the published schemas.
 | 
			
		||||
- Documented the validation loop so air-gapped operators can mirror the CI checks before rolling new event versions.
 | 
			
		||||
 | 
			
		||||
Next steps:
 | 
			
		||||
- Platform Events to embed the canonical samples into their contract tests.
 | 
			
		||||
- Runtime Guild checklist for quieted finding counts & progress hints published in `docs/runtime/SCANNER_RUNTIME_READINESS.md`; gather stakeholder sign-off.
 | 
			
		||||
							
								
								
									
										10
									
								
								docs/updates/2025-10-19-platform-events.md
									
									
									
									
									
										Normal file
									
								
							
							
						
						
									
										10
									
								
								docs/updates/2025-10-19-platform-events.md
									
									
									
									
									
										Normal file
									
								
							@@ -0,0 +1,10 @@
 | 
			
		||||
# Platform Events Update — 2025-10-19
 | 
			
		||||
 | 
			
		||||
**Subject:** Canonical event samples enforced across tests & CI  
 | 
			
		||||
**Audience:** Platform Events Guild, Notify Guild, Scheduler Guild, Docs Guild
 | 
			
		||||
 | 
			
		||||
- Scanner WebService contract tests deserialize `scanner.report.ready@1` and `scanner.scan.completed@1` samples, validating DSSE payloads and canonical ordering via `NotifyCanonicalJsonSerializer`.
 | 
			
		||||
- Notify and Scheduler model suites now round-trip the published event samples (including `attestor.logged@1` and `scheduler.rescan.delta@1`) to catch drift in consumer expectations.
 | 
			
		||||
- Docs CI (`.gitea/workflows/docs.yml`) validates every sample against its schema with `ajv-cli`, keeping offline bundles and repositories aligned.
 | 
			
		||||
 | 
			
		||||
No additional follow-ups — downstream teams can rely on the committed samples for integration coverage.
 | 
			
		||||
							
								
								
									
										5
									
								
								docs/updates/2025-10-19-scanner-policy.md
									
									
									
									
									
										Normal file
									
								
							
							
						
						
									
										5
									
								
								docs/updates/2025-10-19-scanner-policy.md
									
									
									
									
									
										Normal file
									
								
							@@ -0,0 +1,5 @@
 | 
			
		||||
# 2025-10-19 – Scanner ↔ Policy Sync
 | 
			
		||||
 | 
			
		||||
- Scanner WebService now emits `scanner.report.ready` and `scanner.scan.completed` via Redis Streams when `scanner.events.enabled=true`; DSSE envelopes are embedded verbatim to keep Notify/UI consumers in sync.
 | 
			
		||||
- Config plumbing introduces `scanner:events:*` settings (driver, DSN, stream, publish timeout) with validation and Redis-backed publisher wiring.
 | 
			
		||||
- Policy Guild coordination task `POLICY-RUNTIME-17-201` opened to track Zastava runtime feed contract; `SCANNER-RUNTIME-17-401` now depends on it so reachability tags stay aligned once runtime endpoints ship.
 | 
			
		||||
							
								
								
									
										8
									
								
								docs/updates/2025-10-19-scheduler-storage.md
									
									
									
									
									
										Normal file
									
								
							
							
						
						
									
										8
									
								
								docs/updates/2025-10-19-scheduler-storage.md
									
									
									
									
									
										Normal file
									
								
							@@ -0,0 +1,8 @@
 | 
			
		||||
# Scheduler Storage Update — 2025-10-19
 | 
			
		||||
 | 
			
		||||
**Subject:** Mongo bootstrap + canonical fixtures  
 | 
			
		||||
**Audience:** Scheduler Storage Guild, Scheduler WebService/Worker teams
 | 
			
		||||
 | 
			
		||||
- Added `StellaOps.Scheduler.Storage.Mongo` bootstrap (`AddSchedulerMongoStorage`) with collection/index migrations for schedules, runs (incl. TTL), impact snapshots, audit, and locks.
 | 
			
		||||
- Introduced Mongo2Go-backed tests that round-trip the published scheduler samples (`samples/api/scheduler/*.json`) to ensure canonical JSON stays intact.
 | 
			
		||||
- `ISchedulerMongoInitializer.EnsureMigrationsAsync` now provides the single entry point for WebService/Worker hosts to apply migrations at startup.
 | 
			
		||||
		Reference in New Issue
	
	Block a user