wtclaude
26f2079cca
First commit for the UO module — the game-specific half of the Runic Gateway
website, extracted from core so that core can become game-agnostic. Phase 0 of
the module system plan (docs/website/MODULE_SYSTEM.md §2.7) calls for this repo
to get its initial commit before any module work starts.
Governance scaffolding only; no module code. The design of record settles the
API surface in Phase 1 and Phase 3 is what fills the repo, so writing module
code now would be writing against a contract that does not exist yet.
- README.md what module-uo is, the phase table, the packaging layout,
and why an operator never builds anything
- CONTRIBUTING.md planning status, the dev loop (a module is not runnable on
its own), the zero-internal-imports and one-path-segment
rules, schema fragments instead of migrations
- SECURITY.md private reporting, plus the module-specific notes: the
module boundary is not a security boundary, access control
lives in core, and the uo-link token stays write-only
- CODE_OF_CONDUCT.md, CONTRIBUTORS.md, LICENSE.md (GPL-3.0-or-later),
PR + issue templates — the same set every repo in the org carries
- .gitignore Node-shaped; client/dist/ is ignored deliberately, since it
is a release artifact built by CI, not a source artifact
CI lands next, in a PR, mirroring how the installer repo was bootstrapped: an
empty repo cannot take a pull request, but everything after it can.
Co-Authored-By: Claude <noreply@anthropic.com>
34 lines
1.1 KiB
Markdown
34 lines
1.1 KiB
Markdown
<!--
|
|
Thanks for contributing to Runic Gateway!
|
|
Please fill out the sections below and check every box before requesting review.
|
|
-->
|
|
|
|
## What & why
|
|
|
|
<!-- What does this PR change, and why? Link any related issue: "Closes #123". -->
|
|
|
|
## How it was tested
|
|
|
|
<!-- Commands you ran, manual steps, screenshots. -->
|
|
|
|
## Checklist
|
|
|
|
- [ ] I have read [CONTRIBUTING.md](CONTRIBUTING.md).
|
|
- [ ] The change builds and existing tests/checks pass locally.
|
|
- [ ] I have added or updated tests/docs where it makes sense.
|
|
- [ ] My commits are reasonably scoped with clear messages.
|
|
|
|
## AI-assisted contributions (required)
|
|
|
|
This project **requires disclosure of AI tool usage**. Please pick one:
|
|
|
|
- [ ] No AI tools were used to produce this contribution.
|
|
- [ ] AI tools were used. Tool(s): `___________`. I have reviewed and understand
|
|
every change, and take responsibility for it. AI-authored commits are
|
|
marked with a `Co-Authored-By` / `Assisted-By` trailer.
|
|
|
|
## License
|
|
|
|
- [ ] I agree that my contribution is licensed under this project's license
|
|
(**GNU GPL v3.0 or later**), and I have the right to contribute it.
|