Introduce Vexer platform scaffolding and enrich Concelier merge
This commit is contained in:
		| @@ -42,6 +42,10 @@ Legend: ✅ complete, ⚠️ in progress/partial, ❌ not started. | ||||
| - Merge now emits `feedser.merge.normalized_rules` (tags: `package_type`, `scheme`) and `feedser.merge.normalized_rules_missing` (tags: `package_type`). Track these counters to confirm normalized arrays land as connectors roll out. | ||||
| - Expect `normalized_rules_missing` to trend toward zero as each connector flips on normalized output. Investigate any sustained counts by checking the corresponding module `TASKS.md`. | ||||
|  | ||||
| ## Implementation tips | ||||
|  | ||||
| - When a connector only needs to populate `AffectedPackage.NormalizedVersions` (without reusing range primitives), call `SemVerRangeRuleBuilder.BuildNormalizedRules(rawRange, patchedVersion, note)` to project the normalized rule list directly. This avoids re-wrapping `SemVerRangeBuildResult` instances and keeps provenance notes consistent with the shared builder. | ||||
|  | ||||
| ## How to use this dashboard | ||||
|  | ||||
| 1. Before opening a connector PR, update the module `TASKS.md` entry and drop a short bullet here (status + timestamp). | ||||
|   | ||||
		Reference in New Issue
	
	Block a user