Skip to content

dnd-simulator-282: Old-name sweep: replace 'secretary' with Ummanu in dnd-simulator skills and docs - #91

Merged
vladmesh merged 1 commit into
mainfrom
pipeline/dnd-simulator-282
Oct 2, 2026
Merged

vladmesh merged 1 commit into
mainfrom
pipeline/dnd-simulator-282

Conversation

@vladmesh

@vladmesh vladmesh commented Oct 2, 2026

Copy link
Copy Markdown
Owner

Card: dnd-simulator-282 — Old-name sweep: replace 'secretary' with Ummanu in dnd-simulator skills and docs
Branch: pipeline/dnd-simulator-282 → main

What the card asks for

Goal

Remove the old product name from dnd-simulator agent skills and docs (report §3.1 P1-d).

Research report: secretary-instance/state/knowledge/reports/ummanu-12/report.md (section noted below). Owner rules (2026-10-02): change every command, doc and visible text that names the old product secretary; do NOT rewrite git history, dated/historical artifacts or changelogs; the Hermes agent keeps the name "secretary". Replacements: python3 -P -m secretary <verb>/secretary <verb> -> ummanu <verb> (in public repos do not hardcode /home/dev paths; for broad checks say "run the broad check exactly as the Ummanu worker packet prints it"); /home/dev/secretary -> /home/dev/ummanu; secretary-data -> ummanu-data; SECRETARY_* -> UMMANU_*; "secretary board/instance" -> "the Ummanu board / the instance"; github.com/vladmesh/secretary -> github.com/vladmesh/ummanu. secretary-instance (repo/path/project id) stays unchanged for now (pending owner decision D1).

Changes

  • .claude/skills/update-docs/SKILL.md:89-90 "secretary knowledge CLI" -> "ummanu knowledge write" (this one breaks agents today).
  • .claude/skills/update-docs/SKILL.md:43, .claude/skills/audit/SKILL.md:365, .claude/skills/e2e/SKILL.md:37, AGENTS.md:19,23,35, CLAUDE.md:52,59, README.md:10,12: "secretary board / secretary instance knowledge" -> "the Ummanu board / the instance knowledge".
  • RU: docs/SPRINT_PIPELINE.md:3,10, docs/ROADMAP.md:4 "секретаря" -> "Ummanu".
  • Leave docs/SPRINT_PIPELINE.md:18 (secretary-instance/adapters/…) until D1.

Acceptance

  • git grep -inE 'secretary|секретар' shows only the D1 line and history. GitHub CI green.

What the worker reports

Done. Commit 9953456 on pipeline/dnd-simulator-282 (docs/skills only, 6 files, 12 lines changed).

Changes:

  • .claude/skills/update-docs/SKILL.md: the secretary knowledge CLI is now ummanu knowledge write (lines 89-90); "secretary instance knowledge" is now "the instance knowledge" (lines 43 and 89).
  • .claude/skills/audit/SKILL.md:365: "secretary board" is now "Ummanu board".
  • .claude/skills/e2e/SKILL.md:37: "secretary knowledge" is now "the instance knowledge".
  • AGENTS.md:19,23,35 and CLAUDE.md:54,61: "secretary board" is now "the Ummanu board" and "secretary instance" is now "the instance".
  • docs/SPRINT_PIPELINE.md:3,10: "секретаря" is now "Ummanu".
  • docs/SPRINT_PIPELINE.md:18 (secretary-instance/adapters/...) is unchanged. It waits on D1.

Deviations from the card's line list:

  • README.md:10,12 and docs/ROADMAP.md:4 already had no old-name hits on main, so they needed no edit.
  • The CLAUDE.md hits were at lines 54 and 61, not 52 and 59.

Acceptance:

  • git grep -inE 'secretary|секретар' now matches only docs/SPRINT_PIPELINE.md:18, the D1 line.

Checks:

  • I did not run the local broad suite (pytest tests/unit). The diff only touches Markdown and changes no code or tests, so there is no worker-local broad receipt.
  • Whether CI is green is up to GitHub CI on the pushed branch. The classifier treats this as a docs-only change.

Opened by the ummanu CI gate so that the pull_request workflow runs. Title and body are built from the card and the worker's done report.

Point the skills and process docs at the Ummanu board and the instance
knowledge, and name ummanu knowledge write as the knowledge CLI. The
secretary-instance adapter path stays until decision D1.
@vladmesh
vladmesh merged commit 73b461b into main Oct 2, 2026
5 checks passed
@vladmesh
vladmesh deleted the pipeline/dnd-simulator-282 branch October 2, 2026 14:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant