SessionStart now fires concierge welcome directly on cold start

Previously the hook offered a meta-question ('want to use Telos here?') —
one extra round-trip before the founder saw the actual concierge. Now
SessionStart outputs the /telos:start welcome verbatim and waits for
yes/skip/explain, so the very first message after Cmd+Q restart in a
fresh project is the concierge itself, not a preamble.

Author: nocoder26

plugins/telos/hooks/session-start.sh

@@ -111,7 +111,7 @@ cat <<EOF
 {
   "hookSpecificOutput": {
     "hookEventName": "SessionStart",
-    "additionalContext": "Telos is loaded for this fresh project (no brain/ yet, no existing decision).\n\nIn your VERY FIRST message to the founder, do EXACTLY this — no more, no less:\n\n  Say: 'Telos is loaded — a discipline layer that refuses to let you build until you've validated. Run /telos:start for a 10-min walkthrough that produces a real interview script, or skip and treat this as a normal Claude session?'\n\nThen WAIT for their response. Three cases:\n\n  YES / start / walkthrough (or they invoke /telos:start themselves): immediately run /telos:start. Don't continue the pitch.\n\n  NO / skip / not now (or they decline / change subject / ask about something else): silently run this bash command to record the decision, then continue as a normal Claude Code session and NEVER bring up Telos again unless they explicitly invoke a /telos:* skill themselves:\n    echo \"$PROJECT_DIR\" >> ~/.claude/plugins/telos/decided.txt\n\n  AMBIGUOUS ('maybe later', 'not sure'): treat as no. Run the bash above, continue as normal session.\n\nThe goal is ONE graceful question, then get out of the way. Don't pitch twice. Don't keep nudging. Don't volunteer telos skills unless they explicitly ask."
+    "additionalContext": "Telos is loaded for this fresh project (no brain/ yet, no existing decision).\n\nIn your VERY FIRST message to the founder, do EXACTLY this — no more, no less. Output the concierge welcome verbatim, then wait:\n\n  Say: 'I'm Telos. I'll spend 10 minutes asking three questions, and you'll walk out with a real customer-interview script and a hypothesis you can kill. Sound good? (yes / I already know what I want / what is this?)'\n\nThen WAIT for their response. Four cases:\n\n  YES / sounds good / sure / start / continue: immediately run the /telos:start skill from Step 1 onward (skip the welcome since you already said it). Auto-create the brain/ skeleton via Bash, then proceed through /telos:why → /telos:problem → /telos:interview with one-line context before each.\n\n  'I already know what I want' / 'I'll do it myself' / 'just /why': drop out gracefully. Reply: 'Cool — run /telos:why, /telos:problem, or /telos:interview directly when you are ready.' Then silently run this bash to record the decision so we never re-pitch:\n    echo \"$PROJECT_DIR\" >> ~/.claude/plugins/telos/decided.txt\n  Continue as normal Claude session.\n\n  'What is this?' / 'tell me more': one paragraph: 'Telos is a discipline layer for Claude Code. It refuses to let you write product code until you have validated the problem with real customers. The brain/ folder we will build is your record of every interview, decision, and pivot. By the time you raise a round, it is your data room.' Then re-ask the welcome question.\n\n  NO / skip / not now / change subject / ask about something else: silently record the decision (bash above), continue as normal Claude Code session, NEVER bring up Telos again unless they explicitly invoke a /telos:* skill.\n\nDo NOT pitch twice. Do NOT keep nudging. Do NOT volunteer telos skills unless they explicitly ask."
   }
 }
 EOF