testsAndMisc/linux_configuration/docs/SECURITY_HARDENING_ANALYSIS.md
Krzysztof kuhy Rudnicki 346eb1f00b Bring every markdown file under the cap
Twelve prose violations to zero. Eight files split into per-topic
subdirectories with the original left as an index; both SKILL.md files
keep their frontmatter so discovery still works, with detail moved to
references/.

Deleted docs/cleanup-2026-05/ (7 files) and linux_configuration/docs/
VERIFICATION.md on the user's ruling: unreferenced records of finished
work whose rules are now enforced by the polling, shellcheck and shfmt
hooks. PACMAN_WRAPPER_SECURITY.md was split instead - unlike those, it
documents live guarantees.

Every split verified by a sorted diff against HEAD: zero content lines
lost, only the new headings and index links added.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011w2Pj4Ek3ZNMQVYcFHgXDY
2026-08-16 19:25:59 +02:00

17 lines
797 B
Markdown

# Security Hardening Analysis & Implementation Prompt
## Executive Summary
This document analyzes six digital wellbeing/security scripts and provides a detailed implementation prompt for hardening them against tampering. The analysis is based on thorough code review of the entire codebase.
---
Split into one file per part to stay under the 250-line cap.
- [Part 1: Current State Analysis](security-hardening/01-current-state.md)
- [Part 2: Language Considerations](security-hardening/02-language-choice.md)
- [Part 3: Implementation Prompt](security-hardening/03-implementation.md)
- [Part 4: Agent Personas](security-hardening/04-agent-personas.md)
- [Part 5: LLM README Files](security-hardening/05-llm-readmes.md)
- [Part 6: Test Script Template](security-hardening/06-test-template.md)