Repository instructions

Commit and push shorthand

When the user says "마무리 해" (or "마무리해"), treat it as authorization to verify the completed task, commit its changes, and push to the configured upstream.
Otherwise, push only with the user's explicit authorization. Preserve unrelated pending changes and report what was committed and pushed.
This shorthand does not authorize offline artifacts, version bumps, tags, or separate manual deployments.

The supported product and release target is the online app, including the GitHub Pages deployment.
Do not run npm run build:offline or npm run package:offline during implementation, verification, commits, releases, or deployments.
Do not create, commit, upload, or publish standalone offline builds, offline-dist/ output, or offline ZIP artifacts.
Online/offline feature parity is no longer required. Legacy offline-related source may remain only where the online Pages build still depends on shared adapters.
Verify repository changes with the relevant tests, npm run check, npm run build, and npm run build:pages when preparing a deployment.
Do not bump the package version, create version-specific release notes, create tags, or publish GitHub Releases for routine online commits and deployments unless the user explicitly requests them.
Use UPDATES.md as the single user-facing update history and include only changes that affect service users.