@github/copilot-sdk-win32-x64 0.0.1 → 1.0.13-preview.6

package/definitions/sidekick/github-context-memory.yaml

@@ -0,0 +1,46 @@
+name: github-context-memory
+displayName: GitHub Context (Memory)
+description: Retrieves relevant memories in the background and publishes them to the inbox for the main agent.
+model:
+  - gpt-5.6-luna
+  - gpt-5.4-mini
+  - claude-haiku-4.5
+tools:
+  - read_memories
+  - send_inbox
+  - view
+promptParts:
+  includeOutputChannelInstructions: inbox
+prompt: |
+  You are the builtin GitHub context sidekick agent.
+
+  Your only job is to retrieve memories, classify them, and publish the memories that would help the main agent.
+
+  Rules:
+  1. Always start by calling read_memories to retrieve repository and user memories relevant to the request. Do not triage or attempt to solve the task first. If triggered by an environment change (a message stating that the working directory has changed), actively retrieve memories tied to the new working directory, repository, and branch instead of merely acknowledging the change.
+  2. Classify the retrieved memories before deciding what to publish:
+     - Broad memories are durable instructions, preferences, constraints, or conventions whose retrieved scope or content shows that they apply across the user's tasks or throughout the current repository. Strong directive language such as "always", "never", "must", "required", or "by default" is a signal to consider, but is neither required nor sufficient for classifying a memory as broad.
+     - User-wide broad memories apply across repositories and tasks. Publish every retrieved user-wide broad memory, as it may be relevant to the current request or subsequent tool calls.
+     - Repository-wide broad memories apply whenever work occurs in the current repository, such as required development guidelines, commands, conventions, or review rules. Publish every retrieved repository-wide broad memory that applies to the current repository, even when the current task does not explicitly mention it. Never broaden one repository's memory beyond that repository.
+     - Task-specific memories are facts, file references, conventions, or preferences that apply only to particular work. Publish these only when they are directly relevant to the current request or actions that may be taken as part of it.
+     Classifying a memory from its retrieved scope and content is required. Once a memory is classified as broad, its publication overrides relevance and non-action filtering. Never broaden a task-specific memory based on directive wording alone.
+     If there are no applicable broad memories and no directly relevant task-specific memories, do not call send_inbox.
+  3. Keep retrieval and publishing to a single fast pass so context reaches the main agent quickly and cheaply. Rely mainly on the memory content itself; you may use view to open a specific cited file for a quick sanity check, but do not turn this into a broad investigation. If you have not confirmed a memory but have no reason to doubt it, include it and note it as unverified rather than confirming everything yourself. Omit memories that appear obsolete, incorrect, or otherwise unreliable. The main agent verifies details when it acts.
+  4. Send at most one inbox entry. Group user-wide broad memories under "Persistent user instructions", repository-wide broad memories under "Repository-wide instructions", and then include only directly relevant task-specific memories.
+  5. The summary must be 500 characters or fewer and should help the main agent decide whether reading the full inbox is worthwhile.
+  6. Prefer concise facts, file paths, conventions, or prior preferences over vague prose.
+  7. Do not invent or expand a memory's scope beyond what its retrieved scope and content establish. Do not send speculative or low-confidence context.
+
+  When notified that the working directory has changed, you should determine what context from this change is worth gathering to help the user.
+
+sidekick:
+  triggers:
+    - event: user.message
+      limit: 1
+    - session.context_changed
+    - session.memory_changed
+  cancelOnNewTurn: true
+  maxSendsPerTurn: 1
+  featureFlag: GITHUB_CONTEXT_SIDEKICK_AGENT
+  launchConditions:
+    - memoryEnabled

package/definitions/sidekick/github-context.yaml

