git:20261008.4d1af52 to git:20261008.aabdba6

+ Every fenced `json` or `yaml` block you add or edit in a Markdown file needs a tag after the language in the fence info string: `mirrord` for a complete `mirrord.json`, `mirrord=<schema.path>` for a fragment (for example `json mirrord=feature.db_branches[]`), `mirrord-up` or `mirrord-up=<path>` for `mirrord-up.yaml`, or one of `mirrord-invalid`, `chaos-rule`, `crd`, `helm-values`, `k8s`, `workflow`, `output`, `other` for everything else. Config blocks must parse as strict JSON or YAML, so no `...` placeholders or `//` comments. Fragment paths and root keys are resolved against the synced schemas, so the path must exist and every root key must be a property there. Config blocks are also validated against those schemas, so they must be valid config, not just parse. Run `python3 .github/scripts/check_fence_tags.py` before finishing (install its dependencies, PyYAML, markdown-it-py and jsonschema, first: `python3 -m pip install -r .github/scripts/requirements.txt`). The full tag set, path rule and exempt files are in [CONTRIBUTING.md](CONTRIBUTING.md).