Correct three fabricated mechanisms in sweep-authored docs

[nahumtimerman]

Follow-up audit after the QS_ prefix error found in #29. All three of these were written during the PR #17 catch-up, by taking a changeset comment and guessing a plausible mechanism instead of reading the implementation. Each silently does nothing when a reader follows it.

1. AI Assistant placeholders

	Documented	Actual
Key	AIChatURL	AiChatUrl (product, Web.config, sample customer.config)
Missing	—	{context}, {pageContent}

{context} is the JSON bundle of every other value — and the placeholder used by the example Quali itself ships in customer.config (perplexity.ai/search?q={context}). {pageContent} is the visible page text, whitespace-collapsed and truncated to 2000 characters.

Added both, plus:

• a warning that either placeholder sends on-screen Portal content (resource names, addresses, attribute values) to the external chat service, where it may be logged;
• values are URL-encoded automatically, so don't pre-encode;
• an unknown or misspelled placeholder resolves to empty rather than erroring.

Verified against qdPortalHeader.ts and replaceNamedTokens in utilities.js — deliberately not against the AppSetting description string, which is itself stale (it omits pageContent, resourceList, resourceCount and is the kind of secondhand source that caused these bugs).

The key-name error was cosmetic rather than breaking: NameValueCollection lookup is case-insensitive, so AIChatURL did resolve. Fixed for consistency with the product.

2. AllowUnicodeForCommandContext pointed at the wrong machine

Documented as a CloudShell Server key. It's read by ScriptCommandExecutionOperation in TestShell/Runtime/Service — the Execution Server project, which owns QsExecutionServer.exe.config whose appSettings has file="customer.config". Setting it on the Quali Server has no effect. Corrected component and location; pinned the version to 2024.1.0.2669 to match What's New.

3. Docker ES attributes

Documented as one -e ATTRIBUTE_<Name>=<Value> flag per attribute. No such prefix is handled anywhere in the product. es_start.sh reads a single ES_ATTRIBUTES variable containing a JSON object and forwards it as /a: to QsExecutionServerConsoleConfig. Rewrote against the entrypoint and Program.cs, and documented that names may contain spaces, the variable is optional, and attributes apply at first registration.

Audit scope

Extracted every <add key="..."> in the configuration-options tree — 186 keys — and checked each against the product source. All 186 exist; there are no further invented key names. The 2026.1 / 2024.1 version claims on all three items above were verified against the release branches and are correct.

I also corrected a memory note of my own that turned out to be an unverified inference: I had been treating AppSettingVisibility.Support as a gate on customer documentation. The enum is declared // used by QsBuild in Reflection, has no consumer in the workspace, and correlates poorly with reality — AiChatUrl is Support yet ships with a sample value in customer.config, while MoreShellsUrl (a community link) is Customer. Nothing was removed from the docs on the strength of it.

Verification

npx docusaurus build passes; the 3 broken links reported are pre-existing (intro/features/abstract-resources). Diff is pure LF.

🤖 Generated with Claude Code