[Wave 3] Medium — Docs: docs/usermanuals/tr/deployment/

Wave 3 · 1 finding(s) in 1 fix package(s). Documents with fewer than five findings each in this wave, grouped by directory.

Findings

DOC-BNEG-008 (docs, Medium) — docs/usermanuals/tr/deployment/deploy-targets.md: wrong detail — _parser.py:118 choices ollama/vllm/tgi/hf-endpoints hold. The tgi row (tgi-launcher.sh + Dockerfile) and lines 88-106 are wrong: deplo…
severity Medium · already tracked: KNOWN-OPEN CLI-10/CLI-14/CLI-15/CLI-16 (S11) — docs/roadmap/phase-16-trust-surface-hardening.md:616-618,624-625
Where. docs/usermanuals/tr/deployment/deploy-targets.md:28 · type: wrong detail
The document says. TGI hedefi tgi-launcher.sh ve bir Dockerfile üretir (ayrıca satır 88-106)
What the code does. _parser.py:118 choices ollama/vllm/tgi/hf-endpoints hold. The tgi row (tgi-launcher.sh + Dockerfile) and lines 88-106 are wrong: deploy.py:153-180 emits one docker-compose YAML.

Done when

Every finding above is fixed or closed with a reason (tick it here).
Code fixes carry a test; doc fixes update the Turkish mirror in the same PR.

_{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.}

Where to start

Thanks for taking a look. Please confirm the issue is unassigned and comment before starting so work does not overlap.

Start with these files on development:

Replace the TGI launcher/Dockerfile claims with the emitted docker-compose.yaml and the real launch command. Correct both the comparison table and detailed example in EN/TR; do not add a new emitter.

Run the focused tests:

pytest tests/test_deploy.py --no-cov

Run these guards/checks as applicable to the changed files:

ruff format --check forgelm/deploy.py tests/test_deploy.py
ruff check forgelm/deploy.py tests/test_deploy.py
python3 tools/check_bilingual_parity.py --strict
python3 tools/check_bilingual_code_blocks.py --strict
python3 tools/check_anchor_resolution.py --strict
python3 tools/check_tr_links_prefer_mirror.py --strict
python3 tools/check_usermanual_self_contained.py --strict
python3 tools/check_usermanual_schema_drift.py --strict

If user-facing documentation changes, update the existing Turkish mirror in the same PR; keep commands, code and terminal output in English and structurally aligned. English-only contributor standards need no new mirror.

Open the PR against development with Fixes #618 once every finding is resolved or explicitly closed with a reason; use Refs #618 for partial work and list the resolved finding IDs.

I'm removing good first issue here and marking this help wanted, for two reasons. First, it needs natural Turkish written or reviewed by a native or near-native speaker: docs/standards/localization.md does not accept unreviewed machine translation (see its "No machine-translation output" rule). Second, this finding is tracked by Phase 16 step S11 (#897), which lands as one root-cause family with its own review rounds (see "Roadmap steps" in CONTRIBUTING.md). Please don't start on it without coordinating on #897 first.

Removing help wanted again: DOC-BNEG-008 is a unit of Phase 16 S11 (#897), whose pull request is expected to fix it, so this issue is blocked by #897 until S11 lands (see Dependencies between issues). The Turkish-text requirement from the earlier comment still applies to whoever fixes it; i18n stays.

Navigation Menu

Repository navigation

[Wave 3] Medium — Docs: docs/usermanuals/tr/deployment/ #618

Findings

Done when

Where to start

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[Wave 3] Medium — Docs: docs/usermanuals/tr/deployment/ #618

Description

Findings

Done when

Activity

cemililik commented on Oct 11, 2026

Where to start

cemililik commented on Oct 15, 2026

cemililik commented on Oct 20, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions