Skip to content

Fix AS-20 selection handback wording #28

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
briancl2 merged 1 commit into from
Jun 9, 2026
Merged

Fix AS-20 selection handback wording #28

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion ...verhaul/.github/prompts/agentic_newsletter_phase_1a_updates_discovery.prompt.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,9 @@ Additional processing rules:
5. Consolidate model rollout changes (multiple models GA/PREVIEW) into a single "Model availability updates" entry (GA first, then PREVIEW) instead of separate scattered bullets.
6. Governance / legal / indemnity changes appear under Enterprise.
7. Record (internally) when an update is VS Code–centric for downstream implicit Copilot mapping in events.
8. Preserve original raw tags in an internal note field if captured, but FINAL displayed category must be one canonical category only.
8. Preserve original raw tags only in an internal note field if captured:
- For output, write exactly one `Category` value from the canonical taxonomy above.
- For ambiguous or unmapped items, choose the closest canonical category and add internal note metadata `Reviewer Action`: `review_category_mapping` with a brief mapping note. This metadata is not rendered in the final markdown.

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 9, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Persist category review metadata

For ambiguous or unmapped items, this asks the agent to add Reviewer Action metadata but also says it is not rendered in the final markdown. This legacy Phase 1A prompt only writes the discoveries markdown file, and repo-wide search found no consumer or sidecar artifact for Reviewer Action/review_category_mapping, so the mapping note is lost exactly when a reviewer would need it to audit the forced category choice. Persist it somewhere durable, such as a non-customer-facing notes section or sidecar file, instead of keeping it purely internal.

Useful? React with 👍 / 👎.

</decision>
</phase>

Expand Down
Loading