docs: full sweep — verify every sample against real generated output
Documents round-1 fixes #1-#14 (--force and the exit-98 refusal, IR_SYM_001/002
semantics, config path rules, @member member names, validator guards) and corrects
drift that predated them:
- removed the --lang flag, which does not exist; doc stubs are config-driven
- GmRequest and _gm_create_request were missing the _headers parameter
- validators shown as (_inst, _where), actually (__inst__, __where__)
- oneOf/anyOf described via a non-existent IR "Variant" kind; they are validated
- naming: tags are not prepended to operationId names, only to derived fallbacks
- naming: struct members keep the spec name, only arguments are snake_cased
- gm_request_auth_get_token is private (_gm_ prefix)
- cookie params are excluded from signatures, not collected into _cookies
- getting_started told readers to place an obj_gm_core instance; the singleton
helper creates one, so doing both yields two controllers
Details: KnowledgeBase tasks/pending/wiki-full-sweep.md
docs: config-only CLI, validation rules, per-file output paths
- cli_reference: remove the --input/--output/--prefix/--docs direct mode,
which no longer exists. Note that -i is --init. Document the IR validation
codes (IR_OP_001, IR_PATH_001, IR_SYM_001/002) and why operationId is
required. Correct the exit-code table.
- getting_started: new lowerCamelCase config with per-file outputFile, plus a
worked example writing straight into a .yyp tree.
- naming_conventions, home: prefix comes from the config, not --prefix.
The previous pages stated YAML "format is auto-detected from the file
extension", which was untrue at the time and is now correct.
update: new CLI (--config/--init/--input), fix public API names, drop old GMExtensionCodeGen build path
docs: full wiki for GM-SwaggerCodeGen
Covers getting started, CLI reference, generated output (all 8 files),
authentication schemes, cookie jar, response hooks, body converters,
and naming conventions. Matches the GM-ExtensionTools.wiki format.