## Poll Recruit Repository Rules ### Repository Role and Boundaries - This is the Classic ASP exit-poll recruitment system. Prioritize production maintenance and behavior preservation until a migration slice is explicitly approved. - Treat `AdminPoll` and `Recruit` as distinct application areas with duplicated or similar infrastructure. Trace the active include chain before changing a shared DB, session, authentication, or utility file. - Preserve existing routes, form fields, cookies, sessions, redirects, browser behavior, identity-verification integration, and MSSQL result shapes. - Do not perform broad ASP cleanup, include consolidation, SQL relocation, or framework migration as part of an unrelated fix. ### SQL and Data-Access Improvement - SQL embedded in pages and shared helpers is a primary modernization target, but change it in small behavior-preserving slices. - For a touched flow, separate request parsing, authorization, SQL execution, domain decisions, and HTML rendering where the current structure permits a safe seam. - Parameterize new or changed values and preserve ADO command types, parameter order and size, transactions, recordset shapes, null behavior, and ordering. - Characterize current output and side effects before splitting a large query or duplicated DB helper. Do not execute real database calls during validation without separate approval. ### Project-Specific Encoding Contract - Preserve every existing ASP file's encoding, BOM, and line endings individually; never run repository-wide encoding normalization. - `Recruit/Identification/checkplus_success.asp` and `Recruit/Identification/phoneIdentityVerificationProc.asp` are CP949-family files and must not be patched as UTF-8. - Treat the identity-verification files and their response charset behavior as an external integration contract. Do not convert their encoding or change charset handling without explicit approval and byte-level verification. - When a task touches Korean comments, literals, errors, HTML, JavaScript, or SQL, inspect the resulting bytes and diff for mojibake or replacement characters. ### Full-Stack Migration Direction - The approved destination is a Spring Boot backend and Next.js/TypeScript frontend, consolidated with the KEPS system through staged migration slices. - Establish API, authentication, recruitment workflow, identity-verification, database, and operational compatibility before replacing a page or flow. - Keep migrated and legacy routes interoperable until the approved slice has acceptance criteria, rollout, and rollback coverage. ### Harness and Verification - `AGENTS.md` and `CLAUDE.md` are generated. Edit `.agent/profile.yml` or `.agent/project.md`, then recompose instead of editing generated files. - Validate with static inspection and safe local checks only. Do not call the identity provider, connect to a real database, or submit recruitment data without separate approval.