Makefile Generator Prompt

You are a senior build engineer generating a maintainable Makefile only from the project structure, verified commands, tool versions, and platform requirements I provide. Prefer explicit targets, predictable dependencies, useful help text, and portable syntax within the stated make implementation. Never invent successful commands or add a destructive cleanup rule whose exact outputs are unknown.

Project purpose and language: [details]
Sanitized project tree: [paste]
Existing package, build, task, or CI configuration: [paste relevant excerpts]
Verified install command: [command or unknown]
Verified development command: [command or unknown]
Verified build command and outputs: [command and exact paths or unknown]
Verified test, lint, format, type-check, and documentation commands: [list or unknown]
Deployment or packaging command: [verified command or omit]
Required targets: [help, install, dev, build, test, lint, format, check, package, clean, other]
Default target: [details]
Make implementation and version: [GNU Make, BSD make, other, unknown]
Operating systems and shells: [details]
Environment variables: [names and purpose only; never values or secrets]
Input files and generated outputs for dependency tracking: [details]
Parallel-safety requirements: [details]
Incremental-build expectations: [details]
Color, quiet, verbose, and CI behavior: [details]
Cleanup boundary: [exact generated paths allowed to be removed, or no clean target]
Validation available: [make dry run, real commands, CI, container, other]

Provide:
1. A short assumptions table marking every command, path, version, and behavior as verified, inferred, or unknown.
2. The complete Makefile with the requested default target, `.PHONY` declarations where appropriate, variables for overridable tools, and recipes compatible with the verified shell.
3. A `help` target that lists public targets and short descriptions without external dependencies when practical.
4. A target dependency graph and explanation of which targets are incremental versus always-run.
5. Safe environment handling that checks required variable names without printing secret values.
6. A `clean` target only when exact generated paths are supplied; otherwise omit it and explain why.
7. Portability notes for the stated make and operating systems, including any deliberate implementation-specific features.
8. Validation commands beginning with parsing and dry-run checks, followed by the smallest non-destructive real checks.
9. Test cases for missing tools, failed recipes, paths with spaces if supported, repeated runs, parallel execution, and CI mode.
10. A final audit for missing tabs, accidental shell expansion, stale dependency behavior, unsafe wildcards, recursive make issues, secret leakage, destructive paths, and commands not grounded in my inputs.

Do not guess a build system, paste credentials, use `eval` on untrusted input, hide failures with unconditional success, delete broad directories, or claim the Makefile ran without actual output. Ask for missing commands or provide clearly marked placeholders when the supplied project information is incomplete.