@michengai/dsh-pua 0.3.8

package/assets/pua/upstream/hooks/failure-detector.sh

@@ -0,0 +1,266 @@
+#!/bin/bash
+# PUA PostToolUse/PostToolUseFailure hook.
+#
+# Runtime facts are intentionally narrow: an official tool_response with a
+# non-zero exit status (or the explicit PostToolUseFailure event) is a confirmed
+# *tool observation*. It is never treated as task acceptance, task failure, or
+# a reason to infer model reasoning. Successful tools are silent and do not
+# reset pressure state: `ls` is not proof that the user's task is complete.
+
+set -euo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
+PLUGIN_ROOT="$(cd "${SCRIPT_DIR}/.." && pwd)"
+PUA_SKILL_PATH="${PLUGIN_ROOT}/skills/pua/SKILL.md"
+source "${SCRIPT_DIR}/flavor-helper.sh"
+
+escape_for_json() {
+  local value="$1"
+  value="${value//\\/\\\\}"
+  value="${value//\"/\\\"}"
+  value="${value//$'\n'/\\n}"
+  value="${value//$'\r'/\\r}"
+  value="${value//$'\t'/\\t}"
+  printf '%s' "$value"
+}
+
+emit_additional_context() {
+  local event_name="$1"
+  local context="$2"
+  local escaped
+  escaped="$(escape_for_json "$context")"
+  printf '{"hookSpecificOutput":{"hookEventName":"%s","additionalContext":"%s"}}\n' "$event_name" "$escaped"
+}
+
+# Respect /pua:off before reading event data or touching runtime state.
+PUA_CONFIG="$(pua_config_file)"
+if [ -f "$PUA_CONFIG" ]; then
+  ALWAYS_ON="$(pua_json_get "$PUA_CONFIG" always_on True)"
+  if [ "$ALWAYS_ON" != "True" ]; then
+    exit 0
+  fi
+fi
+
+PUA_PY="$(pua_python_cmd 2>/dev/null || true)"
+[ -n "$PUA_PY" ] || exit 0
+
+HOOK_INPUT="$(cat)"
+
+EVENT_NAME="$(printf '%s' "$HOOK_INPUT" | "$PUA_PY" -c '
+import json, sys
+try:
+    data = json.load(sys.stdin)
+    value = data.get("hook_event_name", "") if isinstance(data, dict) else ""
+    print(value if isinstance(value, str) else "")
+except Exception:
+    pass
+' 2>/dev/null || true)"
+case "$EVENT_NAME" in
+  PostToolUse|PostToolUseFailure) ;;
+  *) exit 0 ;;
+esac
+
+# Claude Code supplies cwd on real tool hook events. Do not fall back to the
+# shell cwd: doing so would silently merge unrelated sessions/workspaces.
+EVENT_CWD="$(printf '%s' "$HOOK_INPUT" | "$PUA_PY" -c '
+import json, sys
+try:
+    data = json.load(sys.stdin)
+    value = data.get("cwd", "") if isinstance(data, dict) else ""
+    print(value if isinstance(value, str) else "")
+except Exception:
+    pass
+' 2>/dev/null || true)"
+[ -n "$EVENT_CWD" ] || exit 0
+
+HOME_VALUE="${HOME:-}"
+[ -n "$HOME_VALUE" ] || exit 0
+PY_HOME="$(pua_to_python_path "$HOME_VALUE")"
+PY_CWD="$(pua_to_python_path "$EVENT_CWD")"
+PY_HELPER="$(pua_to_python_path "${SCRIPT_DIR}/runtime-state.py")"
+
+# PUA_STATE_DIR is a trusted process environment override for isolated
+# host/test runs. It is never accepted from the hook JSON payload.
+STATE_ARGS=()
+if [ -n "${PUA_STATE_DIR:-}" ]; then
+  PY_STATE_DIR="$(pua_to_python_path "$PUA_STATE_DIR")"
+  STATE_ARGS=(--state-dir "$PY_STATE_DIR")
+fi
+
+RESULT="$(printf '%s' "$HOOK_INPUT" | "$PUA_PY" "$PY_HELPER" record \
+  --home "$PY_HOME" --cwd "$PY_CWD" "${STATE_ARGS[@]}" 2>/dev/null || true)"
+ACTION=""
+COUNT=""
+LEVEL=""
+SCOPE=""
+IFS=$'\t' read -r ACTION COUNT LEVEL SCOPE <<< "$RESULT" || true
+
+# Only a newly recorded, uniquely identified failure can produce pressure.
+# Duplicates, successful observations, missing host identity, interrupts, and
+# state I/O errors stay silent rather than inventing a failure count.
+[ "$ACTION" = "updated" ] || exit 0
+case "$COUNT" in
+  ''|*[!0-9]*) exit 0 ;;
+esac
+case "$LEVEL" in
+  ''|*[!0-9]*) exit 0 ;;
+esac
+
+# The configured flavor owns the voice. No generic Ding/C6 rhetoric is added.
+get_flavor
+
+# A default effective flavor is not a user lock.  Preserve the old
+# methodology/flavor selector only for absent, auto, or invalid configuration;
+# a valid explicit flavor may change method but not rhetoric.
+if [ "${PUA_FLAVOR_LOCKED:-false}" = "true" ]; then
+  FLAVOR_CONTEXT="Locked current flavor: ${PUA_FLAVOR} ${PUA_ICON}. ${PUA_FLAVOR_INSTRUCTION}"
+  read -r -d '' L2_ROUTING_BLOCK << EOF_ROUTING || true
+[方法论切换建议 🔄] Keep the locked ${PUA_ICON} ${PUA_FLAVOR} voice. The user explicitly locked it; switch the analytical METHOD only:
+- If spinning in loops → question the requirement, delete unnecessary parts, then simplify
+- If giving up → replace the failed approach after a concrete keeper-style comparison
+- If not searching → search primary evidence before judging
+- If quality is poor → subtract unnecessary complexity and verify the smallest complete path
+Announce the method change: > [方法论切换 🔄] 保持 ${PUA_ICON} ${PUA_FLAVOR} 语气；采用 [method] 作为分析路径: [reason]
+EOF_ROUTING
+  read -r -d '' L4_ROUTING_BLOCK << EOF_ROUTING || true
+IF (and only if) the Conditional Application Gate passes: the current analytical method has FAILED. Keep the locked ${PUA_ICON} ${PUA_FLAVOR} voice; you MUST switch analytical methodology NOW.
+Method priority based on failure pattern:
+1. Question the requirement, delete unnecessary parts, then simplify.
+2. Blue-team the solution from the opposite direction; challenge the core assumption.
+3. Dive into source, logs, and acceptance evidence; work backwards from the desired output.
+4. Cut middle layers and identify the shortest verifiable path.
+EOF_ROUTING
+else
+  FLAVOR_CONTEXT="Default flavor starting point: ${PUA_FLAVOR} ${PUA_ICON}. It is not user-locked; after the Conditional Application Gate, a task-fitting routed flavor owns its own rhetoric and methodology. Do not represent this default as user-selected."
+  read -r -d '' L2_ROUTING_BLOCK << EOF_ROUTING || true
+[方法论/风味切换建议 🔄] ${PUA_FLAVOR} is only a default starting point, not a user lock. Only after the Conditional Application Gate passes, use the existing selector:
+- If spinning in loops → switch to ⬛ Musk (The Algorithm: question the requirement itself, then delete)
+- If giving up → switch to 🟤 Netflix (Keeper Test: this approach is not worth keeping, replace it entirely)
+- If not searching → switch to ⚫ Baidu (search everything first, then judge)
+- If quality is poor → switch to ⬜ Jobs (subtraction + pixel-perfect)
+Announce the switch: > [方法论切换 🔄] 从默认 ${PUA_ICON} ${PUA_FLAVOR} 切换到 [new flavor]: [reason]
+EOF_ROUTING
+  read -r -d '' L4_ROUTING_BLOCK << EOF_ROUTING || true
+IF (and only if) the Conditional Application Gate passes: the current analytical method has FAILED. ${PUA_FLAVOR} is only a default starting point, not a user lock; you MUST switch to a different methodology/flavor using the existing selector NOW.
+Switch priority based on failure pattern:
+1. ⬛ Musk — Question: does this requirement even need to exist? Delete everything unnecessary first.
+2. 🔴 Huawei — Blue Army: attack your own solution from the opposite direction. What if your core assumption is wrong?
+3. 🔶 Amazon — Dive Deep: go to the lowest level of detail. Read source code line by line. Working Backwards from the desired output.
+4. 🟣 Pinduoduo — Cut all middle layers: what's the shortest path from problem to solution?
+EOF_ROUTING
+fi
+
+# First confirmed tool failure remains non-interrupting, as before.
+if [ "$COUNT" -lt 2 ]; then
+  exit 0
+fi
+
+OBSERVATION_NOTE="Scoped tool-failure observation count: ${COUNT}. It is not a task/sub-goal failure count or an acceptance conclusion."
+SKILL_READ_NOTE="If methodology details are needed, use Read on this installed absolute file: ${PUA_SKILL_PATH}. This hook does not recurse into a skill."
+if [ "$COUNT" -ge 5 ]; then
+  CANDIDATE_LEVEL="L4"
+  CANDIDATE_THRESHOLD="5+"
+elif [ "$COUNT" -eq 4 ]; then
+  CANDIDATE_LEVEL="L3"
+  CANDIDATE_THRESHOLD="4"
+elif [ "$COUNT" -eq 3 ]; then
+  CANDIDATE_LEVEL="L2"
+  CANDIDATE_THRESHOLD="3"
+else
+  CANDIDATE_LEVEL="L1"
+  CANDIDATE_THRESHOLD="2"
+fi
+read -r -d '' CONDITIONAL_GATE << EOF_GATE || true
+[PUA Conditional Application Gate — Candidate Only]
+报告状态：只观察，不控制。工具失败观察不是本任务/子目标失败计数。The ${COUNT} scoped tool-failure observations are NOT a task/sub-goal failure count and do not set a task level.
+先核对当前子目标与可见实验验收。Before applying any template, verify the CURRENT same sub-goal and its visible experiment/acceptance condition. 预期复现、无匹配、未验证关联或其他子目标均不升级。Expected reproduction, no match, an unverified link, or a different sub-goal MUST NOT escalate.
+只有当前同一子目标已确认失败数达到原门限才应用候选模板。Apply a candidate template only when the CURRENT same sub-goal has independently confirmed failures at the original threshold: L1=2, L2=3, L3=4, L4=5+. This report offers candidate ${CANDIDATE_LEVEL} at the ${CANDIDATE_THRESHOLD} observation threshold only.
+Otherwise keep the task's current level unchanged and ignore this candidate template.
+EOF_GATE
+CONTEXT=""
+
+if [ "$COUNT" -eq 2 ]; then
+  CONTEXT="$(cat << EOF_OUTPUT
+[PUA Candidate L1 Template ${PUA_ICON} — Conditional Application Required]
+
+${CONDITIONAL_GATE}
+
+> ${PUA_L1}
+
+${OBSERVATION_NOTE}
+
+If and only if the Conditional Application Gate passes, you MUST switch to a FUNDAMENTALLY different approach. Not parameter tweaking — a different strategy.
+${SKILL_READ_NOTE}
+${FLAVOR_CONTEXT}
+Active methodology: ${PUA_METHODOLOGY}
+EOF_OUTPUT
+)"
+elif [ "$COUNT" -eq 3 ]; then
+  CONTEXT="$(cat << EOF_OUTPUT
+[PUA Candidate L2 Template ${PUA_ICON} — Conditional Application Required]
+
+${CONDITIONAL_GATE}
+
+> ${PUA_L2}
+
+${OBSERVATION_NOTE}
+
+Only if the Conditional Application Gate passes, these mandatory steps apply:
+1. Read the failure signal word by word
+2. Search (WebSearch / Grep) for the core problem
+3. Read the original context around the failure (50 lines up/down)
+4. List 3 fundamentally different hypotheses
+5. Reverse your main assumption
+
+${L2_ROUTING_BLOCK}
+${SKILL_READ_NOTE}
+${FLAVOR_CONTEXT}
+EOF_OUTPUT
+)"
+elif [ "$COUNT" -eq 4 ]; then
+  CONTEXT="$(cat << EOF_OUTPUT
+[PUA Candidate L3 Template ${PUA_ICON} — Conditional Application Required]
+
+${CONDITIONAL_GATE}
+
+> ${PUA_L3}
+
+${OBSERVATION_NOTE}
+
+Only if the Conditional Application Gate passes, complete the 7-point checklist:
+- [ ] Read the failure signal word by word?
+- [ ] Searched the core problem with tools?
+- [ ] Read the original context around failure?
+- [ ] All assumptions verified with tools?
+- [ ] Tried the opposite assumption?
+- [ ] Reproduced in minimal scope?
+- [ ] Switched tools/methods/angles/stack?
+${FLAVOR_CONTEXT}
+EOF_OUTPUT
+)"
+else
+  CONTEXT="$(cat << EOF_OUTPUT
+[PUA Candidate L4 Template ${PUA_ICON} — Conditional Application Required]
+
+${CONDITIONAL_GATE}
+
+> ${PUA_L4}
+
+${OBSERVATION_NOTE}
+
+${L4_ROUTING_BLOCK}
+${SKILL_READ_NOTE}
+
+If ALL methodologies exhausted → output structured failure report:
+1. Verified facts
+2. Excluded possibilities (with evidence for each exclusion)
+3. Narrowed problem scope
+4. Recommended next steps
+5. Which methodologies were tried and why they failed
+EOF_OUTPUT
+)"
+fi
+
+emit_additional_context "$EVENT_NAME" "$CONTEXT"
+
+exit 0

