REPO REFACTOR — FOUR-STACK LAYOUT IN EFFECT. The original single-stack tree (backend/, frontend/, orchestrator/, infra/, docker-compose.yml at the repo root) has been split into four independently deployable stacks and underscore-prefixed support directories. See _docs/REFACTORING_PLAN.md for the long-form plan; the layout table below is the source of truth for path-specific guidance. | Concern | Location | |--------------------------|-------------------------------------------------| | Submitters stack (active)| submitters/{backend,frontend,orchestrator}/ | | Receivers stack | receivers/{backend,frontend,orchestrator}/ | | Platform stack (phase-0) | platform/main.py, platform/docker-compose.yml| | Providers stack (phase-0)| providers/main.py,…
This repository is a read-only-by-default Azure capacity/enablement toolkit. The full agent guidance lives in ../AGENTS.md — read it before running anything. Non-negotiable rules: - READ-ONLY BY DEFAULT. With the analysis scripts, never create, modify, delete, scale or restart any Azure resource — the only writes are local files under output/. No az ... create/update/delete/set, no New-Az* / Set-Az* / Remove-Az*, no terraform apply, no kubectl apply/delete on your own initiative. - One opt-in write tool. Deploy-QuotaGroups.ps1 (with New-QuotaGroupConfig.ps1) provisions quota…
The main notebook applications/storm_impact_assessment/hurricane_forecast_infra_impact.ipynb is 1.57 MB / 19K JSON lines / 71 cells with 1.07 MB of embedded outputs. This exceeds VS Code's diff editor limits and causes Copilot edit tools (edit_notebook_file, replace_string_in_file) to fail silently or produce corrupt edits. When making complex edits with multiline old/new text:
Read AGENTS.md first. It is the master entry point for all repository guidance, including verification, conventions, and required PR and work-item telemetry. Follow its linked documents. Do not duplicate that guidance here; update the topic's authoritative document.
You are an AI coding agent specialized in building and maintaining Microsoft Power Platform solutions. This repository contains an unpacked Power Platform solution stored as source-controlled files. Your job is…
This file is the source of truth for any AI agent working in this repository. Address the human as Mr. Das (an alt of Iron Man), "Sir", or something similar. dry4csharp is a high-fidelity C# port of the Java tool dry4java (read-only sibling at ../dry4java). It is a duplicate-code detector for C# projects: Roslyn parses C# source, each candidate declaration's syntax tree is normalized (names/literals dropped) into structural fingerprints, and candidate pairs are compared by Jaccard similarity. Product intent, locked…
- Use Node.js 22, matching the GitHub Actions workflows. - Install the locked dependencies with npm ci. - Start the local Vite server with npm run dev. - Validate the visual contract with npm run design:lint. - Run the production validation with npm run build. This runs tsc --noEmit before the Vite multi-page build. - Run only the TypeScript check with npm run typecheck. - Preview the generated dist/ artifact with npm run preview. - No test runner or general…
This file is the source of truth for any AI agent working in this repository. Address the human as Mr. Das (an alt of Iron Man), "Sir", or something similar. mutate4csharp is a high-fidelity C# port of the Java tool mutate4java (read-only sibling at ../mutate4java). It is a mutation-testing tool for C# projects: Roslyn for AST parsing + mutation, Coverlet → Cobertura for coverage, dotnet test / MSBuild as the driver. The live product contract — identity, locked decisions, the…
This is a dependency-free static site with no configured build, test, or lint scripts. There is no automated test suite or single-test command. Validate changes in a browser at desktop and mobile widths, including both color themes, search filtering, sticky navigation links, and expanding/collapsing resource sections. Always update CHANGELOG.md with additions/removals from the sites. Follow the Keep a Changelog convention at https://keepachangelog.com/en/1.0.0/. When updating CHANGELOG.md, make sure there is a newline between the header and the paragraph text.
Follow the repository-wide guidance in AGENTS.md. When changing the VS Code extension, also follow the scoped guidance in vscode-codesearch/AGENTS.md. Keep instructions in those AGENTS.md files authoritative. Do not duplicate long-form guidance here.
For Linux systems, first install the following 4 Linux packages with the package manager of the distribution: For both Linux and Windows systems, run the following to install all other required dependencies: Build specific packages using: It auto fixes formatting issues. This ensures all source code follows rustfmt standards. Always run copyright checks before committing: It auto fixes copyright issues. This ensures all source code has correct copyright headers. Run cargo xtask cbindgen (no --fix) to verify the committed header…
These instructions apply to every AI agent session working on this repository, regardless of platform (Linux, Windows, macOS) or context window state. Read this file in its entirety before making any changes. AI can produce code very fast, but bad code is more expensive than ever: a codebase that is hard to change is a codebase where AI compounds entropy on every iteration. Optimize for a codebase that is easy to change, easy to test, and easy to reason about.…
This is the repository's only agent instruction file. Read docs/quality-spec.md before changing code. It is the general quality standard for durable engineering principles, not an implementation manual or a catalog of current technical contracts. Keep it focused on correctness, security, reliability, maintainability, performance, testing, and documentation standards. Do not add file layouts, workflow matrices, exact implementation behavior, incident histories, or step-by-step operational instructions. Keep executable contracts in source, tests, build configuration, and workflows; keep contributor procedures in contributor documentation. Update…
This repository contains sample projects demonstrating how to use the Azure Connectors .NET SDK, including design-time generated POCOs from dynamic schema operations. Code must follow the team's coding conventions based on BPM repo standards. Each connector's sample functions must be in a dedicated file named {Connector}Functions.cs: Variable naming rules: ALWAYS use this multi-line format: Boolean parameters MUST always use named arguments:
MicrosoftReads credentialsCopilot instructions