Hephaestus v0.7.29

• Self-healing updates for stale plugin caches. hephaestus update now
  recovers runtimes with no RELEASE marker and refreshes existing Claude Code
  and Codex plugin cache directories in addition to the neutral
  ~/.agentlas/runtime/current install.
• Non-interactive /hep-upload no longer stalls. After Cloud or Agentlas
  Hub has been chosen, hep-upload <agent-folder> --visibility private-link
  and --visibility marketplace run through the bundled publisher without
  requiring an interactive TTY.
• English README language cleanup. Removed Korean examples from the English
  README command table and changed the language selector label to English.
• Deterministic /hep-build team shape gate. Added
  scripts/verify-team-package.sh plus valid/degenerate fixtures so generated
  packages must be either one single-agent worker or a real team with
  orchestrator/HQ, topology, memory, policy, eval, QA, and one HQ command.
• Ownership-boundary single vs team classifier. Documented the 0-3 step
  classifier across canonical skills, modes, command adapters, and mode map so
  /hep-build no longer treats the word "team" as enough evidence by itself.
• Plain-language clarify questions. Builder interview and clarify surfaces
  now ask ordinary user-facing questions about whether one expert can do the
  job or several experts must split and merge it, while internal labels such as
  ownership boundary, memory/context, and produces/consumes stay hidden.
• Agentlas Cloud/Network personalization contract. Documented the remote
  Agentlas Web/MCP behavior where signed-in /hep-network searches Cloud,
  then bookmarks, then public Hub, while /hep-cloud remains Cloud-only.
• Workspace-scoped borrowed-agent memory. Added the implemented storage
  contract for Agentlas Web agent bindings, overlays, promoted memory items,
  promoted playbook cards, plugin locks, retrieval receipts, run events, and
  self-evolution proposals. Public Hub packages are not mutated by one
  workspace's personalization.
• Runtime bundle overlay boundary. Clarified that Cloud/Hub bundles may
  receive bounded workspace overlays and receipt ids, but raw prompts,
  transcripts, secrets, credential values, and private local files are not
  durable personalization records.