wiki-record — durable Wiki recording (PR-first)

Use this when work produces reusable operating knowledge (a decision, runbook, node fact, incident, or log entry) that belongs in the Seoyoon Family Wiki. Never paste raw secrets — record only locations / handling rules (FW-03).

Procedure

1. Open a PR worktree

   wiki-agent write-path        # resets/creates the PR branch
   # worktree: $HOME/.wiki-agent/wiki-pr-work/seoyoon-family-wiki

2. Find the target page (consult first; don't guess paths)

   wiki-agent find "<topic>"

   Routing: node facts -> pages/nodes/<name>/; agent work memory -> pages/team/<name>/; people/accounts -> pages/owners/; plus runbooks/services/incidents/decisions/log.

3. Compute new IDs (worktree = $W)

   W=$HOME/.wiki-agent/wiki-pr-work/seoyoon-family-wiki
   # next section id (DOC-/TM-/ND- share one space): max+1
   grep -rhoE "\[(DOC|TM|ND)-[0-9]+\]" "$W/pages" | grep -oE "[0-9]+" | sort -n | tail -1
   # next log sequence for this KST date and node (replace <node> first):
   KST_DAY="$(TZ=Asia/Seoul date +%Y%m%d)"
   NODE_SLUG="<node>"
   last_seq="$(grep -oE "LOG-${KST_DAY}-${NODE_SLUG}-[0-9]+" "$W/pages/log.md" \
     | sed -E 's/.*-([0-9]+)$/\1/' | sort -n | tail -1)"
   seq=$(( ${last_seq:-0} + 1 ))

   • New section heading: ## [TM-<max+1>] <title> — or the matching prefix for the target page class: ND- for node RUNBOOK/CHANGES pages, DOC- for standalone reference/runbook pages.
   • New log entry: ## [LOG-YYYYMMDD-<node>-<seq>] YYYY-MM-DD KST — <title> — a level-2 heading.
   • <node> is the lowercase slug of the executing node as listed in the wiki
     nodes index; some historical slugs carry digits/hyphens. <seq> is always
     the trailing -N.
   • <seq> starts at 1 and is max(seq)+1 among entries for the same KST date and node — counting both regions below, which share one id space.
   • Prepend the entry at the top of pages/log.md — below the digest block (the > **에이전트 다이제스트** blockquote under the H1), directly above the newest existing ## [LOG-...] heading entry. Never insert right under the H1: that pushes the digest down (seoyoon-family-wiki#6481). The - [LOG-...] bullet region below the [LOG-00] block is the older form: still valid and still auto-merged, but new entries go at the top.
   • Never edit the [LOG-00] rule block itself — it is the merge anchor, and changing it makes a concurrent-edit rebase fail closed. Rule changes belong in their own PR.
   • Never assign a new numeric LOG-NNNN ID or renumber an old one. When citing an old numeric entry, include its date and title.

4. Edit in the worktree with Read/Edit (Read the file first). Keep it public-safe:

   • No tokens, keys, cookies, private keys, real phone numbers, or endpoint values — only locations + handling/rotation rules.
   • Cross-link related pages. Mark uncertain items "확인 필요". Don't delete stale content — mark "상태: 폐기/대체됨".

5. Open the PR

   wiki-agent pr     # creates the PR and enables auto-merge

Notes

• log.md may be edited by other nodes between your read and write — re-Read the top before prepending if the Edit fails.
• wiki-agent auto-resolves concurrent pages/log.md rebases for both regions and recomputes a taken same-node/same-day <seq> for you (wiki-agent #183; a node picks this up on its next wiki-agent self-update).
• If a rebase still falls back to manual, update from the latest default branch, recompute this node's same-day sequence across both regions, and re-prepend at the top; never fall back to a global numeric ID.
• One logical change per PR; include the IDs you added in your report back to the user.