Markdown

Outcome: Complete the task with Markdown (Markdown). User context: Un team scrive un unico README. GitHub lo formatta, mentre i terminali e le revisioni del codice mostrano ancora testo leggibile. Technology or engineering concept: Markdown (Markdown). Why it fits: Usalo per guide, modelli di issue, note di rilascio o prompt AI strutturati. Do not use it when: Evita estensioni specifiche di una piattaforma quando il testo deve avere un aspetto coerente in più strumenti. Engineering fit: Define where it runs and which version to use. Set its job, interfaces, data flow, dependencies, supported systems, security, and speed limits. Explain how it fits the current stack. Lifecycle safeguards: Check dependency health and licenses. Add monitoring and a fallback. Name the upgrade owner. Do not add a second tool for the same job without a measured benefit. Acceptance criteria: A small integration proves the needed behavior. Test compatibility, security, failure, and performance. Document deploy, upgrade, support, and rollback steps. Evidence and limits (evidence boundary): Un documento formale può ancora essere una bozza, un release candidate o la versione finale. Controlla il suo stato e il supporto per browser o piattaforma. Unknowns to confirm: Current stack, runtime and version rules, target systems, dependency owner, performance budget, support period, and migration limits.