v0.3.165 - Plain-Language Guidance Convention

v0.3.165 - Plain-Language Guidance Convention

v0.3.165 makes "explain it in everyday language" a normative convention for WOM
operator AIs, not a one-off reminder. WOM already had an
ai-response-concept-guide that translates WOM CONCEPT words for a human, but
nothing told an operator AI to translate git/infrastructure jargon ("fetched to
the mirror", "checkout", "pin", "manifest") when it reports version or
infrastructure state to a person. This release adds that convention to the
runtime-visible surfaces so every WOM operator AI applies it on the first try,
and adds a git/infra lookup layer to the concept guide so the plain phrasing is
one command away.

What ships

• A normative "Plain-Language for Humans" convention on five runtime surfaces.
  The personal/company/family AGENTS.md templates, the runtime
  templates/ai-runtime/wom-archive/SKILL.md, and the normative
  wom-kit/docs/wom-ai-runtime-skill-plugin-layer.md doc (plus one bullet in its
  Skill Template list) now carry the same short rule: when an AI operator
  addresses a HUMAN, it must translate git/infrastructure/WOM-internal jargon
  into everyday language, keeping the exact technical term in parentheses or in
  the logs only. Each surface keeps its own terse style. The canonical worked
  examples are shared across all five:

  the update files arrived but the update button hasn't been pressed yet (fetched, not checked out)
  a saved bookmark to a specific version (a pin)
  the list of which files exist and their fingerprints (the manifest)
  

• A git/infra terminology translation layer in ai-response-concept-guide.
  A new git_infra_terms topic and section emit ko-KR/en-US everyday phrasings
  for fetch, checkout, pin, manifest, hash, commit, tag, branch,
  HEAD, remote, mirror, clone, diff, staged, rebase, and stash.
  This is complementary to the existing WOM operational-term layer (edge types,
  lifecycle states, connection kinds): it covers git/infra words, not WOM concept
  words, so the two layers do not duplicate each other. The guide gains the
  capability flag git_infra_term_translation_available, the guide-contract flag
  translate_git_infra_jargon_for_humans, and a safe-routing lookup entry.
  Look it up with:

  archive ai-response-concept-guide <archive-root> --topic git_infra_terms --locale en-US --dry-run --format json

The boundary (what this is NOT)

• This governs human-facing prose only. Machine, JSON, and receipt output
  stays exact and unchanged.
• The convention is guidance an operator AI applies, enforced by the AI
  reading it — not a code check. WOM does not validate or enforce plain-language
  output, and nothing in this release claims that it does.
• The ai-response-concept-guide command still writes nothing, calls no
  providers, reads no source bytes, and echoes no local absolute paths, provider
  URLs, or secret values.

Upgrade

No archive migration is required. No hash change. The additions are guidance
prose and read-only concept-guide surfaces. See UPGRADE.md.