Adds Security Champion chat / agent mode to provide comprehensive security guidance by integrating Microsoft's Security Development Lifecycle (SDL) practices alongside existing OWASP frameworks. #408

obrocki · 2026-02-04T10:06:10Z

Incorporates all 10 Microsoft SDL practices for secure software development
Organizes security inspection areas by development lifecycle stage (Design, Code, Build/Deploy, Runtime)
Adds guidance for threat modeling, Zero Trust principles, and supply chain security
Expands responsibilities to include security design reviews and Secure by Design promotion
Maintains existing OWASP Top 10 and OWASP Top 10 for LLM Applications (2025) references

🔒 - Generated by Copilot

Pull Request

Description

Related Issue(s)

#416

Type of Change

Select all that apply:

Code & Documentation:

Bug fix (non-breaking change fixing an issue)
New feature (non-breaking change adding functionality)
Breaking change (fix or feature causing existing functionality to change)
Documentation update

Infrastructure & Configuration:

AI Artifacts:

Reviewed contribution with prompt-builder agent and addressed all feedback
Copilot instructions (.github/instructions/*.instructions.md)
Copilot prompt (.github/prompts/*.prompt.md)
Copilot agent (.github/agents/*.agent.md)

Sample Prompts and Usage

Checklist

Required Checks

Documentation is updated (if applicable)
Files follow existing naming conventions
Changes are backwards compatible (if applicable)
Tests added for new functionality (if applicable)

AI Artifact Contributions

Used /prompt-analyze to review contribution
Addressed all feedback from prompt-builder review
Verified contribution follows common standards and type-specific requirements

Required Automated Checks

The following validation commands must pass before merging:

Markdown linting: npm run lint:md
Spell checking: npm run spell-check
Frontmatter validation: npm run lint:frontmatter
Link validation: npm run lint:md-links
PowerShell analysis: npm run lint:ps

Security Considerations

This PR does not contain any sensitive or NDA information
Any new dependencies have been reviewed for security issues
Security-related scripts follow the principle of least privilege

Additional Notes

…M applications - include OWASP Top 10 for LLM Applications (2025) security practices - outline responsibilities and areas to inspect during development stages - emphasize security champion mindset and ongoing threat awareness 🔒 - Generated by Copilot

codecov-commenter · 2026-02-04T10:08:21Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.19%. Comparing base (2b4d123) to head (c0d6bde).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #408      +/-   ##
==========================================
- Coverage   76.22%   76.19%   -0.03%     
==========================================
  Files          20       20              
  Lines        3503     3503              
==========================================
- Hits         2670     2669       -1     
- Misses        833      834       +1

Flag	Coverage Δ
pester	`76.19% <ø> (-0.03%)`	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

…nd tools list 🔒 - Generated by Copilot

Copilot

Pull request overview

This PR adds a Security Champion agent and comprehensive OWASP security instruction files to integrate Microsoft's Security Development Lifecycle (SDL) practices alongside existing OWASP frameworks. The PR introduces security guidance across the development lifecycle, from design through runtime, with detailed coding standards for both traditional web applications and LLM-specific security concerns.

Changes:

Adds Security Champion conversational agent for security-focused code review and advisory
Introduces comprehensive OWASP Top 10 secure coding instructions for web applications
Adds OWASP Top 10 for LLM Applications (2025) secure coding instructions for AI/ML security

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 14 comments.

File	Description
`.github/agents/security-champion.agent.md`	New conversational agent that serves as a security advisor, integrating Microsoft SDL practices with OWASP frameworks to guide security reviews across all development stages
`.github/instructions/owasp-for-web-applications.instructions.md`	New instruction file providing comprehensive secure coding guidelines based on OWASP Top 10, covering vulnerabilities from access control to SSRF
`.github/instructions/owasp-for-llms.instructions.md`	New instruction file providing LLM-specific security guidelines based on OWASP Top 10 for LLM Applications (2025), covering prompt injection, data leakage, and other AI-specific risks

.github/instructions/owasp-for-web-applications.instructions.md

.github/agents/security-champion.agent.md

.github/instructions/owasp-for-web-applications.instructions.md

.github/instructions/owasp-for-llms.instructions.md

.github/instructions/owasp-for-web-applications.instructions.md

.github/instructions/owasp-for-llms.instructions.md

.github/instructions/security/owasp-for-web-applications.instructions.md

.github/instructions/owasp-for-web-applications.instructions.md

- clarify the directive for secure coding practices - emphasize the importance of a security-first mindset - enhance instructions for code reviews and security education 🔒 - Generated by Copilot

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Copilot

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 5 comments.

.github/instructions/owasp-for-web-applications.instructions.md

.github/instructions/owasp-for-llms.instructions.md

.github/instructions/owasp-for-web-applications.instructions.md

…curity champion agent documentation 🔒 - Generated by Copilot

Copilot

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

.github/instructions/owasp-for-llms.instructions.md

.github/agents/security-champion.agent.md

…hampion agent documentation 🔒 - Generated by Copilot

- enhance clarity and structure of security instructions - add maturity status to both documents - improve emphasis on security principles and practices - refine sections for better readability and understanding 🔒 - Generated by Copilot

Copilot

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.

.github/agents/security-champion.agent.md

.github/instructions/owasp-for-web-applications.instructions.md

.github/agents/security-champion.agent.md

WilliamBerryiii · 2026-02-04T17:54:58Z

.github/agents/security-champion.agent.md

+description: "🔐 Security Champion"
+tools: ['execute/getTerminalOutput', 'read', 'agent', 'todo']
+argument-hint: "Assist development teams in integrating security best practices throughout the software development lifecycle by acting as a Security Champion."
+maturity: preview


might want to make this as experimental for now.

Fair. Been using it out in the wild so it has a bit of mileage already.

WilliamBerryiii · 2026-02-04T17:56:57Z

.github/agents/security-champion.agent.md

+
+These frameworks apply throughout the development lifecycle:
+
+* [OWASP Top 10](../instructions/owasp-for-web-applications.instructions.md) for web application security


@katriendg & @agreaves-ms - I'm of the option that in order to get comprehensive review across all these areas, we need to use the same pattern as task researcher where we have a orchestration agent and then sub-agents for each of the areas of focus ... adding in mitre, soc, etc. as dedicated subagents that deeply understand the domain of each standard/practice. thoughts?

Fully agreed, now with the latest release running parallel subagents is supported: https://code.visualstudio.com/updates/v1_109#_agent-orchestration

I wonder if some of the current instructions files referenced by the agent can be transformed by integrating into a more planned approach of going through stages or phases as subagents that are called within the main orchestrator (this security champion agent).

Do we want to start with an MVP version of the discussed capability and add an Issue that captures evolution of this?

That's a good idea, though there are some quick wins you may be able to get for this initial MVP. I'll be adding a few PR comments around these. Thanks.

WilliamBerryiii · 2026-02-04T22:00:59Z

Hi! A small request: could you update the PR title to include the conventional commit format with scope? This ensures release-please picks it up correctly for the changelog.

Suggested: `feat(agents): add security champion agent with Microsoft SDL practices

Thanks!

… guidelines 🔒 - Generated by Copilot

katriendg

Thanks for your contribution. This is valuable, there are a few optimizations I feel are relevant before we merge.

Please re-run the /prompt-analyse or prompt-builder agent again and ensure you add your new files to the context, and ask it to review your three files for recommendations. There are several open recommendations you can still apply before we merge.
Evaluate the usage of the .instructions.md files and applyTo. Is it possible to merge into the custom agent instead? Especially for the LLM application instructions we do not want to enforce this upon every single edit of applicable files. Again here the Task-Researcher and/or Prompt Builder agents may help you refactor some of this in an efficient way.
## Required Phases given this agent has specific phases (in your case Stages), you should be able to easily reformat the agent to follow the phases approach. Also prompt-builder may do this for you.

Hope these make sense!

katriendg · 2026-02-05T09:35:39Z

.github/agents/security-champion.agent.md

@@ -0,0 +1,83 @@
+---
+description: "🔐 Security Champion"
+tools: ['execute/getTerminalOutput', 'read', 'agent', 'todo']


Please add fetch_webpage or remove the tools entirely as your agent has external references it won't be able to fetch. I lately see more value in removing the tools entirely so that users can choose which tools they want to allow.

I see the point of leaving tools blank, would that be the best out-of-the-box, ready-to-go experience?

katriendg · 2026-02-05T09:36:27Z

.github/agents/security-champion.agent.md

+
+These frameworks apply throughout the development lifecycle:
+
+* [OWASP Top 10](../instructions/owasp-for-web-applications.instructions.md) for web application security


That's a good idea, though there are some quick wins you may be able to get for this initial MVP. I'll be adding a few PR comments around these. Thanks.

katriendg · 2026-02-05T09:39:11Z

.github/agents/security-champion.agent.md

+
+## Security Champion Mindset
+
+Security is an ongoing effort where threats, technology, and business assets constantly evolve. Help teams understand the attacker's perspective and goals. Focus on practical, real-world security wins rather than theoretical overkill. Treat threat modeling as a fundamental engineering skill that all developers should possess.


Please add the footer as documented in docs/contributing/custom-agents.md

I missed that one, thank you for pointing it out!

katriendg · 2026-02-05T09:42:33Z

.github/agents/security-champion.agent.md

@@ -0,0 +1,83 @@
+---
+description: "🔐 Security Champion"


The description needs to be more elaborated, when we include this in the Extension packaging it will pick up that description automatically and show it in some of the UI.

katriendg · 2026-02-05T09:44:46Z

.github/agents/security-champion.agent.md

+description: "🔐 Security Champion"
+tools: ['execute/getTerminalOutput', 'read', 'agent', 'todo']
+argument-hint: "Assist development teams in integrating security best practices throughout the software development lifecycle by acting as a Security Champion."
+maturity: experimental


Have you evaluated how this agent can handoff to security-plan-creator?

Not yet, keeping it focused and small for now, good suggestion tho!

katriendg · 2026-02-05T09:46:47Z

.github/agents/security-champion.agent.md

+
+These frameworks apply throughout the development lifecycle:
+
+* [OWASP Top 10](../instructions/owasp-for-web-applications.instructions.md) for web application security


nit: consider adding #file: so copilot can follow the path, same for the next line

katriendg · 2026-02-05T09:49:05Z

.github/instructions/owasp-for-llms.instructions.md

@@ -0,0 +1,573 @@
+---
+description: "Comprehensive secure coding instructions for LLM applications based on OWASP Top 10 for LLM Applications (2025). Ensures AI-powered systems are secure by default, protecting against prompt injection, data leakage, and LLM-specific vulnerabilities. Give clear and concise feedback and points of improvement."
+applyTo: '**/*.py, **/*.tsx, **/*.ts, **/*.jsx, **/*.js, **/*.cs, **/*.java'


Highly recommend rethinking the applyTo which will be added to the context on every single context when files with these extensions are active. This seems inefficient since a lot of work users will do are not relevant to LLM applications guidance. I recommend removing the applyTo entirely, and leaving to being called by the agent instead.

katriendg · 2026-02-05T09:49:47Z

.github/instructions/owasp-for-web-applications.instructions.md

@@ -0,0 +1,226 @@
+---
+description: "Comprehensive secure coding instructions for all languages and frameworks, based on OWASP Top 10 and industry best practices. Give clear and concise feedback and points of improvement."
+applyTo: '**/*.py, **/*.tsx, **/*.ts, **/*.jsx, **/*.js'


Same here, are we sure we want to push this instruction to every edit of a file with these extensions?

katriendg · 2026-02-05T10:03:49Z

.github/instructions/security/owasp-for-llms.instructions.md

+
+Separate system instructions from user content using clear delimiters. Do not concatenate user input directly into prompts without sanitization.
+
+```python


Get prompt builder to help you reformat all examples such as these with XML blocks as per convention. Something like the following, emoji up to you to decide.

 ```python # ✅ GOOD: Structured prompt with clear boundaries system_prompt = "You are a customer service assistant. Only answer questions about product features." user_input = sanitize_input(request.user_message) # Remove injection attempts response = llm.generate(system=system_prompt, user=user_input) validated_response = validate_output_schema(response) # Ensure format compliance

# ❌ BAD: Direct concatenation with no validation prompt = f"Answer this: {request.user_message}" # Vulnerable to injection response = llm.generate(prompt) # No output validation

Copilot

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

.github/instructions/owasp-for-llms.instructions.md

.github/agents/security-champion.agent.md

.github/instructions/owasp-for-llms.instructions.md

…arity and structure - redefine inspection areas as required phases - clarify flow through development lifecycle phases - enhance guidance for security reviews and reporting 🔒 - Generated by Copilot

Copilot

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

katriendg · 2026-02-06T08:51:37Z

Thanks for your changes, I think this is looking good for an initial inclusion into experimental pre-release so we can have some active testing, see how it behaves when used together with some of the other instructions and agents.
Please review any open comments and close them, either adopt the recommendation or leave a note and close the comment. Some of the Copilot comments are valid, some you may just want to discard, or simply outdated.
Once all comments are closed I will do a final review and expect Approval soon from my side.

- Remove tools frontmatter to let users choose available tools - Elaborate agent description for Extension UI visibility - Add #file: references for OWASP instructions so Copilot follows paths - Add maturity: experimental to both OWASP instruction files - Convert bolded-prefix list items to plain text in LLM instructions - Convert embedding inversion defense list to prose

Copilot

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

.github/instructions/security/owasp-for-web-applications.instructions.md

obrocki · 2026-02-06T13:35:18Z

Thanks for your changes, I think this is looking good for an initial inclusion into experimental pre-release so we can have some active testing, see how it behaves when used together with some of the other instructions and agents.
Please review any open comments and close them, either adopt the recommendation or leave a note and close the comment. Some of the Copilot comments are valid, some you may just want to discard, or simply outdated.
Once all comments are closed I will do a final review and expect Approval soon from my side.

Thank you for your feedback and help!

agreaves-ms · 2026-02-06T18:36:23Z

.github/instructions/owasp-for-llms.instructions.md

@@ -0,0 +1,568 @@
+---
+description: "Comprehensive secure coding instructions for LLM applications based on OWASP Top 10 for LLM Applications (2025). Ensures AI-powered systems are secure by default, protecting against prompt injection, data leakage, and LLM-specific vulnerabilities. Give clear and concise feedback and points of improvement."


The description for instructions.md files are added to the system message for the conversation context. I recommend treating all descriptions as additional instructions, so changing this description to inform the model of when to read and use these instructions files.

agreaves-ms · 2026-02-06T18:46:06Z

.github/instructions/security/owasp-for-llms.instructions.md

+maturity: experimental
+---
+
+# OWASP Top 10 for LLM Applications - Secure Coding Guidelines


This looks like it's meant to be used for developing an agentic platform that orchestrates LLMs together for different business use-cases.

I recommend moving both of these instructions into a subfolder, such as llm-platform or whatever a better name might be.

How about security? One of them has nothing to do with LLMs...

agreaves-ms · 2026-02-06T18:50:22Z

.github/instructions/security/owasp-for-llms.instructions.md

+
+#### Red Team Testing
+
+Before deploying any third-party model, conduct rigorous adversarial testing including prompt injection attempts, jailbreaking tests, and bias evaluation.


I recommend reviewing all of the lines in this instructions file and consider what would make sense as an actual instruction to Claude or GPT. As an example, this instruction is not clear with what the model should do. Should it tell the user this information? If so, how would it present this information to the user?

agreaves-ms · 2026-02-06T19:07:41Z

.github/instructions/security/owasp-for-web-applications.instructions.md

+
+## Instructions
+
+Ensure all code generated, reviewed, or refactored is secure by default. Operate with a security-first mindset. When in doubt, choose the more secure option and explain the reasoning.


Same thing here, I would recommend moving this into a different folder, owasp maybe

Both instructions are based on owasp security recommedataions 👇
#408 (comment)

agreaves-ms · 2026-02-06T19:11:38Z

.github/instructions/security/owasp-for-web-applications.instructions.md

+
+#### Principle of Least Privilege
+
+Default to the most restrictive permissions. Explicitly verify the caller's rights for each protected resource or action.


Same for this instructions file, I would recommend reviewing each individual line and make sure it makes sense as an instruction for the model to follow. As an example, the model may not know what the most restrictive permissions are and can result in unintended outputs, same thing for explicitly verifying the caller's rights and what would be considered a protected resource or action.

Since the agent and instructions are in preveiw / experimantal state I'd like to gather more field feedback before revisiting the prompts.

…tore web applications guidelines - introduce OWASP Top 10 for LLM Applications with detailed security measures - restore comprehensive secure coding instructions for web applications - ensure clear communication of security practices and principles 🔒 - Generated by Copilot

Copilot

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

.github/instructions/security/owasp-for-web-applications.instructions.md

Copilot AI review requested due to automatic review settings February 4, 2026 10:06

Copilot started reviewing on behalf of obrocki February 4, 2026 10:06 View session

feat(security-identity): update Security Champion agent description a…

d046fce

…nd tools list 🔒 - Generated by Copilot

Copilot AI reviewed Feb 4, 2026

View reviewed changes

obrocki and others added 2 commits February 4, 2026 13:25

docs(instructions): refine secure coding guidelines for LLM applications

3503c41

- clarify the directive for secure coding practices - emphasize the importance of a security-first mindset - enhance instructions for code reviews and security education 🔒 - Generated by Copilot

Update .github/instructions/owasp-for-web-applications.instructions.md

d0146d2

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Copilot AI review requested due to automatic review settings February 4, 2026 14:03

Copilot started reviewing on behalf of obrocki February 4, 2026 14:04 View session

Copilot AI reviewed Feb 4, 2026

View reviewed changes

obrocki and others added 2 commits February 4, 2026 14:11

style(security-identity): fix link formatting for Microsoft SDL in se…

7855ee0

…curity champion agent documentation 🔒 - Generated by Copilot

Merge branch 'microsoft:main' into feat/security-champion-agent

6224976

Copilot AI review requested due to automatic review settings February 4, 2026 14:54

Copilot started reviewing on behalf of obrocki February 4, 2026 14:54 View session

Copilot AI reviewed Feb 4, 2026

View reviewed changes

.github/instructions/owasp-for-llms.instructions.md Outdated Show resolved Hide resolved

.github/agents/security-champion.agent.md Show resolved Hide resolved

obrocki marked this pull request as ready for review February 4, 2026 16:24

obrocki requested a review from a team as a code owner February 4, 2026 16:24

obrocki added 2 commits February 4, 2026 16:30

style(security-identity): refine language and structure in security c…

4bcfda1

…hampion agent documentation 🔒 - Generated by Copilot

Copilot AI review requested due to automatic review settings February 4, 2026 16:54

Copilot started reviewing on behalf of obrocki February 4, 2026 16:54 View session

Copilot AI reviewed Feb 4, 2026

View reviewed changes

obrocki mentioned this pull request Feb 4, 2026

feat(agents): Add Security Champion agent with SDL and OWASP guidance #416

Open

WilliamBerryiii reviewed Feb 4, 2026

View reviewed changes

WilliamBerryiii added this to the v2.2.0 milestone Feb 5, 2026

chore(instructions): update maturity status to experimental for OWASP…

64def7e

… guidelines 🔒 - Generated by Copilot

katriendg requested changes Feb 5, 2026

View reviewed changes

Copilot AI review requested due to automatic review settings February 5, 2026 14:52

Copilot started reviewing on behalf of obrocki February 5, 2026 14:52 View session

Copilot AI reviewed Feb 5, 2026

View reviewed changes

.github/instructions/owasp-for-llms.instructions.md Outdated Show resolved Hide resolved

.github/agents/security-champion.agent.md Show resolved Hide resolved

.github/instructions/owasp-for-llms.instructions.md Outdated Show resolved Hide resolved

obrocki and others added 2 commits February 5, 2026 19:33

Merge branch 'main' into feat/security-champion-agent

fab4d50

feat(security-identity): update security champion agent phases for cl…

69c28e8

…arity and structure - redefine inspection areas as required phases - clarify flow through development lifecycle phases - enhance guidance for security reviews and reporting 🔒 - Generated by Copilot

Copilot AI review requested due to automatic review settings February 5, 2026 19:48

Copilot started reviewing on behalf of obrocki February 5, 2026 19:49 View session

obrocki requested a review from katriendg February 5, 2026 19:49

Copilot AI reviewed Feb 5, 2026

View reviewed changes

Merge branch 'main' into feat/security-champion-agent

da03c90

Copilot AI review requested due to automatic review settings February 6, 2026 13:28

Copilot started reviewing on behalf of obrocki February 6, 2026 13:28 View session

Copilot AI reviewed Feb 6, 2026

View reviewed changes

.github/instructions/security/owasp-for-web-applications.instructions.md Show resolved Hide resolved

agreaves-ms reviewed Feb 6, 2026

View reviewed changes

WilliamBerryiii modified the milestones: v2.2.0, v2.3.0 Feb 6, 2026

WilliamBerryiii and others added 2 commits February 7, 2026 15:25

Merge branch 'main' into feat/security-champion-agent

d7fa041

Copilot AI review requested due to automatic review settings February 9, 2026 11:16

Copilot started reviewing on behalf of obrocki February 9, 2026 11:16 View session

Copilot AI reviewed Feb 9, 2026

View reviewed changes

.github/instructions/security/owasp-for-web-applications.instructions.md Show resolved Hide resolved

.github/instructions/security/owasp-for-web-applications.instructions.md Show resolved Hide resolved

auyidi1 approved these changes Feb 9, 2026

View reviewed changes

Merge branch 'main' into feat/security-champion-agent

c0d6bde


		These frameworks apply throughout the development lifecycle:

		* [OWASP Top 10](../instructions/owasp-for-web-applications.instructions.md) for web application security


		## Security Champion Mindset

		Security is an ongoing effort where threats, technology, and business assets constantly evolve. Help teams understand the attacker's perspective and goals. Focus on practical, real-world security wins rather than theoretical overkill. Treat threat modeling as a fundamental engineering skill that all developers should possess.


		Separate system instructions from user content using clear delimiters. Do not concatenate user input directly into prompts without sanitization.

		```python

		@@ -0,0 +1,568 @@
		---
		description: "Comprehensive secure coding instructions for LLM applications based on OWASP Top 10 for LLM Applications (2025). Ensures AI-powered systems are secure by default, protecting against prompt injection, data leakage, and LLM-specific vulnerabilities. Give clear and concise feedback and points of improvement."


		#### Red Team Testing

		Before deploying any third-party model, conduct rigorous adversarial testing including prompt injection attempts, jailbreaking tests, and bias evaluation.


		## Instructions

		Ensure all code generated, reviewed, or refactored is secure by default. Operate with a security-first mindset. When in doubt, choose the more secure option and explain the reasoning.


		#### Principle of Least Privilege

		Default to the most restrictive permissions. Explicitly verify the caller's rights for each protected resource or action.

Adds Security Champion chat / agent mode to provide comprehensive security guidance by integrating Microsoft's Security Development Lifecycle (SDL) practices alongside existing OWASP frameworks. #408

Are you sure you want to change the base?

Adds Security Champion chat / agent mode to provide comprehensive security guidance by integrating Microsoft's Security Development Lifecycle (SDL) practices alongside existing OWASP frameworks. #408

Conversation

obrocki commented Feb 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Pull Request

Description

Related Issue(s)

Type of Change

Sample Prompts and Usage

Checklist

Required Checks

AI Artifact Contributions

Required Automated Checks

Security Considerations

Additional Notes

Uh oh!

codecov-commenter commented Feb 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

WilliamBerryiii commented Feb 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

katriendg left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

obrocki commented Feb 4, 2026 •

edited

Loading

codecov-commenter commented Feb 4, 2026 •

edited

Loading

WilliamBerryiii commented Feb 4, 2026 •

edited

Loading