Fix UC3 instructions leading space + sync UC2 pre-created agent change to _labs#483
Merged
Merged
Conversation
The site renders from _labs/mcs-tools.md, but PR #481 only updated labs/mcs-tools/README.md, so the deployed lab still walked through creating the agent and connecting the flow. This applies the same UC2 change to _labs/mcs-tools.md so the published lab matches: the "Create a New Agent" and "Add the Agent Flow" sections are replaced with "Open the Pre-Created Agent", and the summary and objective are updated. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The agent name and instructions fences in the "Create the new-type Sales Account Assistant" section were indented 4 spaces under a "1." list item. Kramdown strips only 3 spaces (the "1. " marker width), so a leading space leaked into the rendered <code>, which the copy button captured and which broke the agent when pasted into Instructions. Reduce the fence indentation to 3 spaces so kramdown strips it cleanly. Applied to both rendered sources (_labs and labs/.../README.md). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two lab content fixes on this branch:
Orchestration lab — UC3 step 4 leading space (commit
37924cc)The agent-name and Instructions code fences in the "Create the new-type Sales Account Assistant" section were indented 4 spaces under a
1.list item. Kramdown strips only 3 spaces (the1.marker width), so a leading space leaked into the rendered<code>— captured by the copy button and pasted into Copilot Studio, which broke the agent when tested. Reduced the fence indentation to 3 spaces so kramdown strips it cleanly. Applied to both rendered sources (_labs/mcs-orchestration.mdandlabs/mcs-orchestration/README.md).mcs-tools lab — UC2 sync to
_labs(commit6803912)The site renders from
_labs/mcs-tools.md, but PR mcs-tools: UC2 reflect pre-created agent and connected flow #481 only updatedlabs/mcs-tools/README.md, so the deployed lab still walked through creating the agent and connecting the flow. Applies the same UC2 change to_labs/mcs-tools.md: the "Create a New Agent" and "Add the Agent Flow" sections are replaced with "Open the Pre-Created Agent", and the summary/objective are updated.Verification
Confirmed the leading-space cause against the live rendered HTML (
<code> You are...) and verified that an existing 3-space-indented fence in another lab renders with no leading space (<code>kind...).🤖 Generated with Claude Code