docs: report a bug or request a feature from the conversation

[mrgoonie]

Do not merge before digitopvn/clarkcant#530 merges.

Official docs (EN + VI) for reporting a bug or requesting a feature from the conversation.

Changes

• docs/index.html, vi/docs/index.html: /report in the slash command list, and a new section Report a bug or request a feature (#report). It covers the Feedback Composer, that only the person's own Create issue press files a report, the policy on that press, duplicate search, the result states, Check again, Send again and Send anyway, recheck after a restart, github_token and the manual link, what is and is never shared, and that handing a filed issue to Clark is not available yet.
• docs/api.html, vi/docs/api.html: new section Report a bug or request a feature (#product-reports) with the three /feedback/reports routes, the request shape, the publish intents, the statuses, 409 NOTHING_SENT, 409 NOT_INCONCLUSIVE, eligibility, and 403 PERSON_ONLY.
• docs/mcp.html, vi/docs/mcp.html: the person-only note now says that filing a product report is refused on machine surfaces.

Source of truth

Every claim was checked against docs/open-interfaces(.vi).md "Product reports", packages/contracts/src/feedback.ts, apps/runtime/src/application/{slash-commands,product-feedback,feedback-github}.ts, packages/contracts/src/machine-surfaces.ts and the card strings in messages-shell.ts at the head of digitopvn/clarkcant#530.

Notes

• The issue lists "Send again". The PR also ships intent: "send-anyway" (Send anyway) for a report whose outcome checking cannot settle. That is documented too.
• The issue templates are mentioned in one sentence (Bug report, Feature request); they live in the product repository, not here.

Verification

• Static checks over all 10 docs pages (EN + VI): tags balanced, no duplicate ids, every internal link and anchor resolves, EN and VI pages carry the same ids.
• node scripts/prepare-site.mjs (build:static) copies the pages and writes the sitemap.
• All five docs branches for docs: report a bug or request a feature from the conversation (/report) #118–docs: long conversations — timeline paging API and history loading (clarkcant#497) #122 were test-merged together without conflicts, and the combined pages pass the same checks.
• The full pnpm verify and browser suite run in the Blog checks workflow on this PR; these pages are static HTML that the typecheck and tests do not read.

Refs #118
Refs digitopvn/clarkcant#510
Refs digitopvn/clarkcant#530