#!/bin/bash
# Verify whether onboarding persists `session.agent` before install.sh consumes it.
rg -nP --type=ts -C3 'markStep(Start|Complete)\("agent_setup"'
rg -nP --type=ts -C2 '\bagent\s*:'

# Verify how agent is persisted in session and what markStepComplete does
rg -nP --type=ts 'sandboxConfig\s*=' -A 5 src/lib/agent-onboard.ts
rg -nP --type=ts 'markStepComplete' -B 2 -A 2 src/lib/
rg -nP --type=ts 'const markStepComplete' -A 15 src/lib/onboard-session.ts

# Get the full markStepComplete function implementation
sed -n '463,500p' src/lib/onboard-session.ts

# Get the filterSafeUpdates function to see what fields are whitelisted
rg -nP --type=ts 'function filterSafeUpdates|const filterSafeUpdates' -A 30 src/lib/onboard-session.ts

# Check if agent is ever passed to markStepComplete or other session updates
rg -nP --type=ts 'markStepComplete|completeSession|updateSession' -B 2 -A 2 | grep -E '(agent|markStepComplete|completeSession)' | head -50

# Check where agent is actually written to the session
# Look for any direct assignment or explicit passes to session updates
rg -nP --type=ts 'session\.agent\s*=' -B 2 -A 2
rg -nP --type=ts '\bagent:' src/lib/onboard.ts -B 1 -A 1 | head -40

# Check if agent field is ever persisted to session anywhere
# by searching for direct updates that might bypass filterSafeUpdates
rg -nP --type=ts 'agent.*null|agent.*string' src/lib/onboard-session.ts
rg -nP --type=ts 'saveSession|updateSession' src/lib/agent-onboard.ts

# Check the context of line 4328 where s.agent is assigned
sed -n '4320,4340p' src/lib/onboard.ts

# Verify the Bash version requirement for parameter expansion ${var^}
# Check what shell directive or version requirement the scripts use
head -5 scripts/install.sh
# Also check if there are any shell version comments or tests
rg -nP '#!/bin/bash|bash.*version|Bash' scripts/install.sh

# Verify if the agent field persists through the full onboarding by checking updateSession
# and whether agent is preserved in the in-memory session object
rg -nP --type=ts 'updateSession.*function|function updateSession' -A 20 src/lib/onboard-session.ts | head -30

# Check where ${var^} syntax is used in the install.sh
rg -nP '\$\{[^}]+\^' scripts/install.sh

# Verify that updateSession actually persists the agent field to file
# by checking saveSession
rg -nP --type=ts 'function saveSession|const saveSession' -A 10 src/lib/onboard-session.ts

#!/bin/bash
# Find Bash-4-only uppercase-first expansions and check whether a minimum Bash version is documented.
rg -nP --type=sh '\$\{[^}]*\^\}'
rg -nP -S 'minimum bash|bash 4|bash >= ?4|Bash >= ?4'

# Check shebang and context around the problematic lines
head -20 scripts/install.sh | cat -n

# Read the specific problematic lines with context
sed -n '210,220p' scripts/install.sh | cat -n
sed -n '233,242p' scripts/install.sh | cat -n

# Search for Bash version requirements in common places
grep -r "bash" README.md 2>/dev/null | head -20
grep -r "minimum" README.md 2>/dev/null
find . -name ".github" -o -name "Makefile" -o -name "*.yaml" -o -name "*.yml" | head -10

# Check if ShellCheck config allows/disables checks for this pattern
cat .shellcheckrc 2>/dev/null || echo "No .shellcheckrc found"

# Verify if there are any disable directives in install.sh
grep -n "shellcheck" scripts/install.sh || echo "No shellcheck directives found"

# Search for version checks or minimum Bash requirements
grep -n "BASH_VERSION\|bash.*version\|version.*bash" scripts/install.sh

# Check README and documentation for Bash requirements
grep -i "bash\|requirement\|require" README.md | head -20

# Check CI/CD workflows for Bash version info
cat .github/workflows/*.yaml 2>/dev/null | grep -i "bash\|shell" | head -20

# Check if there's a shebang or version constraint anywhere
find . -name "*.sh" -type f -exec head -1 {} \; | sort | uniq

# Check GitHub Actions environment details and how bash is invoked
find .github/workflows -name "*.yaml" -o -name "*.yml" | xargs cat 2>/dev/null | grep -A5 -B5 "bash\|shell"

# Check if there are any conditional guards that prevent this code from running
grep -B10 "NEMOCLAW_AGENT\^" scripts/install.sh | head -30

# Check the actual usage of these variables to see if they're always defined
grep -n "NEMOCLAW_AGENT=" scripts/install.sh
grep -n "agent_name=" scripts/install.sh

# Verify the flow - are these code paths actually reachable in a real installation?
grep -B20 "Launch.*OpenShell" scripts/install.sh | tail -25

# Check if there's conditional logic that guards whether this installer even runs on Bash 3.2
grep -n "BASH_VERSINFO\|bash.*version" scripts/install.sh
grep -n "version_check\|check.*version\|minimum" scripts/install.sh | head -10

# Get the exact line 237 and surrounding context more precisely
sed -n '235,242p' scripts/install.sh | cat -n

# Verify what resolve_onboarded_agent returns and where agent_name is used
sed -n '233,250p' scripts/install.sh | cat -n

# Test if Bash 4.0+ parameter expansion is really needed or if it's just for formatting
# Check what these variables contain
grep -A5 "NEMOCLAW_AGENT=" scripts/install.sh | head -10
grep -A5 "resolve_onboarded_agent" scripts/install.sh | head -15