filename="/usr/local/bin/readme-generator.sh"

conf_print_readme_generator_sh() {
	cat <<-'EOF'
		#!/usr/bin/env bash
		# Target-aware README.md Generator

		: "${BUILD_DIR:=$HOME/staging_area}"
		OUTPUT_FILE="${BUILD_DIR}/README.md"

		mkdir -p "$(dirname "$OUTPUT_FILE")"

		cat <<'MARKDOWN' > "$OUTPUT_FILE"
		# Literate DevOps Pipeline: AI → Markdown → Idempotent Bash

		A structured workflow for turning AI-generated Markdown into **validated, reproducible infrastructure**.

		---

		## 🧠 Core Mental Model

		Every file is written using:

		```bash
		${BUILD_DIR}${filename}
		```

		Where:

		- `filename` = absolute system path (e.g. `/etc/nginx/nginx.conf`)
		- `BUILD_DIR` = **target root filesystem**

		---

		## 🧭 Target System Design

		The pipeline introduces:

		- `WORKSPACE_DIR` (default: `~/staging_area`)
		- `TARGET` (default: `dev`)

		Derived as:

		```bash
		BUILD_DIR="${WORKSPACE_DIR}/${TARGET}"
		```

		---

		## 📦 Example Resolution

		Command:

		```bash
		meta-pipeline.sh --target prod setup.md
		```

		File:

		```bash
		filename="/etc/nginx/nginx.conf"
		```

		Final output:

		```text
		~/staging_area/prod/etc/nginx/nginx.conf
		```

		---

		## ⚖️ Precedence Rules

		Explicit `BUILD_DIR` always wins:

		```bash
		BUILD_DIR=/tmp/custom meta-pipeline.sh --target prod setup.md
		```

		Result:

		```text
		/tmp/custom/etc/nginx/nginx.conf
		```

		---

		## 🔄 Pipeline Stages

		```mermaid
		graph TD
		    AI[AI Markdown] --> VAL[Validator]
		    VAL --> CONV[Converter]
		    CONV --> EXEC[Execution]
		    EXEC --> FS[BUILD_DIR Root FS]
		```

		---

		## 🧪 Usage

		### Default (dev)

		```bash
		meta-pipeline.sh setup.md
		```

		### Specific target

		```bash
		meta-pipeline.sh --target prod setup.md
		```

		### Explicit override

		```bash
		BUILD_DIR=/tmp/root meta-pipeline.sh setup.md
		```

		---

		## 🧩 Multi-Target Builds

		Run multiple environments:

		```bash
		for t in dev prod container; do
		    meta-pipeline.sh --target "$t" setup.md
		done
		```

		Result:

		```text
		~/staging_area/dev/...
		~/staging_area/prod/...
		~/staging_area/container/...
		```

		---

		## 🔍 Diff Environments

		```bash
		diff -ru ~/staging_area/dev ~/staging_area/prod
		```

		---

		## 🤖 AI Workflow

		```mermaid
		sequenceDiagram
		    participant User
		    participant AI
		    participant Validator
		    participant Pipeline

		    User->>AI: Generate Markdown
		    AI-->>User: Structured Markdown
		    User->>Validator: Validate
		    Validator-->>User: Pass/Fail
		    User->>Pipeline: Run pipeline
		    Pipeline-->>User: Staged filesystem
		```

		---

		## 🔒 Guarantees

		- Idempotent file writes
		- Safe staging via `BUILD_DIR`
		- Strict validation (Level 3 invariants)
		- Reproducible builds

		---

		## 🚀 Summary

		This system behaves like:

		- `make install DESTDIR=...`
		- Docker root filesystem builds
		- A minimal configuration management system

		But with:

		- Native Bash
		- Markdown as the DSL
		- AI as the generator

		MARKDOWN

		echo "[SUCCESS] README.md generated at $OUTPUT_FILE"
	EOF
}

mkdir -p "$(dirname "${BUILD_DIR}${filename}")"
conf_print_readme_generator_sh | tee "${BUILD_DIR}${filename}" > /dev/null
chmod +x "${BUILD_DIR}${filename}"