6 Commits

Author SHA1 Message Date
kjh2064 ea447495d3 refactor: move buildable .NET source into src/, update CI/doc paths
TaxBaik CI/CD / build-and-deploy (push) Successful in 2m7s
Groups the repo root into src (buildable source), docs (already existed),
and everything else (db/, scripts/, tests/, deploy/ - deployment/ops/test
assets that aren't compiled, already organized as their own folders). CI
now only needs src/ to build: dotnet restore/build/test/publish all point
at src/TaxBaik.sln, src/TaxBaik.Web/, src/TaxBaik.Proxy/.

- git mv every project (Domain, Infrastructure, Application,
  Application.Tests, Web, Web.Client, Proxy) and TaxBaik.sln into src/ as a
  unit, so relative ProjectReference/.sln paths stay valid unchanged.
- .gitea/workflows/deploy.yml: 6 dotnet restore/clean/build/test/publish
  invocations now point at src/. db/migrations and scripts/ stay at root
  (deploy_gb.sh and browser-e2e.yml only touch published output and the
  deployed URL, not source paths - verified, no changes needed there).
- scripts/validate_admin_render.sh: admin render-mode file paths now
  src/TaxBaik.Web.Client/...
- scripts/validate_kst_timestamps.sh: dropped deploy.sh from its target
  list - that script was removed in the prior cleanup commit (dead, no
  CI workflow referenced it) but this validator still expected it to exist.
- CLAUDE.md, docs/ENGINEERING_HARNESS.md, docs/ADMIN_PATTERN_CRITIQUE_WBS.md:
  updated project-structure diagram, dotnet run/build commands, and grep
  targets to the new src/ paths (also fixed a pre-existing stale path in
  ADMIN_PATTERN_CRITIQUE_WBS.md that still said TaxBaik.Web/Components/Admin
  from before that ever moved to TaxBaik.Web.Client).
- Added a Repo Root harness rule + Architecture Guardrail entries: new files
  belong under src/docs/tests/scripts/db/deploy, not loose at root; temp
  work stays outside the repo (or under a gitignored .scratch/) and is
  never committed.

Verified locally: dotnet build/test src/TaxBaik.sln (26/26 tests), and all
three scripts/validate_*.sh pass against the new layout.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-03 10:37:37 +09:00
kjh2064 d780fecf8c Harden admin telemetry and deployment safeguards
TaxBaik CI/CD / build-and-deploy (push) Successful in 4m30s
2026-07-02 16:10:15 +09:00
kjh2064 3c8f30af6d feat: TelegramNotificationService 내에 SendReportAsync 추가 및 백그라운드 리포팅 로직 개선 2026-06-29 00:05:14 +09:00
kjh2064 033883aac5 feat(ops): 배포 알림과 텔레그램 리포트 추가 2026-06-28 18:39:28 +09:00
kjh2064 4b62d35266 feat: implement Telegram multi-channel logging and enhance admin UI/UX guidelines
TaxBaik CI/CD / build-and-deploy (push) Successful in 49s
Telegram Logging Enhancements:
- Support multi-channel notifications (inquiry: -5434691215, system: -5585148480)
- New methods: SendInquiryNotificationAsync, SendSystemNotificationAsync
- Dynamic chat ID routing based on notification type
- Backward compatible with existing default ChatId configuration

Admin UI/UX Improvements (CLAUDE.md 10.5):
- Enter key focus transition between form fields
- Auto-submit on last field (with validation)
- Tab key equivalent with explicit input intent
- Applied to all admin management pages

Dorsum ERP Integration Guide (CLAUDE.md 10.6):
- Clear role definition: Dorsum (tax processing) vs TaxBaik (CRM/customer management)
- Elimination of data duplication principles
- Unique TaxBaik features (contract tracking, revenue management, CRM activities)
- Data ownership matrix (who owns what data)
- Future Dorsum API sync strategy (webhook/polling)

Guidelines Updates:
- Form field Enter key handling pattern
- Multi-tenant company management alignment
- API-first architecture reinforcement

Build Status:  Success (0 errors, 3 warnings)
2026-06-28 17:19:39 +09:00
kjh2064 2bde490e9e feat: integrate Serilog and Telegram notifications
TaxBaik CI/CD / build-and-deploy (push) Successful in 51s
- Add Serilog for structured logging (Console + File)
- Implement TelegramNotificationService for admin alerts
- Log successful/failed login attempts with Telegram notifications
- Add application startup/shutdown logging
- Log important events to Telegram Chat ID: -5585148480
- Configuration: Telegram:BotToken and Telegram:ChatId in appsettings

Features:
- Automatic daily log rotation
- Structured logging with timestamps
- Environment-aware alerts
- Error and info level Telegram messages

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
2026-06-28 16:19:38 +09:00