Why does the project contain two settings files after running npm run setup?	One is a shared template and the other is a machine-specific local configuration.
What security recommendation does Claude Code make regarding hook script paths?	Use absolute paths instead of relative paths.
Which two attacks does using absolute paths for hook scripts help mitigate?	Path interception and binary planting attacks.
Why is it difficult to directly share a settings.json file containing absolute paths?	Absolute paths are machine-specific and change based on each user's project directory location.
What file serves as the shareable template for hook configurations?	settings.example.json
What placeholder is used in the template file to represent the project directory?	$PWD
What does the init-claude.js script do during the setup process?	It replaces $PWD placeholders with the actual absolute path to the project directory.
What is the name of the generated file that holds the resolved absolute paths?	settings.local.json
How does this workflow balance security recommendations with team sharing?	It allows sharing a single template while automatically generating secure, machine-specific paths locally.
What command triggers both dependency installation and the path-initialization script?	npm run setup