Potential fix for code scanning alert no. 6: Improper code sanitization

[Ali-dev11]

Potential fix for https://github.com/Ali-dev11/devforge/security/code-scanning/6

In general, any user-controlled string that is inserted into generated JavaScript code via JSON.stringify must be further sanitized to escape characters that could break out of string or script context (such as <, >, /, newline, etc.). The safest approach is to define a small helper in this file that maps these dangerous characters to safe Unicode escape sequences and to apply this helper to the JSON.stringify(...) result before concatenating it into the generated source.

For this specific issue, we should add an escapeUnsafeChars function (and its associated charMap) somewhere near the top of src/templates.ts (e.g., after the type definitions) and then update line 2202 so that instead of using JSON.stringify(toTitleCase(plan.projectName)) directly, it uses escapeUnsafeChars(JSON.stringify(toTitleCase(plan.projectName))). This keeps existing functionality (the title text remains the same) while ensuring problematic characters are escaped in the generated meta export. No new external imports are needed; this can be implemented with plain TypeScript. All changes must be confined to src/templates.ts within the shown snippet regions.

Suggested fixes powered by Copilot Autofix. Review carefully before merging.