Skip to content

docs/usermanuals/en/deployment/deploy-targets.md: false claim — The 'What's auto-detected' table covers chat template, stop tokens, max_model_len from model.max_length, quantisation and tensor parall… (DOC-D3B08-010) #260

Open

Description

@cemililik

Wave 1 · theme D1-10: Documentation-only fixes · highest severity High · 1 finding(s) · effort docs fix

Summary

Users rely on detection that never happens and miss the flags that do exist.

Primary finding

DOC-D3B08-010 — docs/usermanuals/en/deployment/deploy-targets.md: false claim — The 'What's auto-detected' table covers chat template, stop tokens, max_model_len from model.max_length, quantisation and tensor parall…

severity High · already tracked: KNOWN-OPEN CLI-10|CLI-14|CLI-15|CLI-16 docs/roadmap/phase-16-trust-surface-hardening.md:619-622

Where. docs/usermanuals/en/deployment/deploy-targets.md:144-154 (Turkish mirror: docs/usermanuals/tr/deployment/deploy-targets.md:152-154) · type: false claim

The document says. The 'What's auto-detected' table covers chat template, stop tokens, max_model_len from model.max_length, quantisation and tensor parallelism; 'You can override any auto-detection with explicit YAML'.

What the code does. generate_deploy_config inspects nothing: no tokenizer, config, GPU or training YAML (deploy.py:218-330). max length comes from --max-length (default 4096). Deploy takes no YAML, as line 127 of the same page says. The flag table (lines 139-142) also omits the real knobs: --system, --max-length, --gpu-memory-utilization, --port, --trust-remote-code, --vendor and --output-format.

Code references. forgelm/deploy.py:218-330, forgelm/cli/subcommands/_deploy.py:16-26

User impact. Users rely on detection that never happens and miss the flags that do exist.

Proposed correction. Delete the table and the YAML sentence. List all deploy flags with their defaults (--max-length 4096, --gpu-memory-utilization 0.90, --port 8080, --vendor aws, --system, --trust-remote-code).

Turkish mirror. the Turkish page has the same error; fix both in the same PR

Acceptance criteria

  • Each statement is re-checked against the code at fix time.
  • Documentation listed above is corrected in English and in its Turkish mirror in the same PR.
  • Every finding in this issue is resolved or explicitly closed with a reason.

Found by the October 2026 ForgeLM code and documentation review against commit cab2947. Code links point at that commit; line numbers may have moved since. Finding IDs (CR-…, DOC-…, TECH-…) are stable references for this backlog.

Metadata

Metadata

Assignees

No one assigned

    Labels

    backlog: knownAlready tracked in docs/roadmapblockedWaits for another issue (see Blocked by); set and removed automatically, never by handdocumentationImprovements or additions to documentationseverity: highWrong behaviour or a false claim users rely onsource: review-2026-10Found by the October 2026 code and documentation reviewwave: 1Roadmap wave 1: high severity, small effort

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions