Update repo docs (2312 examples, 31 categories)

Author: agent-aspose-pdf-examples

.github/copilot-instructions.md

@@ -0,0 +1,25 @@
+# Copilot Instructions
+
+This repository is a curated collection of validated, build-tested C# examples for **Aspose.PDF for .NET (26.5.0)** targeting **net10.0**.
+
+The canonical coding-agent guide is [`AGENTS.md`](../AGENTS.md) at the repository root, and there is one per category folder. **Read those first** before suggesting changes.
+
+## When suggesting code in this repository
+
+- Match the style of the surrounding `.cs` files. They are self-contained `dotnet new console` examples, not a multi-file project.
+- Use fully-qualified `Aspose.Pdf.*` types (e.g. `Aspose.Pdf.Drawing.Path`) so `System.IO.Path` does not shadow them.
+- Wrap every `IDisposable` in a `using` block. `Document` in particular must be disposed deterministically.
+- Aspose.PDF uses **1-based** page indexing (`pdfDoc.Pages[1]` is the first page). Off-by-one is the most common bug.
+- Write errors to `Console.Error.WriteLine` with the `Error:` prefix. Successful operations log to `Console.WriteLine`.
+
+## Do not
+
+- Edit `AGENTS.md`, `index.json`, or `README.md` by hand. They are regenerated by an external generator and your edits will be overwritten.
+- Add a `.csproj` per example. CI synthesises one at validation time; shipping one would conflict.
+- Suggest API calls that do not exist in `Aspose.PDF` package version 26.5.0. If you are not sure, check `index.json` for the apis_used field on neighbouring examples in the same category.
+
+## Where to look for context
+
+- [`AGENTS.md`](../AGENTS.md) -- repository-wide conventions, anti-patterns, domain knowledge.
+- `<category>/AGENTS.md` -- category-specific tips and the file table.
+- [`CONTRIBUTING.md`](../CONTRIBUTING.md) -- the human-oriented contribution rules.

.github/pull_request_template.md

@@ -0,0 +1,39 @@
+## Summary
+
+<!-- One or two sentences: what does this PR change and why. -->
+
+## Changed examples / categories
+
+<!-- List the files or categories touched. e.g.
+- `working-with-text/extract-text-from-page.cs`
+- `working-with-annotations/` (new file: `add-text-annotation.cs`)
+-->
+
+## Validation
+
+- [ ] `dotnet build` succeeded for every changed `.cs` file (paste the final line of output below).
+- [ ] `dotnet run` was executed for every changed example. Outcome:
+  - [ ] Ran to completion successfully
+  - [ ] Failed at runtime due to a missing input file (note which file below)
+  - [ ] Skipped runtime testing (explain why below)
+
+```
+<!-- Paste the relevant dotnet build / dotnet run output here. -->
+```
+
+## Missing input files
+
+<!-- If any example expects an input file (input.pdf, sample.docx, etc.) that is
+     NOT included in the repo, list them here so the CI runtime check failure is
+     expected. -->
+
+- None
+
+## Generated metadata
+
+- [ ] I did NOT hand-edit `index.json`, `AGENTS.md`, `README.md`, or `.github/copilot-instructions.md`.
+- [ ] If a generated file looks wrong, I have opened an issue on the generator repo (or this PR fixes it upstream).
+
+## Additional notes
+
+<!-- Optional: anything reviewers should know. -->