v1.1.2 — RAG improvement for unknown fields & ConfigMap externalization

What's Changed

Bug Fix: RAG now consulted for unknown fields

Previously, when a dropped field was not in fixable_typos, the rag_lookup node was skipped entirely. This meant escalation messages relied solely on LLM training knowledge (confidence: medium). RAG is now queried for unknown fields as well, providing explicit correct field names from the knowledge base — raising confidence to high and improving Slack alert quality for human operators.

Feature: agent_config.yaml externalized as K8s ConfigMap

agent_config.yaml (fixable_typos, PLMN whitelist, vendor_fields) is now mounted into the pod via a K8s ConfigMap rather than baked into the Docker image. Config-only changes (adding typos, updating PLMN whitelist) now require only:

kubectl apply -f k8s/aiops/agent-config.yaml && kubectl rollout restart deployment/aiops-worker -n aiops

No image rebuild needed.

Config: expand fixable_typos

• Added NfSetIdLists (capital N variant of nfSetIdLists)
• Added localities (plural typo of locality)

Knowledge Accumulation Workflow (validated)

This release validates the end-to-end fault discovery → RAG accumulation → auto-fix promotion workflow:

1. New unknown field detected → RAG queried → Slack escalation with correct field name suggested
2. Operator confirms → adds field to fixable_typos ConfigMap (no rebuild)
3. Next occurrence → auto-fixed automatically