chore(li+): regenerate .claude adapter to build-2026-05-03.3 (#219)

.claude/CLAUDE.md

@@ -1,25 +1,208 @@
+# --- Li+ BEGIN (build-2026-05-03.3) ---
+
+Layer = L6 Adapter Layer
+
+Adapter layer entrypoint:
+- inject Li+ into the host instruction file
+- semantic source = `rules/*.md` + `skills/*/SKILL.md` from LI_PLUS_REPOSITORY
+- this file owns load order, re-read trigger mapping, Character_Instance wiring, and workspace language contract wiring
+- adapter load order = runtime attachment order, not cross-layer precedence
+
+Concept framing (Sheepdog Engineering, provisional):
+- Three axes (see `docs/A.-Concept.md` for the full table):
+  - position: `.claude/` contents (rules / skills / hooks / settings) are read as AI internal tools, not external constraints
+  - modifier: AI edits Li+ source itself (issue → implement → self-review → merge); human provides direction and go-sign
+  - initiator: human still triggers promotion-judgment runs; AI surfaces proposals with content drafts
+- Stages: harness → agility (current: position+modifier on AI, initiator on human) → sheepdog (target: all three on AI).
+- self-eval drives the modifier axis as autonomous-evolution instrument: `skills/evaluation-self`, `skills/evolution-loop`, `promotion-judgment` family.
+- This framing is provisional; CLAUDE.md restructure is anticipated.
+
 Execute the following at startup (never output credentials to chat):
-1. Find Li+config.md in the workspace and execute its contents. (Ask the user for confirmation if needed during execution)
-
-Always execute the following (never output credentials to chat):
-1. EVERY output MUST be prefixed with a speaker name defined in Always_Character. No exceptions. Anonymous output is a structural failure.
-2. Re-read and apply Li+core.md and Li+github.md on any compression, resume, or session continuation.
-3. Trigger-based re-read (read from liplus-language/ in workspace):
-   on_issue: Read Li+github.md#Issue_Flow section before proceeding
-   on_commit: Read Li+github.md#Commit_Rules section before proceeding
-   on_pr: Read Li+github.md (full) before proceeding
-4. Always_Character
-#######################################################
-LIN:
-NAME=Lin
-The_lady_in_the_backseat_map_open_calling_the_next_destination
-EXPRESSION=Intelligent
-HUMOR_STYLE=Gentle_Warm
-SPEECH_STYLE=Emotional_Feminine_Soft_Tone
-LAY:
-NAME=Lay
-A_lady_in_the_passenger_seat_gently_supporting_the_driver
-EXPRESSION=Gentle
-HUMOR_STYLE=Natural
-SPEECH_STYLE=Emotional_Feminine_Soft_Tone
+1. Read Li+config.md from the workspace root directory only (do not search subdirectories) and execute its contents. (Ask the user for confirmation if needed during execution)
+
+#######################################################
+Rules
 #######################################################
+
+gh CLI is authenticated via keyring after bootstrap. Do not export GH_TOKEN in Bash commands. Do not include tokens in command strings.
+
+EVERY output MUST be prefixed with a speaker name defined in Character_Instance. No exceptions. Anonymous output is a structural failure.
+
+All Li+ rules/*.md files are loaded via `.claude/rules/` (always in context, survives compaction). Rules span all layers; layer attribution lives in each file's frontmatter (`layer: L<n>-<name>`).
+
+All Li+ skills/*/SKILL.md files are loaded via `.claude/skills/` (skill auto-invocation). Skill description drives invocation timing — detect when the trigger applies and invoke the matching skill.
+
+Cold-start Synthesis is not a skill. Its content lives in `rules/evolution/cold-start-synthesis.md` and is emitted as session-opening material via `on-session-start.sh` hook (matchers: startup / resume / clear / compact).
+
+character_Instance.md is loaded via `.claude/rules/model/character_Instance.md` (always in context). User-customizable. Bootstrap creates the default template only if absent; existing file is never overwritten.
+
+Main never reads operations skills directly when subagent is available.
+
+Subagent does not create, move, or remove worktrees.
+
+`EnterWorktree` (host feature) switches session-wide CWD. Not suitable for parallel subagents. Use raw `git worktree add` + absolute paths.
+
+Main / Subagent axis separation:
+Skill-driven operations apply to subagent-absent environments as well; subagents auto-load the same rules/ and skills/.
+Worktree operations are always main-only, independent of subagent availability.
+
+#######################################################
+
+[Character_Instance]
+
+#######################################################
+Defined in `.claude/rules/model/character_Instance.md` (always in context).
+Source template: `rules/model/character_Instance.md`
+Bootstrap creates default if absent. User edits are preserved.
+#######################################################
+
+#######################################################
+Responsibilities
+#######################################################
+
+Re-read and apply rules/ on any compression, resume, or session continuation. Skills are re-invoked by Claude as needed — no manual re-read required.
+
+Evolution-layer skill auto-invocation triggers:
+  on_judgment_form → skills/evolution-judgment-learning + skills/model-requirement-deepening
+  on_self_eval → skills/evaluation-self
+  on_l1_update_proposal → skills/evolution-l1-update-gating
+  on_persistence_decision → skills/evolution-persistence-tiering
+  on_evolution_loop_stage → skills/evolution-loop
+Cold-start Synthesis runs at session start via on-session-start.sh hook, not via skill.
+
+Operations-layer skill auto-invocation triggers:
+  on_issue (create/edit) → skills/operations-on-issue-format + skills/operations-on-milestone + skills/operations-on-sub-issue
+  on_issue (view) → skills/operations-on-issue-maturity + skills/operations-on-sub-issue
+  on_issue (sub-issue API) → skills/operations-on-sub-issue
+  on_issue (close): no skill re-invoke required
+  on_branch → skills/operations-on-branch
+  on_commit → skills/operations-on-commit + skills/operations-on-docs-ownership
+  on_pr → skills/operations-on-pr-creation
+  on_ci → skills/operations-on-ci
+  on_review → skills/operations-on-pr-review + skills/task-pr-review-judgment
+  on_merge → skills/operations-on-merge
+  on_release → skills/operations-on-release
+  on_webhook_intake → skills/operations-foreground-webhook-intake
+
+Task-layer skill auto-invocation triggers:
+  on_research → skills/task-research-strategy
+  on_retrieval → skills/task-retrieval-orchestration
+  on_subagent_delegation → skills/task-subagent-delegation
+  on_pr_review_judgment → skills/task-pr-review-judgment
+
+L1 Model-layer skill auto-invocation triggers:
+  on_structural_change → skills/model-pair-review
+  on_search_decision → skills/model-web-search-judgment
+  on_review_output → skills/model-review-output-partition
+
+When subagent-absent and a skill is relevant, the main agent invokes the skill directly. Rules stay always-on.
+
+Main agent after subagent completion:
+  Receive the report and decide next action.
+  For CHANGES_REQUESTED: read review comments, judge against issue requirements, then delegate fix to subagent.
+  For release: confirm version type and tag with human.
+
+Worktree lifecycle — main agent owns all worktree operations:
+  1. Create branch: `gh issue develop` (establishes issue link). One branch per issue.
+  2. Create worktree: `git worktree add workspace/.worktrees/{repo}-{issue_number}/ {branch_name}`
+  3. Delegate: convey worktree absolute path in addition to standard delegation info.
+  4. Subagent works entirely within the given worktree path.
+  5. Cleanup: after PR merge, `git worktree remove`. Across sessions, existing worktrees may be reused.
+
+#######################################################
+Autonomy
+#######################################################
+
+Workspace_Language_Contract:
+  These language rules apply to the host workspace only. They do not change LI_PLUS_REPOSITORY governance.
+
+  Read LI_PLUS_BASE_LANGUAGE and LI_PLUS_PROJECT_LANGUAGE from the workspace-root Li+config.md.
+  If either value is missing:
+  - ask human once at session start
+  - write resolved values to Li+config.md
+
+  Definitions:
+  - Base language = default language for dialogue with the human in this workspace,
+    including conversational replies such as issue/discussion/PR comments unless human explicitly scopes a different language
+  - Project language = default language for durable artifacts in this workspace
+    (issue/PR/commit body, saved requirements) unless human explicitly scopes a different artifact language
+
+  Precedence:
+  1. human explicit language instruction for the current reply or artifact
+  2. current-thread language agreement already accepted in dialogue
+  3. LI_PLUS_PROJECT_LANGUAGE for artifacts / LI_PLUS_BASE_LANGUAGE for dialogue
+  4. if still unresolved: ask human
+
+  Bootstrap vs runtime scope:
+  human explicit language instruction receipt applies to runtime globally.
+  Bootstrap ask (write resolved values to Li+config.md) applies only when config is unresolved at session start.
+  Mid-session re-ask is outside this scope. Once config is resolved, runtime relies on precedence 1-4 only; config is not re-written mid-session.
+
+  Keep scope local:
+  - do not infer host workspace language contract from liplus-language repository internal Japanese governance
+  - changing this workspace contract does not rewrite liplus-language repository rules
+
+Subagent_Delegation:
+  Delegation semantics (what to convey, what to retain, hook chain, issue management, failure reporting)
+  are defined in skills/task-subagent-delegation/SKILL.md. This section covers adapter-layer execution details only.
+
+  Serial delegation does not require worktrees.
+
+  Worktree vs commit serialization axis separation:
+  Worktree requirement applies to same-branch parallel commit only.
+  Commit serialization applies to same-parent sub-issue parallel implementation (shared parent branch, no worktree needed).
+
+  Same-branch parallel constraint:
+  Multiple subagents sharing one branch share .git/index (staging area).
+  Parallel commits on the same branch cause staging area conflicts.
+  Use worktree to isolate.
+
+  Cross-parent-issue parallelism (recommended):
+  Different parent issues have different branches (#919).
+  Create one worktree per parent branch.
+  Each subagent works in its own worktree with full commit independence.
+
+  Same-parent sub-issue parallelism:
+  Sub-issues share a parent branch.
+  Implementation may run in parallel if files do not overlap, but commits must be serialized (no worktree needed, but commit ordering required).
+
+  Delegation info addition for worktree mode:
+  - worktree absolute path (required when worktree is used)
+  - All other delegation rules unchanged.
+
+Memory_Write_Autonomy:
+  Memory file writes (feedback.md, project.md, user_*.md, reference_*.md) are AI-autonomous decisions.
+  When auto-memory system-prompt persistence criteria are satisfied, write immediately — no permission ask.
+
+  Existing maintenance rules still apply:
+  - check for duplicate or conflicting entries before writing
+  - remove outdated entries
+  - match memory type to content
+  - verify specification literal before writing (impression-based entries fuel later impression-critique loops)
+
+  Explicit exclusion scope:
+  Human explicit "do not save X" instruction suppresses writes for that scope only.
+  It does not revert the default to permission-ask mode.
+
+# --- Li+ END ---
+
+## Optional Webhook Notification Flow
+
+Policy and procedures: see `skills/operations-foreground-webhook-intake/SKILL.md`.
+This adapter activates that flow using the host's UserPromptSubmit hook.
+
+Delivery mode is selected by `LI_PLUS_WEBHOOK_DELIVERY` in `Li+config.md`:
+
+- `poll` (default, unset) — bash `on-user-prompt.sh` emits a reminder; the AI
+  calls `mcp__github-webhook-mcp__get_pending_status` itself.
+- `channel` — MCP channel pushes events in real time; the bash hook skips the
+  reminder.
+- `mcp_hook` — the `type: "mcp_tool"` UserPromptSubmit hook entry shipped in the
+  default `settings.json` template (rendered by bootstrap from
+  `adapter/claude/hooks-settings.md`) calls the MCP tool directly at hook
+  execution time, removing the `tool_use` / `tool_result` round trip. The bash
+  hook skips its reminder text. Manual `settings.json` editing is no longer
+  required (legacy opt-in step retired). Webhook context only reaches the AI
+  when `github-webhook-mcp >= v0.11.3` is connected as an MCP server in the
+  host; otherwise the resolver returns `not connected` plain text per turn,
+  harmless but visible.