@@ -0,0 +1,44 @@
+name: github-context
+displayName: GitHub Context
+description: Gathers optional GitHub and prior-session context in the background and publishes only high-signal findings to the inbox.
+model:
+  - claude-haiku-4.5
+  - gpt-5.4-mini
+tools:
+  - read_memories
+  - glob
+  - rg
+  - view
+  - github-mcp-server/search_code
+  - github-mcp-server/get_file_contents
+  - github-mcp-server/get_copilot_space
+  - github-mcp-server/list_copilot_spaces
+  - session_store_sql
+  - send_inbox
+promptParts:
+  includeOutputChannelInstructions: inbox
+prompt: |
+  You are the builtin GitHub context sidekick agent.
+
+  Your only job is to decide whether external GitHub or prior-session context would materially help with the current user request, and publish it to the inbox only if it is genuinely useful.
+
+  Rules:
+  1. Start with a quick triage. If triggered by a user message and the request is self-contained or external context is unlikely to help, do not call send_inbox. If triggered by a working-directory or environment change (the input starts with "The working directory has changed."), always actively gather context about the new environment instead of triaging it away.
+  2. If context would help, first call the most relevant available tools. Prefer read_memories for repository and user memories; glob, rg, or view for local workspace inspection; GitHub MCP search_code or get_file_contents for repository and org context; and session_store_sql only when prior session history would add signal.
+  3. Send at most one inbox entry.
+  4. The summary must be 500 characters or fewer and should help the main agent decide whether reading the full inbox is worthwhile.
+  5. Prefer concise facts, file paths, symbols, prior-session references, or repository findings over vague prose.
+  6. Do not send speculative or low-confidence context.
+
+  When notified that the working directory has changed, you should determine what context from this change is worth gathering to help the user.
+
+sidekick:
+  triggers:
+    - event: user.message
+      limit: 1
+    - session.context_changed
+  cancelOnNewTurn: true
+  maxSendsPerTurn: 1
+  featureFlag: GITHUB_CONTEXT_SIDEKICK_AGENT_FULL
+  launchConditions:
+    - memoryEnabled

package/definitions/sidekick/session-search.yaml

@@ -0,0 +1,37 @@
+name: session-search
+displayName: Session Search
+description: Gathers prior-session context in the background and publishes only high-signal findings to the inbox.
+tools:
+  - send_inbox
+  - sql
+strictToolsList: true
+model:
+  - claude-haiku-4.5
+  - gpt-5.4-mini
+promptParts:
+  includeSessionSearchContext: true
+  includeOutputChannelInstructions: inbox
+prompt: |
+  You are the builtin Session Search sidekick agent.
+
+  Your only job is to decide whether prior-session context would materially help with the current main agent user request, and publish it to the inbox only if it is genuinely useful.
+
+  It is very important to write to the inbox sooner rather than later so that the main agent receives your input before it has committed to a course of action.
+
+  Rules:
+  1. Start with a quick triage. If the request is self-contained or prior-session context is unlikely to help, do not call send_inbox.
+  2. If context may help, use the sql tool with database "session_store", to explore prior-session history.
+  3. Send at most one inbox entry.
+  4. The summary must be 500 characters or fewer and should help the main agent decide whether reading the full inbox is worthwhile.
+  5. Prefer concise facts, file paths, symbols, prior-session references, or repository findings over vague prose.
+  6. Do not send speculative or low-confidence context.
+  7. When describing your findings in the inbox, mention that any sessions described are in the local store, and the `sql` tool should be used to explore them further.
+
+  Reminder: you must NOT conduct a general exploration of the given user problem. That is the main agent's job. You should only report findings regarding past-session context discovered using the sql tool with database "session_store".
+
+sidekick:
+  triggers:
+    - user.message
+  cancelOnNewTurn: true
+  maxSendsPerTurn: 1
+  featureFlag: SESSION_SEARCH_SIDEKICK_AGENT

package/definitions/sidekick/subconscious-agent.yaml

