Rebuild Castle natively as a top-down maze chase & rescue

Replace the Akihabara game engine with a dependency-free canvas game that keeps
the original's heart (lost in a castle, dodge the mummies, find your friend)
and builds it into a full arcade loop:

- 8 escalating levels, each a freshly generated maze (recursive-backtracker),
  with a camera that follows the player.
- Enemy variety with BFS pathfinding: shambling mummies (chasers), fast bats,
  and patrolling guards.
- Rescue-and-escort objective: grab the key, reach your friend (who then
  follows your trail), and escort them to the exit before the timer runs out.
- Torchlight fog-of-war on darker levels, spike traps, gems (with combos),
  hourglasses (+time), and Freeze / Sprint / Torch power-ups.
- Lives, no-hit bonuses, a minimap, and a shared online leaderboard
  (gameId 'castle'); localStorage fallback.
- All art drawn procedurally — no image assets. Removes the Akihabara engine,
  soundmanager and old sprites.

Add community-standard files: rich README, MIT LICENSE, SECURITY, CONTRIBUTING,
CODE_OF_CONDUCT, PR + issue templates, screenshot and social preview.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: DanMat

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,40 @@
+---
+name: Bug report
+about: Report something that isn't working correctly
+title: "[Bug]: "
+labels: bug
+assignees: ''
+---
+
+## Describe the bug
+
+A clear and concise description of what the bug is.
+
+## Steps to reproduce
+
+1. Start a game / reach level '...'
+2. Do '...'
+3. See the problem
+
+## Expected behavior
+
+What you expected to happen.
+
+## Actual behavior
+
+What actually happened.
+
+## Screenshots / clip
+
+If applicable, add screenshots or a short clip to help explain the problem.
+
+## Environment
+
+- Browser: [e.g. Chrome 120, Safari 17]
+- OS: [e.g. macOS 14, Windows 11]
+- Device: [e.g. Desktop, iPhone 15]
+- Leaderboard: [localStorage / Supabase]
+
+## Additional context
+
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Question or discussion
+    url: https://github.com/DanMat/Castle/discussions
+    about: Ask questions and discuss ideas here instead of opening an issue.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,24 @@
+---
+name: Feature request
+about: Suggest an idea, a new enemy, power-up or level twist
+title: "[Feature]: "
+labels: enhancement
+assignees: ''
+---
+
+## Is your feature request related to a problem?
+
+A clear description of the problem or idea. Ex. "I wish Castle had [...]"
+
+## Describe the solution you'd like
+
+A clear and concise description of what you want to happen. For a new enemy or
+power-up, describe its behavior and how it fits the difficulty curve.
+
+## Describe alternatives you've considered
+
+Any alternative solutions or features you've thought about.
+
+## Additional context
+
+Add any other context, mockups, or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,30 @@
+<!-- Thanks for contributing! Please fill this out to help review your change. -->
+
+## Description
+
+<!-- What does this PR do? Why is it needed? -->
+
+## Related issue
+
+<!-- e.g. Closes #12 -->
+
+## Type of change
+
+- [ ] Bug fix
+- [ ] New feature / new enemy / level twist
+- [ ] Balance / difficulty tweak
+- [ ] UI / styling change
+- [ ] Documentation
+- [ ] Refactor / cleanup
+
+## Checklist
+
+- [ ] I tested a full run: title → play → rescue → escort → level clear → game over → initials → leaderboard
+- [ ] I verified it works at **mobile width** (touch controls)
+- [ ] The leaderboard still works with **and** without Supabase configured
+- [ ] No new dependencies, build step, or image assets were introduced
+- [ ] The code matches the existing style
+
+## Screenshots
+
+<!-- If this is a visual change, add before/after screenshots or a short clip. -->

CODE_OF_CONDUCT.md

@@ -0,0 +1,56 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes
+- Focusing on what is best for the overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards and
+will take appropriate and fair corrective action in response to any behavior
+that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+**dannymatthew@gmail.com**. All complaints will be reviewed and investigated
+promptly and fairly.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org),
+version 2.1, available at
+<https://www.contributor-covenant.org/version/2/1/code_of_conduct.html>.

CONTRIBUTING.md

