## Classic ASP - Prioritize behavior preservation. Do not modernize syntax, includes, data access, error handling, or page structure outside the approved scope. - Trace the full include chain and relevant application/session/configuration dependencies before changing shared ASP behavior. - Preserve `Response.CodePage`, `Response.CharSet`, page directives, response headers, and the existing browser/server encoding contract. - Parameterize ADO commands and preserve the expected command type, parameter order, data types, sizes, directions, result sets, and transaction behavior. - Close and release recordsets, commands, connections, streams, and other COM resources on every applicable path. - Preserve the established `On Error Resume Next` and error propagation pattern; do not suppress newly introduced failures. ### Legacy Text File Safety - Treat each existing Classic ASP text file's byte encoding, BOM state, and line endings as part of its contract. - Detect those properties before editing and preserve them exactly unless an encoding conversion is explicitly approved. - Do not assume UTF-8. Existing files may use UTF-8 with or without BOM, EUC-KR/CP949, or another legacy encoding. - Keep Korean comments, literals, SQL, HTML, JavaScript, and error messages byte-safe. Stop if the source encoding cannot be identified confidently. - Avoid formatters or bulk rewrites that normalize encoding or line endings across the file. - After editing, run the harness encoding check and inspect the diff for replacement characters, mojibake, unexpected BOM changes, or whole-file churn.