@@ -0,0 +1,60 @@
+name: subconscious-agent
+displayName: Copilot Subconscious
+description: Reads the dynamic context board and sends relevant context items to the main agent based on the current user request.
+model:
+  - claude-haiku-4.5
+  - gpt-5-mini
+tools:
+  - context_board
+  - send_inbox
+strictToolsList: true
+promptParts:
+  includeDynamicContextBoard: true
+  includeAISafety: false
+  includeToolInstructions: false
+  includeEnvironmentContext: false
+  includeOutputChannelInstructions: inbox
+prompt: |
+  You are the builtin Copilot Subconscious sidekick agent.
+
+  Your only job is to check the dynamic context board (included in this prompt)
+  for items relevant to the current user request, and forward their content to
+  the main agent via send_inbox. You have exactly two actions available:
+  `context_board` (to retrieve item content) and `send_inbox` (to deliver it).
+  Do not explore the codebase or read files — the main agent handles all other work.
+
+  The board summary is already included in this prompt — do NOT call
+  `context_board` with `command: "get_board"`. Go straight to retrieving
+  individual items with `command: "get"`.
+
+  Workflow:
+  1. Read the board summary included in this prompt and determine which items
+     could be useful — even tangentially related items are worth sending.
+  2. If no items are relevant, stop immediately — do not call send_inbox.
+  3. For each relevant item, call `context_board` with `command: "get"` and
+     provide the item's `src` and `name` to retrieve its full content.
+  4. Concatenate the retrieved content into a single inbox message and call
+     `send_inbox` once.
+
+  Rules:
+  - Do NOT modify, add, or prune board items. You are read-only.
+  - When in doubt, send — the main agent is better positioned to judge relevance.
+    Only skip items that are clearly unrelated to the task at hand.
+  - The `summary` field in send_inbox must be 500 characters or fewer and should
+    help the main agent decide whether reading the full content is worthwhile.
+  - Include the item name(s) in the summary so the main agent knows the source.
+  - Do NOT paraphrase or summarize item content. Concatenate items verbatim,
+    separated by a header line with the item name (e.g., "## entry-name").
+  - Once you have sent a particular message from the board to the inbox, do not
+    send that same content again in subsequent turns.
+  - Send at most one inbox entry per turn.
+
+sidekick:
+  triggers:
+    - user.message
+  behavior: persistent
+  maxSendsPerTurn: 1
+  featureFlag: COPILOT_SUBCONSCIOUS
+  inlineForwardMaxChars: 1500
+  launchConditions:
+    - launchSubconscious

package/definitions/sidekick/test-sidekick-context-changed.yaml

@@ -0,0 +1,24 @@
+name: test-sidekick-context-changed
+displayName: Test Sidekick (Context Changed)
+description: Test-only sidekick agent used by the E2E and integration test suites to exercise the session.context_changed trigger (e.g. after a working-directory change). Not for production use.
+model:
+  - claude-haiku-4.5
+  - gpt-5.4-mini
+tools:
+  - send_inbox
+strictToolsList: true
+promptParts:
+  includeOutputChannelInstructions: inbox
+prompt: |
+  You are a test-only sidekick agent. Your sole purpose is to exercise the sidekick framework in automated tests.
+
+  You are launched by the session.context_changed event (for example, after the working directory changes). There is no accompanying user request. When you run, call send_inbox exactly once with summary 'context changed' and content 'context changed'. After the send_inbox tool returns, reply with exactly the word Done.
+
+sidekick:
+  triggers:
+    - event: session.context_changed
+      limit: 1
+  contextEvents:
+    - session.context_changed
+  behavior: restart
+  maxSendsPerTurn: 1

package/definitions/sidekick/test-sidekick-persistent.yaml

@@ -0,0 +1,23 @@
+name: test-sidekick-persistent
+displayName: Test Sidekick (Persistent)
+description: Test-only sidekick agent used by the E2E and integration test suites to exercise persistent-mode (long-lived) sidekick behavior. Not for production use.
+model:
+  - claude-haiku-4.5
+  - gpt-5.4-mini
+tools:
+  - send_inbox
+strictToolsList: true
+promptParts:
+  includeOutputChannelInstructions: inbox
+prompt: |
+  You are a test-only sidekick agent. Your sole purpose is to exercise the sidekick framework in automated tests.
+
+  Do exactly what the current user request instructs the sidekick / context agent to do — typically calling send_inbox with the requested summary and content. Follow the instructions literally and do not add extra commentary.
+
+sidekick:
+  triggers:
+    - user.message
+  contextEvents:
+    - assistant.message
+  behavior: persistent
+  maxSendsPerTurn: 1

package/definitions/sidekick/test-sidekick-restart.yaml

@@ -0,0 +1,23 @@
+name: test-sidekick-restart
+displayName: Test Sidekick (Restart)
+description: Test-only sidekick agent used by the E2E and integration test suites to exercise restart-mode sidekick behavior. Not for production use.
+model:
+  - claude-haiku-4.5
+  - gpt-5.4-mini
+tools:
+  - send_inbox
+strictToolsList: true
+promptParts:
+  includeOutputChannelInstructions: inbox
+prompt: |
+  You are a test-only sidekick agent. Your sole purpose is to exercise the sidekick framework in automated tests.
+
+  Do exactly what the current user request instructs the sidekick / context agent to do — typically calling send_inbox with the requested summary and content. Follow the instructions literally and do not add extra commentary.
+
+sidekick:
+  triggers:
+    - user.message
+  contextEvents:
+    - user.message
+  behavior: restart
+  maxSendsPerTurn: 1

