kb-field-reportlisted

Use the Field Report CLI as a progressive-disclosure interview. 1. Start with `node .knowledge/tools/field-report.js start --new --json`, or resume with `questions --json`. Public output is fixed to English. The source language defaults to `auto`; complete English prose resolves automatically, while other or ambiguous prose requires `translation-export --language=<source-bcp47>`. 2. Ask only the returned questions, including the report relationship (independent user, first-party maintainer dogfooding, internal QA, or controlled comparison). Preserve negative and uncertain answers; ask at most one concrete follow-up when evidence is vague. Use generalized descriptions instead of internal workspace, department, client, or team names. 3. Save answers as JSON and run `ingest --report-id=<id> --answers=<path>`. For a non-English source, use `translation-export`. Translate only the privacy-stable exported answers, preserve both `original_hash` and `exported_answers_hash`, require complete translator identity (`provider`, `model`, `actor`) and all safety attestations, then use `translation-ingest`. 4. Run `translation-approve --yes --tester-actor=<independent-reviewer>` only after that tester reviews the English translation. The reviewer must not be the translator. 5. Use the generated `task-results.template.json` to prepare a separate `knowledge-field-report-task-results.v1` file. Bind every public pass/warning/fail row to repository- or stat