wtclaude
249f2e513f
All checks were successful
PR Checks / plugin-checks (pull_request) Successful in -1m44s
The repository RunicNPC is built in (docs/runicnpc/PLAN.md §9, stage 0): - plugin/RunicNPC.cs: `// Requires: Kits` (D217), `[Info]` with the 0.0.0 placeholder the release stamps, `RunicNpc_ApiVersion()` (API 1), and `rnpc.status`, which reports the version and which hooks have fired. It spawns nothing. - plugin.toml: the API version, the framework floors it was loaded on (Oxide 2.0.7726, Carbon 2.0.259) and requires_plugins = ["Kits"]. - scripts/checkPlugin.js, adapted from Rust-Plugins': every hook listed and void unless written down; chat-command signatures; every RunicNpc_ call reachable by Call (the HumanNPC trap, PLAN.md §1.2); ApiVersion, `// Requires:` and [Info] agreeing with plugin.toml. 23 self-tests, including the real plugin and a CRLF checkout. - PR Checks on PRs into main and edge; the release workflow on main, with Rust-Plugins' release engine unchanged and an adapter that ships runicnpc-<ver>.tar.gz (runicnpc/RunicNPC.cs + manifest.json) and SHA256SUMS. No bundle dispatch until stage 4. - tools/: the rig panel scripts, with the panel and server ids moved into a git-ignored tools/rigs.json. `con.js` became `console.js`: CON is a reserved device name on Windows, and git there cannot open the file. - README, CONTRIBUTING (edge-based flow, AI disclosure, borrow-not-copy), SECURITY, the code of conduct, issue and PR templates. `feat:` so the cutover to main cuts the first release, 0.1.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
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.
|