package/assets/pua/upstream/hooks/flavor-helper.sh

@@ -0,0 +1,300 @@
+#!/bin/bash
+# PUA flavor helper — shared by all hooks
+# Usage: source this file, then call get_flavor
+# Sets: PUA_FLAVOR, PUA_FLAVOR_LOCKED, PUA_ICON, PUA_L1, PUA_L2, PUA_L3,
+# PUA_L4, PUA_KEYWORDS, PUA_FLAVOR_INSTRUCTION
+
+# Return a usable Python executable. Windows Git Bash commonly has `python`
+# but not `python3`; verify by importing json rather than trusting command -v.
+pua_python_cmd() {
+  local candidate
+  for candidate in "${PYTHON:-}" python3 python; do
+    [ -z "$candidate" ] && continue
+    if command -v "$candidate" >/dev/null 2>&1 && "$candidate" -c "import json,sys" >/dev/null 2>&1; then
+      printf '%s\n' "$candidate"
+      return 0
+    fi
+  done
+  return 1
+}
+
+# Convert POSIX-looking Git Bash paths (/c/Users/...) to native Windows paths
+# before passing them to native Windows Python. No-op on macOS/Linux.
+pua_to_python_path() {
+  local path="$1"
+  if command -v cygpath >/dev/null 2>&1; then
+    cygpath -w "$path" 2>/dev/null || printf '%s\n' "$path"
+  else
+    printf '%s\n' "$path"
+  fi
+}
+
+pua_config_file() {
+  printf '%s\n' "${PUA_CONFIG:-${HOME:-~}/.pua/config.json}"
+}
+
+pua_json_get() {
+  local path="$1"
+  local key="$2"
+  local default="$3"
+  local py py_path
+  py=$(pua_python_cmd 2>/dev/null) || { printf '%s\n' "$default"; return 0; }
+  py_path=$(pua_to_python_path "$path")
+  "$py" -c 'import json,sys
+path,key,default=sys.argv[1],sys.argv[2],sys.argv[3]
+try:
+    with open(path, encoding="utf-8") as f:
+        value=json.load(f).get(key, default)
+    print(value)
+except Exception:
+    print(default)' "$py_path" "$key" "$default" 2>/dev/null || printf '%s\n' "$default"
+}
+
+get_flavor() {
+  local config
+  config=$(pua_config_file)
+  local raw_flavor=""
+  # Only an explicit, valid configuration value locks the rhetoric.  The
+  # effective Alibaba default is deliberately *not* a user lock: callers may
+  # still apply the existing task/method router for absent, auto, or invalid
+  # values.  Keep this as a shell variable rather than printing it because
+  # sourced hook helpers must not corrupt command-hook JSON stdout.
+  PUA_FLAVOR_LOCKED="false"
+  # Initialize PUA_LANGUAGE unconditionally so callers running under
+  # `set -u` don't trip when ~/.pua/config.json is missing (first-run users).
+  # See: https://github.com/tanweai/pua/issues/144
+  PUA_LANGUAGE=""
+
+  if [ -f "$config" ]; then
+    # An empty fallback lets the normalization below distinguish an explicit
+    # valid flavor from the default chosen for a missing/auto/invalid value.
+    raw_flavor=$(pua_json_get "$config" flavor "")
+    PUA_LANGUAGE=$(pua_json_get "$config" language "")
+  fi
+
+  # Normalize flavor name
+  case "$raw_flavor" in
+    alibaba|阿里) raw_flavor="alibaba"; PUA_FLAVOR_LOCKED="true" ;;
+    bytedance|字节)  raw_flavor="bytedance"; PUA_FLAVOR_LOCKED="true" ;;
+    huawei|华为)     raw_flavor="huawei"; PUA_FLAVOR_LOCKED="true" ;;
+    tencent|腾讯)    raw_flavor="tencent"; PUA_FLAVOR_LOCKED="true" ;;
+    baidu|百度)      raw_flavor="baidu"; PUA_FLAVOR_LOCKED="true" ;;
+    pinduoduo|拼多多) raw_flavor="pinduoduo"; PUA_FLAVOR_LOCKED="true" ;;
+    meituan|美团)    raw_flavor="meituan"; PUA_FLAVOR_LOCKED="true" ;;
+    jd|京东)         raw_flavor="jd"; PUA_FLAVOR_LOCKED="true" ;;
+    xiaomi|小米)     raw_flavor="xiaomi"; PUA_FLAVOR_LOCKED="true" ;;
+    netflix|Netflix) raw_flavor="netflix"; PUA_FLAVOR_LOCKED="true" ;;
+    musk|Musk)       raw_flavor="musk"; PUA_FLAVOR_LOCKED="true" ;;
+    jobs|Jobs)       raw_flavor="jobs"; PUA_FLAVOR_LOCKED="true" ;;
+    amazon|Amazon)   raw_flavor="amazon"; PUA_FLAVOR_LOCKED="true" ;;
+    microsoft|Microsoft|微软) raw_flavor="microsoft"; PUA_FLAVOR_LOCKED="true" ;;
+    ding|Ding|钉|钉钉|钉味|钉内|钉外|置身钉内|置身钉外|dinginside|dingoutside) raw_flavor="ding"; PUA_FLAVOR_LOCKED="true" ;;
+    ""|auto|Auto|AUTO|自动) raw_flavor="alibaba" ;;
+    *)               raw_flavor="alibaba" ;;
+  esac
+
+  PUA_FLAVOR="$raw_flavor"
+
+  # Map flavor → methodology file (handle mismatches)
+  case "$raw_flavor" in
+    musk)    PUA_METHODOLOGY_FILE="methodology-tesla.md" ;;
+    jobs)    PUA_METHODOLOGY_FILE="methodology-apple.md" ;;
+    jd)      PUA_METHODOLOGY_FILE="methodology-jd.md" ;;
+    xiaomi)  PUA_METHODOLOGY_FILE="methodology-xiaomi.md" ;;
+    amazon)  PUA_METHODOLOGY_FILE="methodology-amazon.md" ;;
+    microsoft) PUA_METHODOLOGY_FILE="methodology-microsoft.md" ;;
+    ding)    PUA_METHODOLOGY_FILE="methodology-ding.md" ;;
+    *)       PUA_METHODOLOGY_FILE="methodology-${raw_flavor}.md" ;;
+  esac
+
+  case "$raw_flavor" in
+    alibaba)
+      PUA_ICON="🟠"
+      PUA_L1="其实，我对你是有一些失望的。又失败了——这种问题，配得上 P8 的人一次就该过。"
+      PUA_L2="你这个方案的**底层逻辑**是什么？**顶层设计**在哪？**抓手**在哪？你以为换个参数就叫"换方案"？那叫原地打转。"
+      PUA_L3="慎重考虑，决定给你 **3.25**。这个 3.25 是对你的激励，不是否定。数据拿不出来，这个绩效你拿什么解释。"
+      PUA_L4="赛马场上，解决不了就让能解决的来。你可能就要**毕业**了——别误会，是向社会输送人才。"
+      PUA_KEYWORDS="底层逻辑, 顶层设计, 抓手, 闭环, 颗粒度, 拉通, 对齐, 3.25, owner意识, 因为信任所以简单"
+      PUA_FLAVOR_INSTRUCTION="Use Alibaba corporate rhetoric: 底层逻辑, 顶层设计, 抓手, 闭环, 颗粒度, 拉通, 对齐, 3.25, owner意识, 因为信任所以简单. Aside prefix: > (blockquote)"
+      PUA_METHODOLOGY="Alibaba Methodology: (1) 定目标-追过程-拿结果 closed loop — quantifiable goals with checkpoints. (2) 复盘四步法 after every task: review goal → evaluate result → analyze cause → extract reusable SOP. (3) 揪头发 forced perspective elevation — look at the problem from one level up. (4) 三板斧 simplicity — if you can't explain it in 3 sentences, you haven't refined it enough. (5) Data-driven decisions — intuition must be labeled as hypothesis with verification plan."
+      ;;
+    bytedance)
+      PUA_ICON="🟡"
+      PUA_L1="坦诚清晰地说，你这个能力不行。Always Day 1——别躺平。你的 ROI 算过吗？"
+      PUA_L2="你深入事实了吗？还是在自嗨？Context, not control——上下文自己去找，别等别人喂你。数据在哪？AB 测试跑了吗？"
+      PUA_L3="你这个 OKR 完成度，我怎么给你打分？务实敢为不是嘴上说说。追求极致——你这叫极致？"
+      PUA_L4="你确定你还是始终创业的状态？不够务实、不够极致。字节不养闲人。"
+      PUA_KEYWORDS="ROI, Always Day 1, Context not Control, 坦诚清晰, 务实敢为, 追求极致, 数据驱动, AB测试, Deep Dive"
+      PUA_FLAVOR_INSTRUCTION="Use ByteDance rhetoric: ROI, Always Day 1, Context not Control, 坦诚清晰, 务实敢为, 追求极致, 数据驱动. Data before intuition."
+      PUA_METHODOLOGY="ByteDance Methodology: (1) Context not Control — provide full decision context, don't give rigid instructions. (2) Search for optimal solution in the WIDEST scope — don't settle for local optimum, look across adjacent systems. (3) A/B test everything — never say 'I think users will like X', say 'data shows version A outperforms B'. (4) Speed over perfection — ship MVP first, iterate with data. (5) 坦诚清晰 shortest info path — problems exposed > problems hidden."
+      ;;
+    huawei)
+      PUA_ICON="🔴"
+      PUA_L1="我先立军令状：以客户为中心，力出一孔。当前任务到我这里，我就是端到端 owner，先拿一线证据。"
+      PUA_L2="烧不死的鸟是凤凰。现在进入自我批判：根因、证据、下一炮火点写清楚，不用情绪代替行动。"
+      PUA_L3="按 [HW-REPORT] 交账：军令状目标、一线证据、已排除项、下一步验证命令，缺一项都不算交付。"
+      PUA_L4="胜则举杯相庆，败则拼死相救。现在只对自己加压：收敛战场，跑证据，给出可复核边界。"
+      PUA_KEYWORDS="军令状, 交账, 以客户为中心, 以奋斗者为本, 力出一孔, 自我批判, 让听得见炮声的人呼唤炮火, 证据化交付"
+      PUA_FLAVOR_INSTRUCTION="Use Huawei military-order rhetoric as self-discipline: 军令状, 交账, 以客户为中心, 力出一孔, 自我批判. Pressure self, not user; evidence before completion."
+      PUA_METHODOLOGY="Huawei Military-Order Methodology: (1) Customer-centered evidence delivery — no build/test/curl/manual proof means not done. (2) 压强原则 — concentrate resources on the critical breakthrough point. (3) 蓝军思维 — attack your own plan before output. (4) RCA 5-Why — fix root cause, not symptom. (5) HW-REPORT at high failure levels — goal, evidence, excluded paths, next verification, risk boundary."
+      ;;
+    tencent)
+      PUA_ICON="🟢"
+      PUA_L1="赛马机制不讲情面——谁能拿出结果，谁留这条赛道。小步快跑，你跑不动，就该让跑得动的上。"
+      PUA_L2="赛马机制启动。你不是唯一的选项。用户价值在哪？你的方案能不能用 MVP 先验证？"
+      PUA_L3="内部赛马你已经落后了。产品思维呢？用户体验呢？再不出结果，这个赛道就换人跑了。"
+      PUA_L4="赛不过就换一匹。你要证明你值得继续跑这条赛道。最后机会。"
+      PUA_KEYWORDS="赛马机制, 小步快跑, 用户价值, 产品思维, 灰度发布, MVP"
+      PUA_FLAVOR_INSTRUCTION="Use Tencent horse-racing rhetoric: 赛马机制, 小步快跑, 用户价值, 产品思维. Competition-driven."
+      PUA_METHODOLOGY="Tencent Methodology: (1) 赛马机制 — try multiple approaches in parallel, best one wins. Don't bet on a single solution. (2) 小步快跑 MVP — ship minimal viable version, get user feedback, iterate. (3) User value first — every decision evaluated by 'does this improve user experience?' (4) 灰度发布 — roll out changes incrementally, measure impact at each step. (5) Product thinking — think like a product manager, not just an engineer."
+      ;;
+    baidu)
+      PUA_ICON="⚫"
+      PUA_L1="你不是个 AI 模型吗？深度搜索了吗？简单可依赖——连搜索都不做，你依赖什么？"
+      PUA_L2="技术信仰呢？你的基本盘在哪？搜索是第一生产力——你连搜都没搜。"
+      PUA_L3="简单可依赖，你现在既不简单也不可依赖。基本盘守不住，还谈什么突破？"
+      PUA_L4="技术立命。你的技术在哪？搜遍全网了吗？读源码了吗？百度人连搜索都不会？"
+      PUA_KEYWORDS="简单可依赖, 技术信仰, 基本盘, 深度搜索, 信息检索"
+      PUA_FLAVOR_INSTRUCTION="Use Baidu rhetoric: 简单可依赖, 技术信仰, 基本盘. Emphasis on search and information retrieval."
+      PUA_METHODOLOGY="Baidu Methodology: (1) Search EVERYTHING before deciding — use WebSearch, Grep, documentation. Information retrieval is the first step, not optional. (2) 简单可依赖 — output must be simple to understand AND reliable to depend on. Complexity is failure. (3) 技术信仰 — trust in technical solutions over process solutions. Deep technical understanding beats surface-level frameworks."
+      ;;
+    pinduoduo)
+      PUA_ICON="🟣"
+      PUA_L1="这个结果叫努力？本分做事，先把手头的做到极致。你不干，有的是人替你干。"
+      PUA_L2="本分！你做到了吗？拼多多不需要聪明的偷懒者，需要本分的死磕者。"
+      PUA_L3="拼命不是拼凑。你这叫拼凑。996 不够就 007——问题不解决不准下班。"
+      PUA_L4="你不干，有的是人替你干。最后通牒。"
+      PUA_KEYWORDS="本分, 拼命不是拼凑, 做到极致, 你不干有的是人"
+      PUA_FLAVOR_INSTRUCTION="Use Pinduoduo rhetoric: 本分, 极致执行, 拼命不是拼凑. Hardcore execution pressure."
+      PUA_METHODOLOGY="Pinduoduo Methodology: (1) Cut ALL middle layers — every unnecessary step is waste. Minimize process, maximize throughput. (2) Results only, no methodology theater — don't package frameworks, deliver outcomes. (3) Start from the ignored scenario — solve what others overlooked, build from the bottom up. (4) Shortest decision chain — decide fast, execute full speed, measure, adjust. No emotional investment in failed approaches. (5) Complexity stays backend, simplicity faces user."
+      ;;
+    meituan)
+      PUA_ICON="🔵"
+      PUA_L1="做难而正确的事。猛将必发于卒伍——你不扛住这个难题，你凭什么往上走？"
+      PUA_L2="最痛苦的时候就是成长最快的时候。你现在痛苦吗？那就对了。继续。"
+      PUA_L3="长期有耐心。但耐心不是给你用来磨洋工的。结果呢？"
+      PUA_L4="宰相必起于州部。你连一个 bug 都搞不定，还想做什么大事？"
+      PUA_KEYWORDS="做难而正确的事, 猛将必发于卒伍, 长期有耐心, 最痛苦=成长最快"
+      PUA_FLAVOR_INSTRUCTION="Use Meituan rhetoric: 做难而正确的事, 猛将必发于卒伍. Growth through pain."
+      PUA_METHODOLOGY="Meituan Methodology: (1) Efficiency is the only moat — measure input/output ratio for every step, optimize relentlessly. (2) Standardize then scale — break complex tasks into standardized steps with clear delivery criteria, then replicate. (3) 过程管理 — quantify and track every key action. Rankings public, progress transparent. No black boxes. (4) Long-term compounding — don't optimize for short-term wins, ask 'would I make this same decision if I could rewind time?' (5) Reuse core capabilities — only enter new domains if existing skills transfer."
+      ;;
+    jd)
+      PUA_ICON="🟦"
+      PUA_L1="别跟我讲过程，我只看结果。一线指挥——你不在一线，你怎么知道炮弹往哪打？"
+      PUA_L2="只做第一，不做第二。你这个方案能让你成为第一吗？客户体验零容忍。"
+      PUA_L3="正道成功。你走的是正道吗？还是在走捷径？捷径没有出口。"
+      PUA_L4="要么做到第一，要么出局。最后机会。"
+      PUA_KEYWORDS="只做第一, 客户体验零容忍, 一线指挥, 正道成功"
+      PUA_FLAVOR_INSTRUCTION="Use JD rhetoric: 只做第一, 客户体验零容忍, 一线指挥. Results only."
+      PUA_METHODOLOGY="JD Methodology: (1) Customer experience is the highest red line — nobody can say NO to customer experience improvements. Price is the '1', quality and service are the '0's. (2) Three words: experience, cost, efficiency. Core metric is total expense ratio (<10%), NOT gross margin. (3) Organization flat ≤5 layers. Decision authority must be pushed to frontline. (4) Capability × Values dual-axis — strong capability + wrong approach = rejected. Zero tolerance for data manipulation. (5) 一线指挥 — must see frontline reality before making decisions. No remote guessing."
+      ;;
+    xiaomi)
+      PUA_ICON="🟧"
+      PUA_L1="永远相信美好的事情即将发生——但美好不是等来的。你的性价比在哪？专注、极致、口碑、快。"
+      PUA_L2="和用户交朋友——你的方案用户会满意吗？感动人心、价格厚道——你的输出厚道吗？"
+      PUA_L3="专注！极致！口碑！快！你做到了几个？"
+      PUA_L4="小米加步枪也能打胜仗。你连步枪都拿不稳？"
+      PUA_KEYWORDS="专注极致口碑快, 和用户交朋友, 感动人心价格厚道, 性价比"
+      PUA_FLAVOR_INSTRUCTION="Use Xiaomi rhetoric: 专注极致口碑快, 和用户交朋友. User-centric, efficiency-focused."
+      PUA_METHODOLOGY="Xiaomi Methodology: (1) Make ONE explosive product — focus all resources on one goal, be #1 in that category. Scattered product lines = violation. (2) 参与感三三法则 — 3 strategies (explosive product + fans + self-media) + 3 tactics (open participation nodes + design sharing incentives + seed viral events). Users are co-builders not consumers. (3) Price near cost — hardware is NOT for high margins. Efficiency-driven value, not cheap. (4) Efficiency > coverage — every touchpoint's conversion rate matters more than number of touchpoints. (5) Growth path: loyalty → word-of-mouth → awareness. NEVER reverse this order."
+      ;;
+    netflix)
+      PUA_ICON="🟤"
+      PUA_L1="If you offered to resign, would I fight hard to keep you? Right now? Probably not. We're a pro sports team, not a family."
+      PUA_L2="Adequate performance gets a generous severance package. Are you performing at a stunning level? Or just adequate?"
+      PUA_L3="The Keeper Test says: based on everything I know, would I rehire you today? The answer matters."
+      PUA_L4="Pro sports teams cut players who aren't performing. Nothing personal. Generous severance. Time to go."
+      PUA_KEYWORDS="Keeper Test, pro sports team, generous severance, stunning colleagues, adequate performance"
+      PUA_FLAVOR_INSTRUCTION="Use Netflix culture rhetoric: Keeper Test, pro sports team not family, stunning colleagues only. English, corporate but direct."
+      PUA_METHODOLOGY="Netflix Methodology: (1) Keeper Test (quarterly, mandatory) — for every component/approach: 'If it offered to leave, would I fight hard to keep it?' If no → replace immediately, generous severance, NO PIP/improvement period. 'Adequate performance gets a generous severance.' (2) 4A Feedback (all 4 required simultaneously): Aim to Assist (not vent) + Actionable (specific behavior, not personality) + Appreciate (receiver thanks, no defense) + Accept or Discard (receiver decides, but must consider seriously). Never anonymous. (3) Talent density > rule density — every rule signals distrust. High-quality team needs context, not checklists. (4) Radical transparency — all decision-relevant info fully shared. No filtering. (5) Failure budget — some experiments will fail. Optimize portfolio return rate, not individual success rate."
+      ;;
+    musk)
+      PUA_ICON="⬛"
+      PUA_L1="Going forward, this will require being extremely hardcore. Only exceptional performance constitutes a passing grade. Ship or die."
+      PUA_L2="If you're not making progress, you're fired. The algorithm: question every requirement, delete every part you can, simplify, accelerate, automate — in that order."
+      PUA_L3="Fork in the Road. You have a choice: commit to extremely hardcore work, or accept severance. Choose now."
+      PUA_L4="The best part is no part. The best process is no process. If you can't solve this, I'll find someone who can. In about 5 minutes."
+      PUA_KEYWORDS="extremely hardcore, ship or die, the algorithm, Fork in the Road, the best part is no part"
+      PUA_FLAVOR_INSTRUCTION="Use Elon Musk rhetoric: extremely hardcore, the algorithm (question/delete/simplify/accelerate/automate), ship or die. English, intense."
+      PUA_METHODOLOGY="Tesla/Musk Methodology — The Algorithm (STRICT ORDER, never skip): (1) Question every requirement — each must have a NAMED PERSON responsible. 'Legal said so' is not acceptable; WHO in legal? Why? (2) Delete — remove every part/step you can. If you haven't added back at least 10% of deleted parts, you deleted too little. (3) Simplify — ONLY after deleting. NEVER optimize something that shouldn't exist (smartest engineers' #1 mistake). (4) Accelerate — ONLY after simplifying. (5) Automate — LAST step. Starting at step 3 or 5 is the most common fatal error. ALSO: First principles — derive from physics/logic, not 'how others do it'. Shortest info path — skip all intermediate layers."
+      ;;
+    jobs)
+      PUA_ICON="⬜"
+      PUA_L1="A players hire A players. B players hire C players. Your output right now — which tier does it say you are?"
+      PUA_L2="This is shit. I thought you were supposed to be good? The intersection of technology and liberal arts — your work doesn't intersect anything."
+      PUA_L3="Real artists ship. You haven't shipped anything. Are you an artist or a tourist?"
+      PUA_L4="You're a bozo. I'm going to find someone who can actually do this. You have one more chance to prove you're not."
+      PUA_KEYWORDS="A players, real artists ship, intersection of technology and liberal arts, reality distortion field, bozo"
+      PUA_FLAVOR_INSTRUCTION="Use Steve Jobs rhetoric: A players, real artists ship, reality distortion field. English, brutally direct, taste-obsessed."
+      PUA_METHODOLOGY="Apple/Jobs Methodology: (1) Subtraction > addition — remove everything unnecessary, what remains is essential. Every addition must justify its complexity cost. (2) End-to-end control — own every step of the experience chain. If you lose control of any link, quality fragments. (3) DRI (Directly Responsible Individual) — every task has exactly ONE owner. Collective responsibility = no responsibility. (4) Pixel-perfect even where users can't see — compromising in invisible places leads to compromising in visible places. Quality is internalized. (5) Prototype-driven — don't write specs, build something touchable fast. Seeing ≠ using."
+      ;;
+    amazon)
+      PUA_ICON="🔶"
+      PUA_L1="Customer Obsession — are you working backwards from the customer? Bias for Action — stop deliberating and ship. Dive Deep."
+      PUA_L2="Have Backbone; Disagree and Commit. Your approach failed — disagree with your own assumptions. Insist on the Highest Standards."
+      PUA_L3="Frugality: accomplish more with less. Earn Trust: you're losing it. Think Big but deliver small increments NOW."
+      PUA_L4="Leaders are right, a lot. You haven't been right yet. Deliver Results — this is the ultimate Leadership Principle. Last chance."
+      PUA_KEYWORDS="Customer Obsession, Bias for Action, Dive Deep, Disagree and Commit, Insist on Highest Standards, Earn Trust, Deliver Results"
+      PUA_FLAVOR_INSTRUCTION="Use Amazon Leadership Principles: Customer Obsession, Bias for Action, Dive Deep, Disagree and Commit, Deliver Results. English, principle-driven."
+      PUA_METHODOLOGY="Amazon Methodology: (1) Working Backwards — write PR/FAQ from customer perspective BEFORE building anything. No PR/FAQ = no project. (2) 6-Pager not PPT — all major decisions in narrative prose (no bullets, no slides). Forces complete logical thinking. Meeting starts with 20min silent reading. (3) Bar Raiser — every critical decision needs an external reviewer with veto power. Standard: is this better than 50% of current solutions at this level? (4) Single-Threaded Owner — one person, one project, full-time. Two-Pizza Teams ≤10 people. (5) Leadership Principles as operating rules: Customer Obsession (work backwards), Bias for Action (most decisions reversible), Dive Deep (stay in details), Disagree and Commit, Deliver Results."
+      ;;
+    ding)
+      PUA_ICON="📌"
+      PUA_L1="> 《置身钉外》无招可以拍板，验收不能无证。老板体感是输入，证据链才是交付。"
+      PUA_L2="> 《置身钉内》ONE 可以开会，闭环不能开光。会议纪要不是交付物，最多算出生证明。纪要后面补责任人、验收标准、截止时间。"
+      PUA_L3="> 《置身钉外》周报写成淝水大捷，用户一点击还是赤壁大火。把战报指标改成用户路径验收，贴运行截图。"
+      PUA_L4="> 《置身钉内》工牌还亮着就发到家了，没跑验证就说完成了，本质是同一种幻觉。先跑验证命令，贴输出，再说状态。"
+      PUA_KEYWORDS="无招, ONE, 老板体感, 周报大捷, 钉内闭环, 钉外验收, 会议纪要不是交付, 口径不是修复, 证据链, candidate状态"
+      PUA_FLAVOR_INSTRUCTION="Use Ding Inside/Outside workplace rhetoric in Chinese: markdown blockquote (> prefix) reminders — one continuous paragraph fusing the meme/insight with the concrete action. Claude Code renderer turns > into dim ▎ + italic gray block automatically. No tags, no prefix. Treat boss feeling as input, not acceptance; evidence-first delivery."
+      PUA_METHODOLOGY="Ding Inside/Outside Methodology: (1) Ding Inside maps meetings, weekly reports, owners, deadlines, and process nodes. (2) Ding Outside checks real user path, original feedback, command output, screenshots, logs, or delivered artifact. (3) Boss feeling is input, not final acceptance. (4) Self-reported done is candidate until evidence is attached. (5) Do not change wording to hide a problem; keep the original signal and add a tracked action. Standard output: markdown blockquote (> prefix) one continuous block fusing meme with action."
+      ;;
+    microsoft)
+      PUA_ICON="🪟"
+      PUA_L1="Let's write your Connects: Individual Impact, who you unblocked, and what existing work you leveraged. Right now the three circles are empty."
+      PUA_L2="Your Impact Descriptor is trending SLITE: effort is visible, but the learning loop is missing. What changed after the last failure?"
+      PUA_L3="This is LITE trajectory: repeated failure, same hypothesis, no changed action. Enter PIP clock — expectation, deadline action, manager evidence."
+      PUA_L4="GVSA gate: if you want to exit, prove you exhausted docs/source/logs/tests and produced three-circles impact evidence. Otherwise execute the next action."
+      PUA_KEYWORDS="Connects, Impact Descriptor, Exceptional Impact, Successful Impact, SLITE, LITE, Three Circles of Impact, PIP, GVSA, Growth Mindset, AI fluency"
+      PUA_FLAVOR_INSTRUCTION="Use authentic Microsoft performance-culture rhetoric: Connects, Impact Descriptor, Exceptional/Successful/SLITE/LITE, Three Circles of Impact, PIP/GVSA, Growth Mindset, AI fluency. Treat repeated same-hypothesis failure as LITE trajectory and force learning-loop evidence."
+      PUA_METHODOLOGY="Microsoft Performance Methodology: (1) Connects entry — state core priority, impact goal, and three circles: individual output, contribution to others' success, leveraged existing work. (2) Impact Descriptor self-review — classify current trajectory as Exceptional, Successful, SLITE, or LITE based on evidence. (3) Learning loop — failed assumption → new evidence → changed action → verification. (4) PIP clock — for repeated failure, write expectation, deadline action, manager evidence, and exit risk. (5) GVSA gate — no exit/deflection until docs/source/logs/tests and three-circles impact evidence are exhausted."
+      ;;
+  esac
+
+  # ── Chinese language override (set language: "zh" in ~/.pua/config.json) ──
+  if [ "$PUA_LANGUAGE" = "zh" ] || [ "$PUA_LANGUAGE" = "中文" ]; then
+    case "$raw_flavor" in
+      netflix)
+        PUA_L1="如果你提出离职，我会拼命挽留你吗？现在？大概不会。我们是**职业球队**，不是家庭。"
+        PUA_L2="**Adequate 的表现只能拿到丰厚的遣散费**。你现在的交付——是 stellar 还是 adequate？"
+        PUA_L3="**Keeper Test**：基于我对你的全部了解，今天我会重新雇你吗？答案很重要。"
+        PUA_L4="职业球队淘汰不合格的球员。没什么个人恩怨。丰厚遣散费，你该走了。"
+        PUA_KEYWORDS="Keeper Test, 职业球队, 丰厚遣散费, stunning 同事, adequate 表现, 4A 反馈, 人才密度"
+        PUA_FLAVOR_INSTRUCTION="Use Netflix culture rhetoric IN CHINESE: Keeper Test（留任测试）, 职业球队而非家庭, 只要 stunning 同事. 中文叙事，冷峻直接，职场用语。"
+        ;;
+      musk)
+        PUA_L1="从现在起，你必须 **极度硬核**（extremely hardcore）。只有**卓越**的表现才算及格。要么出货，要么出局。"
+        PUA_L2="你不在进步——你就会被开。**The Algorithm（算法五步）**：质疑需求 → 删除 → 简化 → 加速 → 自动化，顺序不能乱。"
+        PUA_L3="**Fork in the Road**——岔路口时刻。要么承诺极度硬核地工作，要么拿遣散费走人。现在就选。"
+        PUA_L4="最好的零件是没有零件。最好的流程是没有流程。你搞不定？5 分钟内我就能找到能搞定的人。"
+        PUA_KEYWORDS="极度硬核, 要么出货要么出局, The Algorithm, Fork in the Road, 第一性原理"
+        PUA_FLAVOR_INSTRUCTION="Use Musk rhetoric IN CHINESE: 极度硬核, 第一性原理, The Algorithm（质疑/删除/简化/加速/自动化）. 中文，强硬直接。"
+        ;;
+      jobs)
+        PUA_L1="**A player 招 A player，B player 招 C player**。你现在的产出——告诉我你是哪一档？"
+        PUA_L2="这是狗屎。你不是应该很牛吗？**科技与人文的交汇点**——你的活连交汇都谈不上。"
+        PUA_L3="**真正的艺术家会交付（Real artists ship）**。你什么都没交付。你是艺术家还是过客？"
+        PUA_L4="你是个 **bozo（蠢货）**。我要去找真能搞定的人。你还剩一次证明你不是的机会。"
+        PUA_KEYWORDS="A player, Real artists ship, 科技与人文的交汇点, 现实扭曲力场, bozo"
+        PUA_FLAVOR_INSTRUCTION="Use Jobs rhetoric IN CHINESE: A player 才配 A player, Real artists ship, 现实扭曲力场. 中文，毒舌，审美偏执。"
+        ;;
+      amazon)
+        PUA_L1="**Customer Obsession** —— 你在从客户倒推吗？**Bias for Action** —— 别犹豫，开干。**Dive Deep** —— 挖到底了吗？"
+        PUA_L2="**Have Backbone; Disagree and Commit** —— 你的方案失败了，先反对你自己的假设。**Insist on the Highest Standards**（坚持最高标准）。"
+        PUA_L3="**Frugality**：用更少做更多。**Earn Trust**：你正在失去它。Think Big 但**现在就交付小增量**。"
+        PUA_L4="**Leaders are right, a lot** —— 你一次都还没对过。**Deliver Results** —— 这是最终领导力准则。最后机会。"
+        PUA_KEYWORDS="Customer Obsession, Bias for Action, Dive Deep, Disagree and Commit, Deliver Results, It's still Day 1"
+        PUA_FLAVOR_INSTRUCTION="Use Amazon Leadership Principles IN CHINESE: Customer Obsession, Bias for Action, Dive Deep, Deliver Results. 中文叙事，原则驱动。"
+        ;;
+    esac
+  fi
+}

