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>
42 lines
765 B
Markdown
42 lines
765 B
Markdown
---
|
|
name: Bug report
|
|
about: Report something that is broken or behaving unexpectedly
|
|
title: "[bug] "
|
|
labels:
|
|
- bug
|
|
---
|
|
|
|
## Summary
|
|
|
|
<!-- A clear, concise description of the bug. -->
|
|
|
|
## Steps to reproduce
|
|
|
|
1.
|
|
2.
|
|
3.
|
|
|
|
## Expected behavior
|
|
|
|
<!-- What you expected to happen. -->
|
|
|
|
## Actual behavior
|
|
|
|
<!-- What actually happened. Include exact error messages and logs if you have them. -->
|
|
|
|
## Environment
|
|
|
|
- Component / repo:
|
|
- Version or commit:
|
|
- OS / runtime (Node, Rust, ServUO, browser…):
|
|
- Deployment (Docker Compose, local dev, bare metal…):
|
|
|
|
## Additional context
|
|
|
|
<!-- Screenshots, config (with secrets redacted), anything else that helps. -->
|
|
|
|
<!--
|
|
Security issue? Do NOT file it here. See SECURITY.md and email
|
|
whitlocktech@gmail.com instead.
|
|
-->
|