docs(portal): clarify prompt features are analysis-only metadata (#1276)

[Derrick Richard (DerrickUnleashed)]

Summary

Closes #1276.

Users confused prompt features with something that affects run behavior. The Portal copy implied features describe "capabilities the agent's prompt or output uses", which reads like a runtime toggle. Prompt features are detection rules over a task prompt, and they are analysis metadata only: they categorize prompts so you can slice and filter runs.

Verified in source: taskPrompt.features is only read by report-template trigger evaluation (packages/shared/src/report-templates/trigger-evaluator.ts) and run filtering (apps/api/src/routes/requests/index.ts). It is never injected into an agent prompt, and never influences orchestration or judging.

• apps/portal/src/pages/PromptFeatureList.tsx — correct the header tooltip (it described agent capabilities) and the page description.
• apps/portal/src/pages/PromptFeatureDetail.tsx — add a "Metadata only" note above the detection-prompt editor.
• apps/portal/src/components/PromptFeatureWizard.tsx — step 1 states that features only categorize prompts for analysis.
• website/src/content/docs/guides/prompt-features.mdx — new note: features are never sent to the agent and never change the prompt, run execution, or scoring; edit the task prompt, not its features.
• AGENTS.md — replace "Feature flags tracking what capabilities agents request" (implied runtime behavior) with the prompt-categorization description.

Demos

N/A — copy-only changes to existing Portal pages and docs; no behavior or UI layout changes.

Before

N/A

After

N/A

Testing

• pnpm --filter portal lint (tsc --noEmit) — clean
• pnpm vitest run apps/portal — 68 files / 467 tests pass
• pnpm --dir website test — pass
• SITE=https://microsoft.github.io BASE_PATH=/scope pnpm --dir website build — 214 pages built

Documentation and compatibility

• website/src/content/docs/guides/prompt-features.mdx — added an explicit "features are analysis-only" note.
• AGENTS.md — corrected the prompt-features description.
• No API, CLI, or schema changes. No breaking changes and no upgrade steps.

Checklist

• If Portal features changed, keep CLI capabilities in sync. — N/A (copy clarification only, no capability change)
• If Portal components changed, update their Storybook stories. — N/A (text-only copy changes, no component structure/states added)
• If database changes require a migration, include up() / down() and keep it CosmosDB-compatible. — N/A (no database changes)
• If dependencies changed, update the lockfile and regenerate NOTICE / NOTICE-REVIEW.txt with pnpm notice as needed. — N/A (no dependency changes)
• Video showing the behavior before the suggested change — N/A (see Demos)
• Video showing the behavior after the suggested change — N/A (see Demos)

[Derrick Richard (DerrickUnleashed)]

@microsoft-github-policy-service agree