📖 [Docs]: AGENTS.md added to Memory Repository Template scaffold (#77)

## Why

A sibling session auditing the live ecosystem found that both
instantiated memory
repos — `MSXOrg/memory` and `PSModule/memory` — were missing
`AGENTS.md`, the
cross-client agent entry point that [design.md's client behavior

table](https://msxorg.github.io/docs/Frameworks/Agentic-Development/design/#client-behavior)
says every repository in the framework carries: "Cross-client agents |
`AGENTS.md` |
Read the shared project pointer and local nuance."

Tracing it back, the gap isn't just in those two repos — it's in the
template they
were scaffolded from. `memory-template.md` (introduced in #70) never
listed
`AGENTS.md` in its `## Scaffold` file tree, so any future memory
repository
instantiated from this template would launch missing it too.

**Note:** `MSXOrg/memory` and `PSModule/memory` have already been fixed
directly
(their `AGENTS.md` files exist and work today). This PR doesn't need to
land for
those two repos to be correct — it's solely so future memory
repositories get
`AGENTS.md` from day one.

## What changed

- Added `AGENTS.md` to the `## Scaffold` code-fence tree, right after
`README.md`/`CONTRIBUTING.md`, with an inline comment describing its
purpose.
- Added a paragraph explaining that `AGENTS.md` doesn't map to a
`memory` ownership
bullet from `design.md#memory` — it's the framework's
client-behavior-table entry
point instead, distinct from `CONTRIBUTING.md`'s contribution-process
framing even
  though this repo's real audience is agents.
- Updated the "A memory repository still carries README.md,
CONTRIBUTING.md,
.gitattributes, and .gitignore" sentence in the Repository Standard
exception
  section to include `AGENTS.md`.

## Validation

- `.github/scripts/Test-DocumentationLink.ps1` — all links resolve.
- `markdownlint-cli` against `.github/linters/.markdown-lint.yml` on the
changed
  file — clean.
- `.github/scripts/Update-DocumentationIndex.ps1 -Check` reports
pre-existing drift
across many unrelated index files on `main` (confirmed by stashing this
change and
re-running) — not caused by this PR, and this page's front matter
(`title`/
  `description`) is unchanged, so it adds no new drift.

Follow-up to #70 (which introduced `memory-template.md`).

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

Author: MariusStorhaug

src/docs/Frameworks/Agentic-Development/memory-template.md

@@ -18,6 +18,7 @@ organization; structure does not.
 memory/
 ├── README.md        # front door: what this repo is, that it's private, "commit straight to main, no PR"
 ├── CONTRIBUTING.md   # short: direct push to main, no PR/review gate, keep entries short/dated/factual
+├── AGENTS.md         # cross-client agent entry point: orients an agent landing here cold, points at index.md and the memory-writing rules
 ├── .gitattributes
 ├── .gitignore
 ├── index.md          # OKF root index (okf_version frontmatter), links to the sections below
@@ -48,6 +49,16 @@ top-level folder is one of those responsibilities made concrete:
 it links to `gotchas/index.md`, `knowledge/index.md`, and `agents/index.md` so a human or
 agent can start at the root and drill inward.
 
+`AGENTS.md` doesn't map to a `memory` ownership bullet — it isn't content memory owns, it's the
+framework's [client behavior table](design.md#client-behavior) entry point: "Cross-client agents |
+`AGENTS.md` | Read the shared project pointer and local nuance." Every repository in the
+framework carries one so an agent landing cold knows where to start; a `memory` repository is no
+exception. Its job is narrower than `README.md`'s and different from `CONTRIBUTING.md`'s — it
+orients an *agent* specifically, pointing straight at `index.md` and the
+[memory writing rules](design.md#memory-writing-rules), while `CONTRIBUTING.md` stays
+contribution-process-flavored (direct push, no PR) even though this repository's real audience is
+agents, not human contributors.
+
 ## A deliberate exception to the Repository Standard
 
 [Repository Standard](../../Ways-of-Working/Repository-Standard.md) lists the files every
@@ -75,8 +86,8 @@ exception, made explicit rather than left as an oversight:
   expectations for a broad or public contributor community; a `memory` repository's
   audience is the organization's own humans and agents.
 
-A `memory` repository still carries `README.md`, `CONTRIBUTING.md`, `.gitattributes`, and
-`.gitignore` — the minimum needed to explain itself and behave predictably in git.
+A `memory` repository still carries `README.md`, `CONTRIBUTING.md`, `AGENTS.md`, `.gitattributes`,
+and `.gitignore` — the minimum needed to explain itself and behave predictably in git.
 
 ## Visibility