aiops: claude - Configure Claude settings and privacy boundaries #259

AI Ops Summary

Configure Claude settings and privacy boundaries for lightspeedwp/ThisOneTimeOnAcidCom.

Build Summary

Delivery and remaining validation — 17 October 2026

Settings and supporting documentation were delivered in aiops: claude - Configure agents, hooks, skills and cloud settings, merged into develop. Supported keys, model configuration, privacy boundaries, precedence and effective loaded settings remain unverified. Acceptance checkboxes remain unchanged; author-reported tests are not independently verified.

Implement .claude/settings.json, .claude/settings.example.json and private-configuration exclusions in .gitignore. Document shared, local, user-wide, managed and cloud configuration ownership in docs/claude-configuration.md.

Linked Stories/Tasks/PRs/Epic

Parent: #218.

Milestones & Timeline

No milestone or deadline specified. Estimates remain unset.

Problem / Opportunity

Shared defaults must be separated from personal configuration, credentials and machine-specific values.

Approach / Solution

Follow the repository’s own instructions. Establish settings ownership and supported keys before configuring dependent agents, hooks, skills and cloud behaviour.

Acceptance Criteria

• AI workflow/agent described
• Problem/opportunity scoped
• Success metric defined
• Documentation updated
• PR uses correct branch prefix (aiops/)
• PR description updated with relevant details
• Changelog entry prepared for PR (if applicable)
• Labels/types match org standards
• Settings use supported keys for the verified Claude Code version.
• Shared defaults contain no credentials, personal paths or machine-specific values.
• Local settings are excluded from version control.
• Permissions, precedence, setup and rollback are documented.
• JSON validation and effective-setting checks are recorded.

Additional Context

Recheck settings and hook registration against the merged revision. Record supported-schema and effective-setting evidence; reconcile setup and rollback documentation with actual behaviour.

Dependencies: parent baseline decisions covering integration branch, branch naming, runtime, package manager and Claude compatibility. Branch-prefix policy remains subject to repository verification. Preserve protected files; do not edit CHANGELOG.md without separate authorisation.

Definition of Ready (DoR)

• AI ops goal described
• Area/action mapped
• Acceptance criteria listed
• Estimate added

Definition of Done (DoD)

• All acceptance criteria met
• Solution/automation verified
• Documentation updated
• PR uses correct branch prefix (aiops/)
• PR uses the correct PR template based on type:aiops PR label or linked issue type or linked issue type:aiops label
• Branch deleted after merge
• Linked issue(s) updated with latest status and closed after merge,
• The related epic should not be closed, instead updated with a comment to reflect the closed issue

Branch instructions

• Repository: lightspeedwp/ThisOneTimeOnAcidCom.
• Implementing target: this settings/privacy issue; independently verified counterpart GitHub issue 259.
• Parent context: existing coordination parent only. Do not copy its identifier or link into the branch, PR title or PR body, or use it as a native development/closing target.
• Allowed closing targets: none currently verified. This issue becomes eligible only after its complete agreed outcome and acceptance evidence are satisfied and association effects verified; never the coordination parent.
• Branch state: proposed new branch; no verified existing branch suitable for reuse.
• Branch: aiops/claude-settings-privacy.
• Base: develop, checked at 4ecdb26d9655a48bf000a7c89da2f70383edce87.
• Naming policy: local guide, validator and organisation strategy. aiops fits settings/privacy work; it is not application feature development. Proposed name checked statically only.
• PR template: verified shared AI-ops template. Populate explicitly; local routing lacks reliable AI-ops selection. Do not copy template sample closing clauses or parent references.
• Missing evidence: installed Claude version, supported keys/model, managed/user/project precedence and effective settings. Existing guidance calls shared settings locked: resolve ownership before editing. Locked configuration remains human-only wherever that rule applies; implementation approval cannot override that prohibition.
• Constraints: planning only. Preserve unrelated changes; no automatic branch creation, reuse, renaming, implementation, force-push, merge or deployment. File plans are not execution authority.

Expected file changes

Provisional and bounded. All existing paths read at 4ecdb26d9655a48bf000a7c89da2f70383edce87. Existence is not approval or evidence of completed implementation.

No change proposed to .gitignore: .claude/settings.local.json and .claude/*.local.json exclusions already exist. Their presence alone does not prove complete privacy.

No creates, moves or deletions proposed. Compatibility findings may change this plan, not authorise additional files. Agent/skill/cloud configuration, dependencies, unrelated protected files and workflows are outside scope. Any materially different operation requires a revised preview and approval.