Estate style cleanup: keep client BugSink DSN, split Main HUD chrome #1

Merged
epistemophiliac merged 2 commits from style/estate-cleanup into main 2026-07-27 06:07:11 +00:00

Summary

  • Keep the BugSink client ingest DSN in the APK (required so every player's device can report); document that it is public ingest, not an admin secret. Rename script to BugSinkClient.gd because Godot forbids class_name matching the BugSink autoload.
  • Split HUD build/layout into HudChrome.gd; Main stays the run/tutorial controller (class_name AphelionMain). Document signals; tighten a few typed containers.
  • Add scripts/ci_shellcheck.sh + Jenkins Shellcheck stage (Estate Bash gate).

Test plan

  • bash scripts/ci_shellcheck.sh
  • bash scripts/ci_test.sh — 170/170 passed
  • Jenkins green on the PR branch
  • Smoke: title → Options → Back; Begin Run → layout on phone-ish viewport
## Summary - Keep the BugSink **client ingest DSN** in the APK (required so every player's device can report); document that it is public ingest, not an admin secret. Rename script to `BugSinkClient.gd` because Godot forbids `class_name` matching the `BugSink` autoload. - Split HUD build/layout into `HudChrome.gd`; Main stays the run/tutorial controller (`class_name AphelionMain`). Document signals; tighten a few typed containers. - Add `scripts/ci_shellcheck.sh` + Jenkins `Shellcheck` stage (Estate Bash gate). ## Test plan - [x] `bash scripts/ci_shellcheck.sh` - [x] `bash scripts/ci_test.sh` — 170/170 passed - [ ] Jenkins green on the PR branch - [ ] Smoke: title → Options → Back; Begin Run → layout on phone-ish viewport
Keep the public ingest DSN in-client (required for every player's reports), document why class_name is BugSinkClient vs autoload BugSink, split HUD chrome out of Main, document signals, tighten a few typed containers, and add a shellcheck CI stage.

Co-authored-by: Cursor <[email protected]>
epistemophiliac deleted branch style/estate-cleanup 2026-07-27 06:07:11 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
epistemophiliac/gametestv1!1
No description provided.