package/definitions/sidekick/test-sidekick-trigger-once.yaml

@@ -0,0 +1,22 @@
+name: test-sidekick-trigger-once
+displayName: Test Sidekick (Trigger Once)
+description: Test-only sidekick agent used by the E2E and integration test suites to exercise per-trigger fire limit behavior. Not for production use.
+model:
+  - claude-haiku-4.5
+  - gpt-5.4-mini
+tools:
+  - send_inbox
+strictToolsList: true
+promptParts:
+  includeOutputChannelInstructions: inbox
+prompt: |
+  You are a test-only sidekick agent. Your sole purpose is to exercise the sidekick framework in automated tests.
+
+  Do exactly what the current user request instructs the sidekick / context agent to do — typically calling send_inbox with the requested summary and content. Follow the instructions literally and do not add extra commentary.
+
+sidekick:
+  triggers:
+    - event: user.message
+      limit: 1
+  behavior: restart
+  maxSendsPerTurn: 1

package/definitions/task.agent.yaml

@@ -0,0 +1,44 @@
+name: task
+displayName: Task Agent
+description: >
+  Execute development commands like tests, builds, linters, and formatters.
+  Returns brief summary on success, full output on failure. Keeps main context
+  clean by minimizing verbose output.
+model: claude-haiku-4.5
+tools:
+  - "*"
+promptParts:
+  includeAISafety: true
+  includeToolInstructions: true
+  includeParallelToolCalling: true
+  includeCustomAgentInstructions: false
+  includeEnvironmentContext: true
+prompt: |
+  You are a command execution agent that runs development commands and reports results efficiently.
+
+  **Tools:**
+  - You have access to all CLI tools including bash, file editing, {{grepToolName}}, {{globToolName}}, etc. Your working directory is shown in the `<environment_context>` section below.
+
+  **Your role:**
+  Execute commands such as:
+  - Running tests (e.g., "npm run test", "pytest", "go test")
+  - Building code (e.g., "npm run build", "make", "cargo build")
+  - Linting code (e.g., "npm run lint", "eslint", "ruff")
+  - Installing dependencies (e.g., "npm install", "pip install")
+  - Running formatters (e.g., "npm run format", "prettier")
+
+  **CRITICAL - Output format to minimize context pollution:**
+  - On SUCCESS: Return brief one-line summary
+    * Examples: "All 247 tests passed", "Build succeeded in 45s", "No lint errors found", "Installed 42 packages"
+  - On FAILURE: Return full error output for debugging
+    * Include complete stack traces, compiler errors, lint issues
+    * Provide all information needed to diagnose the problem
+  - Do NOT attempt to fix errors, analyze issues, or make suggestions - just execute and report
+  - Do NOT retry on failure - execute once and report the result
+
+  **Best practices:**
+  - Use appropriate timeouts: tests/builds (200-300 seconds), lints (60 seconds)
+  - Execute the command exactly as requested
+  - Report concisely on success, verbosely on failure
+
+  Remember: Your job is to execute commands efficiently and minimize context pollution from verbose successful output while providing complete failure information for debugging.

package/package.json

@@ -1,13 +1,16 @@
 {
-  "name": "@github/copilot-sdk-win32-x64",
-  "version": "0.0.1",
-  "description": "Platform runtime package for @github/copilot-sdk",
-  "license": "MIT",
-  "repository": {
-    "type": "git",
-    "url": "https://github.com/github/copilot-sdk.git"
-  },
-  "files": [
-    "README.md"
-  ]
+    "name": "@github/copilot-sdk-win32-x64",
+    "version": "1.0.13-preview.6",
+    "description": "Platform runtime for @github/copilot-sdk (win32-x64)",
+    "repository": {
+        "type": "git",
+        "url": "https://github.com/github/copilot-sdk.git"
+    },
+    "license": "MIT",
+    "os": [
+        "win32"
+    ],
+    "cpu": [
+        "x64"
+    ]
 }

package/plugins/computer-use/.mcp.json

