Add §8 to methodology/code-list-strategy.md: why some code-carriers have no
single correct code list (sector-specific choice), the rule that every object
property still declares a range, and how unece:any-code (an abstract open
ConceptScheme with no fixed members) serves as that range while the concrete
list is bound downstream in a JSON-LD context or SHACL profile. Notes the
per-property rdfs:comment guidance and that promoting to a concrete scheme later
is non-breaking.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>