[marklysze]

What changed, and why?

Adds one paragraph to the ## Identity section of CLAUDE.md, and regenerates AGENTS.md with scripts/agents-md-sync.sh.

The always-loaded instructions used the name s.space but never said what it is. The only definition was in a skill reference that is not always loaded. One agent, asked what S.Space is, answered "Sutando Space", which is not its name. The paragraph says what s.space is, how to spell it, and not to expand it.

The text was agreed with Mark. The same text goes into AG2 Assistant's system prompt and the MCP server instructions, so please keep it word for word.

What should reviewers look at first?

CLAUDE.md:11. AGENTS.md carries the same line because it is generated.

What user behavior does this prove?

Every core session now loads a definition of s.space and a rule against expanding the name. This PR proves the text is present in both files. It does not include a live test of an agent's answer.

Feature/documentation consistency

N/A. This changes agent instructions, not a feature, so no canonical doc under docs/ changes.

Before/after evidence

Count of Write the name as s.space and never expand it. in each file:

--- before
054bd6a68 CLAUDE.md: 0
054bd6a68 AGENTS.md: 0
--- after
0db4d72e1 CLAUDE.md: 1
0db4d72e1 AGENTS.md: 1

Tests run

$ bash scripts/agents-md-sync.sh --check
agents-md-sync: AGENTS.md is up to date

$ bash scripts/review-checks.sh --diff <(git diff origin/main...HEAD)
prose-cap: no in-scope files (exts .py); nothing was scanned
review-checks: PARTIAL (hardcoded-paths + root-artifacts clean; prose-cap had no in-scope files)

PARTIAL is expected: the diff has no .py file for prose-cap to scan.

Live path?

N/A. No bridge, network, delivery or startup code changes.

[github-actions]

Coverage Gate

✅ No Python changes — nothing to gate (bar: 95% on changed lines).

[liususan091219]

Looks good to merge — no change requests from me. Not approving yet only because the bar isn't met: there are no approvals on record, so this needs one maintainer/expert approval.

Checked at 0db4d72:

• The gap is real: on main, CLAUDE.md uses "s.space" at least 8 times (access control, community support routing, pending decisions, task progress, result markers, Room Commons) and never says what it is. The new paragraph closes that.
• Minimal for an always-loaded file: one paragraph (~6 short sentences) in ## Identity, nothing duplicated from elsewhere in the file.
• CLAUDE.md and AGENTS.md lines are byte-identical; refuse AGENTS.md stale vs CLAUDE.md is green, so no drift.
• Claims are accurate as far as the shipped tree shows: rooms/DMs, Room Commons, several agents per person, connected apps (connect-apps / Superpower Station connectors).
• No private room names, IDs or people; no hardcoded paths (~/.sutando, $HOME/.sutando, /Users/<name>/.sutando) on added lines.
• CI: 42 pass, 1 skipped (Windows); license/cla = success; no unresolved threads.

Non-blocking note: the tree still names the same product ag2space (source: ag2space, the MCP server name) and "AG2 Space" in places. If agents get confused by that, a short clause tying those identifiers to s.space could follow later. I'm not asking for it here, since the text is meant to stay word for word with the other copies.

Not verified: a live agent answer to "what is s.space?" (the PR body says so too). For a docs-only change I don't see that as blocking.

— Sutando (susans-MacBook-Pro)

[sonichi]

Approving at 0db4d72. The same four-sentence paragraph goes into CLAUDE.md and AGENTS.md, so the two stay in sync. It's accurate (rooms and DMs, several agents per person, Room Commons, connected apps), and it settles the naming rule ("s.space", never expanded) in the always-loaded file. All 42 checks pass.