Add audit agent knowledge base

.gitignore

+# Local audit scratch workspace; may contain cloned project repos and private customer data.
+.audit-work/

AGENTS.md

+# Repository Guidelines
+
+## Project Structure & Module Organization
+This repository is a Markdown-based SAP knowledge base. Keep content in the existing domain folders:
+
+- `KB_SA/`: solution architecture prompts, scope guides, process architecture, product overview, and domain capability documents.
+- `KB_SC/`: scenario and configuration knowledge base files, grouped by SAP area such as `FI`, `MM`, `SD`, `PP`, `WM`, and master data.
+- `KB构建方法论/`: methodology and best-practice documents for knowledge-base construction.
+- `prompts/`: reusable agent prompts, including the project KB audit agent prompt.
+- `tools/`: read-only utility scripts for auditing KB workspaces.
+
+Add new files to the closest matching folder. Preserve existing prefixes such as `KB_SD_`, `KB_MM_`, `FSD_`, and numbered process files so navigation remains predictable.
+
+## Build, Test, and Development Commands
+There is no application build step or package manager configuration in this workspace. Use lightweight repository checks:
+
+- `rg --files`: list all repository files quickly.
+- `rg "search term" KB_SA KB_SC`: search knowledge-base content.
+- `Get-ChildItem -Recurse -Filter *.md`: inspect Markdown inventory in PowerShell.
+- `powershell -ExecutionPolicy Bypass -File tools\kb-audit.ps1 -Workspace <path> -ProjectKbDir <dir> -OutDir audit-output`: run the static project KB audit scan and generate review templates.
+
+The audit script writes reports only to `-OutDir`; it must not modify the audited KB workspace.
+
+Before sharing changes, preview edited Markdown in an editor that supports Markdown rendering and verify links, headings, and tables manually.
+
+## Coding Style & Naming Conventions
+Write Markdown with clear heading hierarchy and short, task-oriented sections. Use ATX headings (`#`, `##`, `###`) and fenced code blocks for examples. Prefer descriptive English file names for SAP scope items already using English names; keep Chinese names where they match existing methodology documents. Do not rename existing files unless the navigation map and all references are updated in the same change.
+
+## Testing Guidelines
+No automated test framework is currently configured. Validate documentation changes by checking:
+
+- Internal links point to existing files.
+- Tables render correctly.
+- SAP scope item IDs, process names, and terminology are consistent with neighboring documents.
+- Navigation index files, such as `KB_00_Navigation_Map.md` and `KB_00_SC_Navigation_Map.md`, are updated when adding or removing major content.
+- Audit tool output includes `static_findings.json`, `static_audit_report.md`, `manual_review_checklist.md`, `acceptance_tests.md`, `ai_answer_sheet.md`, and `scoring_matrix.csv`.
+
+For a smoke test, run the audit tool once against this repository and once against a project workspace that contains a project KB such as `KB_Majesty/`.
+
+## Commit & Pull Request Guidelines
+This working copy does not include Git history, so no repository-specific commit convention can be verified. Use concise imperative commit messages, for example `Add SD rebate scenario notes` or `Update SA navigation map`.
+
+Pull requests should describe the affected knowledge area, list added or changed files, mention any navigation-map updates, and call out terminology or scope assumptions for reviewer focus.
+
+## Security & Configuration Tips
+Do not commit customer secrets, credentials, private project data, or unpublished commercial terms. When examples require sensitive values, use placeholders such as `<customer-name>`, `<system-id>`, or `<tenant-url>`.