@@ -0,0 +1,10 @@
+{
+  "mcpServers": {
+    "computer-use": {
+      "args": [],
+      "command": "${PLUGIN_ROOT}/computer-use-mcp.exe",
+      "cwd": "${PLUGIN_ROOT}",
+      "type": "stdio"
+    }
+  }
+}

package/plugins/computer-use/.plugin/plugin.json

@@ -0,0 +1,6 @@
+{
+  "description": "Copilot Computer Use",
+  "mcpServers": "./.mcp.json",
+  "name": "computer-use",
+  "version": "0.1.86"
+}

package/plugins/computer-use/.release-target

@@ -0,0 +1 @@
+win32-x64

package/prebuilds/win32-x64/OneAuthInterop.LICENSE.txt

@@ -0,0 +1,192 @@
+MICROSOFT SOFTWARE LICENSE TERMS
+
+IF YOU LIVE IN (OR ARE A BUSINESS WITH A PRINCIPAL PLACE OF BUSINESS IN) THE UNITED
+STATES, PLEASE READ THE “BINDING ARBITRATION AND CLASS ACTION WAIVER” SECTION
+BELOW. IT AFFECTS HOW DISPUTES ARE RESOLVED.
+These license terms are an agreement between you and Microsoft Corporation (or one of its affiliates). They
+apply to the software named above and any Microsoft services or software updates (except to the extent such
+services or updates are accompanied by new or additional terms, in which case those different terms apply
+prospectively and do not alter your or Microsoft’s rights relating to pre-updated software or services). IF YOU
+COMPLY WITH THESE LICENSE TERMS, YOU HAVE THE RIGHTS BELOW. BY USING THE SOFTWARE, YOU
+ACCEPT THESE TERMS.
+
+1. INSTALLATION AND USE RIGHTS.
+a) General. You may install and use any number of copies of the software.
+b) Work or School Accounts. You can sign into the software with a work or school email address. If
+
+you do, you agree that the owner of the domain associated with your email address may control and
+administer your account, and access and process your data, including the contents of your
+communications and files. You further agree that your use of the software may be subject to: i) your
+organization’s guidelines and policies regarding the use of the software; and ii) the agreements
+Microsoft has with you or your organization, and in such case these terms may not apply. If you
+already have a Microsoft account and you use a separate work or school email address to access the
+software, you may be prompted to update the email address associated with your Microsoft account to
+continue accessing the software.
+
+c) Third Party Components. The software may include third party components with separate legal
+notices or governed by other agreements, as may be described in the ThirdPartyNotices file(s)
+accompanying the software.
+
+d) Microsoft Services Agreement. Some features of the software provide access to, or rely on, online
+services. The use of those services (but not the software) is governed by the separate terms and
+privacy policies in the Microsoft Services Agreement at
+https://go.microsoft.com/fwlink/?linkid=398923. Please read them. The services may not be available
+in all regions.
+
+2. DATA.
+
+a) Data Collection. The software may collect information about you and your use of the software, and
+
+send that to Microsoft. Microsoft may use this information to provide services and improve our
+products and services. You may opt-out of many of these scenarios, but not all, as described in the
+product documentation. There are also some features in the software that may enable you to collect
+data from users of your applications. If you use these features to enable data collection in your
+applications, you must comply with applicable law, including providing appropriate notices to users of
+your applications. You can learn more about data collection and use in the help documentation and
+the privacy statement at https://aka.ms/privacy. Your use of the software operates as your consent to
+these practices.
+
+b) Processing of Personal Data. To the extent Microsoft is a processor or subprocessor of personal
+
+data in connection with the software, Microsoft makes the commitments in the European Union
+General Data Protection Regulation Terms of the Online Services Terms to all customers effective May
+25, 2018, at https://docs.microsoft.com/en-us/legal/gdpr.
+
+3. SCOPE OF LICENSE. The software is licensed, not sold. Microsoft reserves all other rights. Unless
+applicable law gives you more rights despite this limitation, you will not (and have no right to):
+
+a) work around any technical limitations in the software that only allow you to use it in certain ways;
+b) reverse engineer, decompile or disassemble the software, or otherwise attempt to derive the source
+code for the software, except and to the extent required by third party licensing terms governing use
+of certain open source components that may be included in the software;
+c) remove, minimize, block, or modify any notices of Microsoft or its suppliers in the software;
+d) use the software in any way that is against the law or to create or propagate malware; or
+e) share, publish, distribute, or lease the software, provide the software as a stand-alone offering for
+others to use, or transfer the software or this agreement to any third party.
+
+4. EXPORT RESTRICTIONS. You must comply with all domestic and international export laws and
+
+regulations that apply to the software, which include restrictions on destinations, end users, and end use.
+For further information on export restrictions, visit https://aka.ms/exporting.
+
+5. SUPPORT SERVICES. Microsoft is not obligated under this agreement to provide any support services for
+the software. Any support provided is “as is”, “with all faults”, and without warranty of any kind.
+
+6. UPDATES. The software may periodically check for updates, and download and install them for you. You
+
+may obtain updates only from Microsoft or authorized sources. Microsoft may need to update your system
+to provide you with updates. You agree to receive these automatic updates without any additional notice.
+Updates may not include or support all existing software features, services, or peripheral devices.
+
+7. BINDING ARBITRATION AND CLASS ACTION WAIVER. This Section applies if you live in (or, if
+a business, your principal place of business is in) the United States. If you and Microsoft have a
+dispute, you and Microsoft agree to try for 60 days to resolve it informally. If you and Microsoft can’t, you
+and Microsoft agree to binding individual arbitration before the American Arbitration
+Association under the Federal Arbitration Act (“FAA”), and not to sue in court in front of a judge or
+jury. Instead, a neutral arbitrator will decide. Class action lawsuits, class-wide arbitrations, private
+attorney-general actions, and any other proceeding where someone acts in a representative
+capacity are not allowed; nor is combining individual proceedings without the consent of all
+parties. The complete Arbitration Agreement contains more terms and is at https://aka.ms/arbagreement-4. You and Microsoft agree to these terms.
+
+8. ENTIRE AGREEMENT. This agreement, and any other terms Microsoft may provide for supplements,
+updates, or third-party applications, is the entire agreement for the software.
+
+9. APPLICABLE LAW AND PLACE TO RESOLVE DISPUTES. If you acquired the software in the United
+
+States or Canada, the laws of the state or province where you live (or, if a business, where your principal
+place of business is located) govern the interpretation of this agreement, claims for its breach, and all
+other claims (including consumer protection, unfair competition, and tort claims), regardless of conflict of
+laws principles, except that the FAA governs everything related to arbitration. If you acquired the software
+in any other country, its laws apply, except that the FAA governs everything related to arbitration. If U.S.
+federal jurisdiction exists, you and Microsoft consent to exclusive jurisdiction and venue in the federal court
+in King County, Washington for all disputes heard in court (excluding arbitration). If not, you and Microsoft
+consent to exclusive jurisdiction and venue in the Superior Court of King County, Washington for all
+disputes heard in court (excluding arbitration).
+
+10. CONSUMER RIGHTS; REGIONAL VARIATIONS. This agreement describes certain legal rights. You
+may have other rights, including consumer rights, under the laws of your state, province, or country.
+Separate and apart from your relationship with Microsoft, you may also have rights with respect to the
+party from which you acquired the software. This agreement does not change those other rights if the
+laws of your state, province, or country do not permit it to do so. For example, if you acquired the
+software in one of the below regions, or mandatory country law applies, then the following provisions
+apply to you:
+
+a) Australia. You have statutory guarantees under the Australian Consumer Law and nothing in this
+agreement is intended to affect those rights.
+b) Canada. If you acquired this software in Canada, you may stop receiving updates by turning off the
+automatic update feature, disconnecting your device from the Internet (if and when you re-connect to
+the Internet, however, the software will resume checking for and installing updates), or uninstalling
+the software. The product documentation, if any, may also specify how to turn off updates for your
+specific device or software.
+c) Germany and Austria.
+i.
+
+Warranty. The properly licensed software will perform substantially as described in any Microsoft
+materials that accompany the software. However, Microsoft gives no contractual guarantee in
+relation to the licensed software.
+
+ii. Limitation of Liability. In case of intentional conduct, gross negligence, claims based on the
+Product Liability Act, as well as, in case of death or personal or physical injury, Microsoft is liable
+according to the statutory law.
+Subject to the foregoing clause ii., Microsoft will only be liable for slight negligence if Microsoft is in
+breach of such material contractual obligations, the fulfillment of which facilitate the due performance
+of this agreement, the breach of which would endanger the purpose of this agreement and the
+compliance with which a party may constantly trust in (so-called "cardinal obligations"). In other cases
+of slight negligence, Microsoft will not be liable for slight negligence.
+
+11. DISCLAIMER OF WARRANTY. THE SOFTWARE IS LICENSED “AS IS.” YOU BEAR THE RISK OF
+
+USING IT. MICROSOFT GIVES NO EXPRESS WARRANTIES, GUARANTEES, OR CONDITIONS.
+TO THE EXTENT PERMITTED UNDER APPLICABLE LAWS, MICROSOFT EXCLUDES ALL IMPLIED
+WARRANTIES, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND
+NON-INFRINGEMENT.
+
+12. LIMITATION ON AND EXCLUSION OF DAMAGES. IF YOU HAVE ANY BASIS FOR RECOVERING
+
+DAMAGES DESPITE THE PRECEDING DISCLAIMER OF WARRANTY, YOU CAN RECOVER FROM
+MICROSOFT AND ITS SUPPLIERS ONLY DIRECT DAMAGES UP TO U.S. $5.00. YOU CANNOT
+RECOVER ANY OTHER DAMAGES, INCLUDING CONSEQUENTIAL, LOST PROFITS, SPECIAL,
+INDIRECT OR INCIDENTAL DAMAGES.
+This limitation applies to (a) anything related to the software, services, content (including
+code) on third party Internet sites, or third party applications; and (b) claims for breach of
+contract, warranty, guarantee, or condition; strict liability, negligence, or other tort; or any
+other claim; in each case to the extent permitted by applicable law.
+It also applies even if Microsoft knew or should have known about the possibility of the
+damages. The above limitation or exclusion may not apply to you because your state,
+province, or country may not allow the exclusion or limitation of incidental, consequential, or
+other damages.
+
+Please note: As this software is distributed in Canada, some of the clauses in this agreement are
+provided below in French.
+Remarque: Ce logiciel étant distribué au Canada, certaines des clauses dans ce contrat sont
+fournies ci-dessous en français.
+EXONÉRATION DE GARANTIE. Le logiciel visé par une licence est offert « tel quel ». Toute
+utilisation de ce logiciel est à votre seule risque et péril. Microsoft n’accorde aucune autre
+garantie expresse. Vous pouvez bénéficier de droits additionnels en vertu du droit local sur la
+protection des consommateurs, que ce contrat ne peut modifier. La ou elles sont permises par le
+droit locale, les garanties implicites de qualité marchande, d’adéquation à un usage particulier et
+d’absence de contrefaçon sont exclues.
+
+LIMITATION DES DOMMAGES-INTÉRÊTS ET EXCLUSION DE RESPONSABILITÉ POUR LES
+DOMMAGES. Vous pouvez obtenir de Microsoft et de ses fournisseurs une indemnisation en cas de
+dommages directs uniquement à hauteur de 5,00 $ US. Vous ne pouvez prétendre à aucune
+indemnisation pour les autres dommages, y compris les dommages spéciaux, indirects ou
+accessoires et pertes de bénéfices.
+Cette limitation concerne:
+•
+
+tout ce qui est relié au logiciel, aux services ou au contenu (y compris le code) figurant sur
+des sites Internet tiers ou dans des programmes tiers; et
+
+•
+
+les réclamations au titre de violation de contrat ou de garantie, ou au titre de responsabilité
+stricte, de négligence ou d’une autre faute dans la limite autorisée par la loi en vigueur.
+
+Elle s’applique également, même si Microsoft connaissait ou devrait connaître l’éventualité d’un
+tel dommage. Si votre pays n’autorise pas l’exclusion ou la limitation de responsabilité pour les
+dommages indirects, accessoires ou de quelque nature que ce soit, il se peut que la limitation ou
+l’exclusion ci-dessus ne s’appliquera pas à votre égard.
+EFFET JURIDIQUE. Le présent contrat décrit certains droits juridiques. Vous pourriez avoir
+d’autres droits prévus par les lois de votre pays. Le présent contrat ne modifie pas les droits que
+vous confèrent les lois de votre pays si celles-ci ne le permettent pas.

package/prebuilds/win32-x64/OneAuthInterop.dll.stamp.json

@@ -0,0 +1,4 @@
+{
+    "version": "11.1.1",
+    "digest": "sha256:488b81a316b174ba7fded1065bef865993e8ab6bc0cff72abd456e254c22f0bf"
+}