Adds a skill for taking a Windows desktop app through its first Microsoft
Store submission: product identity, an unsigned Store MSIX, package
inspection, WACK with report verification, every Partner Center section,
and certification monitoring. It includes PowerShell scripts for MSIX
inspection and WACK, a guarded Playwright controller for Partner Center,
references, and templates.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 33e33f93-bd16-4262-8026-fc42063cef78
The README build fetched the live GitHub MCP registry to decide whether to
link server names, which made output nondeterministic (e.g. Apify) and
caused the validate-readme check to fail intermittently.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
* Add v-development skill
Teach Copilot V language development: toolchain, v.mod layout, build/test/fmt, and Option/Result error handling.
* Fix v-development skill accuracy
Correct v.mod schema (dependencies), manifest optionality, entry-point guidance, VPM registry URL, and globals rule per official V docs.
* Correct mutability and Option/Result propagation guidance
Variables use mut, only struct sections use mut:; postfix ? propagates Options, ! propagates errors; no forced unwrap.
* Scope compilation, nil, and mutability guidance to verified behavior
v run excludes test files; nil only in unsafe/C interop; mutable parameters documented.
* Keep example Config fields immutable
The port field was never mutated; placing it under mut: contradicted the immutable-by-default guidance.
* Recommend json2 over superseded json module
Official V docs teach json2 for encoding/decoding.
* Refactor Learning Hub content to reduce changelog-audit-trail noise
Follows up on the Learning Hub content audit report: automated
changelog-driven PRs had turned several evergreen guide pages into a
version-history audit trail rather than current-state documentation
(e.g. copilot-configuration-basics.md had 86 inline vX.Y.Z+ tags).
Content changes:
- copilot-configuration-basics.md, installing-and-using-plugins.md,
building-custom-agents.md, automating-with-hooks.md, and
understanding-mcp-servers.md: removed decorative inline version
tags from the main teaching flow so pages read as 'how to use this
today' rather than 'when this changed'. Genuinely actionable
history (renames, removed flags/settings, breaking defaults) is
consolidated into a new Compatibility and Migration Notes section
per page instead of being scattered inline.
Automation change:
- .github/workflows/learning-hub-updater.md (+ recompiled .lock.yml):
added a 'stale version notes' detection step, a content model that
distinguishes evergreen guides from Compatibility and Migration
Notes sections, consolidation rules, and a required content-cleanup
checklist item in the PR body, so future automated updates keep
this pattern instead of re-accumulating inline version chronology.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
* Address Learning Hub review feedback
Clarify the evergreen and compatibility section model and restore version thresholds needed for troubleshooting older CLI installations.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
* Update .NET Copilot SDK cookbook: fix On<T> breaking change, add in-process runtime, tool search, and message provenance recipes
- Fix breaking change: Session.On is now generic (On<T> where T : SessionEvent).
Updated all recipes that used the old non-generic session.On(evt => ...) pattern:
error-handling, pr-visualization, managing-local-files, accessibility-report,
ralph-loop (both .md and .cs where applicable).
- Add new 'In-Process Runtime' recipe (in-process-runtime.md + recipe/in-process-runtime.cs)
demonstrating RuntimeConnection.ForInProcess(), live-tested.
- Document tool search / deferred loading (SessionConfig.ToolSearch / ToolSearchConfig)
in pr-visualization.md, live-tested.
- Document typed message provenance (MessageOptions.Source / MessageSource) in
error-handling.md, live-tested.
- Fix dotnet/README.md recipe index: it was missing Ralph Loop and Accessibility
Report entries; also added the new In-Process Runtime entry.
- Add In-Process Runtime entry to the top-level cookbook/copilot-sdk/README.md
.NET section.
- Update dotnet/recipe/README.md runnable-examples table with the new recipe.
All existing .NET cookbook recipes were rebuilt and rechecked against the current
GitHub Copilot SDK (Copilot CLI 1.0.85); no other breaking changes were found.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Update cookbook model names to current supported models
- Replace stale/nonexistent model IDs (gpt-5, claude-sonnet-4.5,
claude-opus-4.6, gpt-5.1-codex-mini) with current values from the
supported AI models list
- Prefer Model = "auto" wherever a specific model isn't load-bearing
to the recipe's teaching point
- ralph-loop: pin gpt-5.3-codex (current codex-family GA model), since
a dedicated coding model is a deliberate, documented choice for the
autonomous loop
- multiple-sessions: reshape the model narrative so it demonstrates a
real explicit-override use case (A/B testing via claude-sonnet-5)
instead of two sessions sharing the same hardcoded model
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Use SendAndWaitAsync in in-process runtime recipe
Replace the event-based TaskCompletionSource pattern with SendAndWaitAsync so the example waits for the final assistant response, propagates session errors, and uses the SDK timeout behavior.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Update the external plugin version and tag, pin the merged upstream release commit, and regenerate the marketplace.
Co-authored-by: haozhang <haozhan@microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 4a60a8cc-9b50-40c7-b29a-bdbf60144f6f
* Update Anarlog to local-first version 1.3.0
Pin the existing listing to the tested source revision and regenerate its marketplace entry.
* Pin the final reviewed Anarlog package
Include corrected Flatpak setup and paid-Team eligibility in the 1.3.0 source.
* keep-the-why: bump to 0.16.0
* keep-the-why: bump to 0.16.1
* keep-the-why: bump to 0.16.2
* keep-the-why: bump to 0.16.3
* keep-the-why: bump to 0.17.0 (version and source.ref)
* Simplify agent definitions and bump plugin version to 1.129.0
* Fix spelling of reusable in gem-planner agent
* Simplify agent definitions and bump gem-team to 1.130.0
* Simplify agent definitions and bump gem-team to 1.131.0
* fix: revise proof rule to aovid redundant echoing
* fix: Simplify orchstrator rules
All three links in this section are stale. One is a hard 404, the other two
point at VS Code documentation paths that have since been restructured.
- The "Awesome Copilot Prompt Files" link pointed at
github.com/github/awesome-copilot/tree/main/prompts, which returns 404.
There is no prompts/ directory in this repository, no *.prompt.md file
anywhere in it, and no prompts page on the site — awesome-copilot.github.com
serves agents, instructions, skills, plugins and extensions only, and
/prompts/ is a 404 there too. Since the collection no longer exists, the
bullet is removed rather than repointed.
- "Prompt Files Documentation" moved from /docs/copilot/customization/
prompt-files to /docs/agent-customization/prompt-files. The old path still
redirects, but the destination is now explicit. The #_prompt-file-format
anchor still exists on the new page, so the deep link is preserved.
- "Tool Configuration" pointed at /docs/copilot/chat/chat-agent-mode
#_agent-mode-tools. That path now redirects to the generic chat overview,
where the #_agent-mode-tools anchor no longer exists, so the link landed
readers on a page with no tool configuration content. Updated to
/docs/agents/run/tools, the current page for selecting and managing tools.
Every URL was requested directly and the resulting status and final URL
recorded. Both replacements return 200, and the surviving anchor was
confirmed present in the new page's markup.
Co-authored-by: SurefireStudios <heresamemo@gmail.com>