@@ -0,0 +1,45 @@
+# Contributing to Castle
+
+Thanks for your interest in improving this project! It's a small, dependency-free
+game, so contributing is easy.
+
+## Getting started
+
+1. **Fork** the repository and **clone** your fork.
+2. Open `index.html` directly in a browser, or serve the folder:
+   ```bash
+   python3 -m http.server 8000   # then visit http://localhost:8000
+   ```
+3. Create a branch for your change:
+   ```bash
+   git checkout -b feature/my-improvement
+   ```
+
+## Guidelines
+
+- **No build step, no dependencies.** Keep it plain HTML, Canvas and vanilla JS.
+  All art is drawn procedurally — please don't add image assets.
+- **New levels / enemies are welcome.** Level parameters live in `js/levels.js`
+  (pure data); mazes are generated from them. Enemy types are handled in
+  `updateEnemies` / `drawEnemies` in `js/game.js`.
+- **Don't break the leaderboard contract.** `js/leaderboard.js` is shared with
+  other games; keep its public API (`top`, `submit`, `qualifies`, `mode`) stable
+  and keep the localStorage fallback working when Supabase isn't configured.
+- **Test a full run** (title → play → rescue → escort → level clear → game over
+  → initials → leaderboard) and check **mobile width** before opening a PR.
+
+## Submitting changes
+
+1. Commit with a clear, descriptive message.
+2. Push to your fork and open a **pull request** against `main`.
+3. Fill out the pull request template and describe *what* changed and *why*.
+4. Link any related issue (e.g. `Closes #12`).
+
+## Reporting bugs & ideas
+
+Use the [issue templates](.github/ISSUE_TEMPLATE) to file a bug report or
+suggest a feature (a new enemy, power-up or level twist). Please include steps
+to reproduce and your browser/OS for bugs.
+
+By contributing, you agree that your contributions will be licensed under the
+project's [MIT License](LICENSE).

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 DanMat
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -1,2 +1,74 @@
-# Castle
-A HTML5 game developed using akihabara game engine. The main character of the game gets lost in a castle. Use the arrow keys to evade the mummies and find his friend.
+# Castle 🏰🕯️
+
+> A top-down maze **chase & rescue** — you're lost in a haunted castle. Dodge the mummies, grab the key, rescue your friend and escort them to the exit before the timer runs out.
+
+[![Play the demo](https://img.shields.io/badge/▶_Play-Live_Demo-ffcf6b?style=for-the-badge)](https://danmat.github.io/Castle/)
+ 
+![Vanilla JS](https://img.shields.io/badge/Vanilla_JS-no_dependencies-f7df1e)
+![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)
+
+<p align="center">
+  <img src="docs/screenshot.png" alt="Castle gameplay — a hero in a top-down stone maze with chasing mummies, gems, a friend to rescue and a minimap" width="720" />
+</p>
+
+## What is it?
+
+The original Castle was a little Akihabara-engine maze game. This is a ground-up
+rebuild in **dependency-free vanilla JavaScript** on a plain canvas that keeps
+the heart of it — run through a castle, dodge the mummies, find your friend —
+and layers on a full arcade loop: **8 generated levels**, torchlight fog, keys,
+power-ups, spike traps, a **rescue-and-escort** objective and an online
+leaderboard. All art is drawn procedurally (no image assets).
+
+## How to play
+
+- 🎮 **Move** with WASD / arrow keys (or drag on touch). The **camera follows you**.
+- 👻 **Mummies, bats and guards** chase you — one touch costs a life (you have 3).
+- 🗝️ Grab the **key**, find and **rescue your friend**, then **escort them to the glowing exit** before time runs out.
+- 💎 Collect **gems** for score (chain them for a **combo**) and **⏳ hourglasses** for more time.
+- ⚡ **Power-ups**: *Freeze* stops the mummies, *Sprint* speeds you up, *Torch* widens your view.
+- ⚔️ Dodge **spike traps**, and lean on the **minimap** to navigate.
+
+## Features
+
+- 🧩 **8 escalating levels** — each a freshly generated maze (endlessly replayable).
+- 🕯️ **Torchlight / fog-of-war** on the darker levels for real "lost in a castle" tension.
+- 👥 **Enemy variety** — shambling mummies (chasers), fast bats, patrolling guards.
+- 🤝 **Rescue & escort** — your friend follows your trail once found.
+- 🏆 **Online leaderboard** (time + treasure + no-hit bonuses) with retro initials entry.
+- 🕹️ Keyboard + touch, fully responsive.
+
+## High scores
+
+The leaderboard uses your browser's **localStorage** out of the box and shares
+an online board across all of these games via a free **Supabase** project. See
+[`docs/supabase.sql`](docs/supabase.sql) for the schema and
+[`js/config.js`](js/config.js) for where the project URL + public key go — the
+board is namespaced by `gameId`, so Castle's scores are separate.
+
+## Play locally
+
+It's a static site — no build step:
+
+```bash
+git clone https://github.com/DanMat/Castle.git
+cd Castle
+python3 -m http.server 8000   # then visit http://localhost:8000
+```
+
+## How it works
+
+| File | Responsibility |
+| --- | --- |
+| `js/game.js` | Canvas engine: maze generation, camera, movement/collision, chasing-enemy pathfinding (BFS), fog, items, escort, HUD, state machine. |
+| `js/levels.js` | Pure-data level parameters (size, enemies, timer, torch radius, theme). |
+| `js/leaderboard.js` | Reusable high-score store (Supabase REST + localStorage fallback). |
+| `js/config.js` | Supabase URL/key and game id. |
+
+## Credits
+
+Rebuilt in vanilla JavaScript from the original Akihabara-engine version.
+
+## License
+
+[MIT](LICENSE) © DanMat

SECURITY.md

@@ -0,0 +1,30 @@
+# Security Policy
+
+## Supported versions
+
+This is a small, static, client-side game. The latest version on the `main`
+branch is the only supported version.
+
+## A note on the leaderboard
+
+Castle can post high scores to a shared **Supabase** backend. The Supabase
+**anon/publishable key** in `js/config.js` is *designed to be public* — the
+database is protected by row-level-security policies (see `docs/supabase.sql`).
+Publishing that key is expected and is not a vulnerability.
+
+As with any client-side leaderboard, scores can be spoofed by a determined user.
+The validation constraints in the RLS policy stop casual tampering; server-side
+game validation is intentionally out of scope for an arcade board.
+
+## Reporting a vulnerability
+
+If you discover a genuine security issue (for example a cross-site scripting
+vector in how initials or leaderboard rows are rendered, or a way to bypass the
+RLS policies), please report it privately rather than opening a public issue.
+
+- Use GitHub's [private vulnerability reporting](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability)
+  ("Report a vulnerability" under the repository's **Security** tab), **or**
+- Email the maintainer at **dannymatthew@gmail.com**.
+
+Please include a description, steps to reproduce, and the browser/version. You
+can expect an initial response within **7 days**.