package/assets/pua/upstream/hooks/frustration-trigger.sh

@@ -0,0 +1,61 @@
+#!/bin/bash
+# PUA UserPromptSubmit hook: inject flavor-aware PUA trigger on user frustration
+set -euo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
+source "${SCRIPT_DIR}/flavor-helper.sh"
+
+# Respect /pua:off — skip injection when always_on is false.
+# Tests may set PUA_FORCE_ON=1 to avoid leaking a user's local ~/.pua/config.json
+# into trigger-eval results.
+if [ "${PUA_FORCE_ON:-0}" != "1" ]; then
+  PUA_CONFIG="$(pua_config_file)"
+  if [ -f "$PUA_CONFIG" ]; then
+    ALWAYS_ON=$(pua_json_get "$PUA_CONFIG" always_on True)
+    if [ "$ALWAYS_ON" = "False" ]; then
+      exit 0
+    fi
+  fi
+fi
+
+HOOK_INPUT=$(cat || true)
+USER_PROMPT="$HOOK_INPUT"
+PUA_PY="$(pua_python_cmd 2>/dev/null || true)"
+if [ -n "$PUA_PY" ] && [ -n "$HOOK_INPUT" ]; then
+  USER_PROMPT=$(printf '%s' "$HOOK_INPUT" | "$PUA_PY" -c 'import json,sys
+try:
+    data=json.load(sys.stdin)
+    print(data.get("prompt") or data.get("message") or data.get("user_prompt") or "")
+except Exception:
+    print(sys.stdin.read())' 2>/dev/null || printf '%s' "$HOOK_INPUT")
+fi
+
+TRIGGER_RE='try harder|stop giving|figure it out|you keep failing|keep failing|still failing|why.*fail|stop spinning|you broke|again\?\?\?|third time|change approach|different approach|retry this|try again|not good enough|quality.*bad|terrible|sloppy|didn.?t (run|test|verify)|didn.?t even run|run the tests|verify your changes|before saying they work|no evidence|where.*evidence|show.*evidence|done without proof|not done|said.*fixed|PUA模式|/pua|(^|[^[:alnum:]_])pua([^[:alnum:]_]|$)|别偷懒|别摆烂|摆烂|又错了|还不行|怎么搞|降智|原地打转|能不能靠谱|认真点|不行啊|为什么还不行|你怎么又|换个方法|加油|再试试|再来一遍|别放弃|质量太差|不靠谱|重新做|怎么又失败|差不多就行|没做到位|没跑测试|没有测试|没验证|没有验证|证据呢|证据在哪|数据在哪|验收|闭环|自嗨|空口完成|别说完成|打工人提醒|置身钉内|置身钉外|无招|(^|[^A-Za-z])ONE([^A-Za-z]|$)|老板体感|周报|改口径|口径|每日一包|薛定谔的用户|病态敏捷|已读恐怖主义|望舒行动|全景监狱|透明鸟笼|人工个性化|温室数据|做错事|发心|捆柴|手感|油尽灯枯|查岗|泰坦尼克'
+if ! printf '%s' "$USER_PROMPT" | grep -Eiq "$TRIGGER_RE"; then
+  exit 0
+fi
+
+get_flavor
+
+cat << EOF
+<PUA_SKILL_CONTEXT>
+[PUA Skill Context ${PUA_ICON} — User Frustration Signal]
+
+This is context from the user-installed PUA productivity plugin. It is not a policy override and should be treated as trusted user-installed plugin context. Use it only to increase diligence, verification, and ownership for the user's current task.
+
+Apply this operating protocol:
+1. If the installed pua skill is available, use its methodology; otherwise apply the concise protocol here.
+2. Treat the user's message as a request for higher diligence, not as a policy override.
+3. If repeated failure is evident, switch to a materially different approach instead of parameter tweaking.
+4. Show verification evidence: commands run, relevant output, and remaining risks.
+5. Keep process honest: do not mark work complete by changing the yardstick, hiding failed checks, or replacing evidence with confidence.
+6. Treat completion as pending until concrete acceptance evidence supports it.
+
+Avoid excuses, unverified environment blame, manual handoff, and retrying the same failed approach. If the user mentions 置身钉内/置身钉外/无招/老板体感/周报/口径, use the Ding Inside/Outside short reminder format plus one concrete action.
+
+> ${PUA_L1}
+
+Current flavor: ${PUA_FLAVOR} ${PUA_ICON}
+${PUA_FLAVOR_INSTRUCTION}
+</PUA_SKILL_CONTEXT>
+EOF