Repository navigation
docs(contributing): adopt the org Wave issue template - #38
Merged
Merged
Conversation
Replaces ISSUE_TEMPLATE/wave-task.md with the single Kinlock issue format (including the mandatory context review that binds contributors to PRD.md, ARCHITECTURE.md and the AGENTS.md constraints before they write code), and adds the seven roadmap rows the seeded Wave backlog maps to, byte-identically across all five ROADMAP.md copies. W-05 is an org row and stays TODO here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
Adopt Kinlock's single issue format in this repo so Wave and other external contributors get scope,
evidence and a completion test they can work from, and so the roadmap rows the seeded backlog maps to
exist here before anyone claims an issue.
Changes
.github/ISSUE_TEMPLATE/wave-task.mdreplaced with the org template fromKinlock-Org/.githubPR docs: link the live testnet app; add README badges #26: Task, Context, mandatory context review, Why we need this, Scope (including the
do-not-touch list), Suggested implementation, Done means, Tests, Documentation, Verify commands,
PR rules, Tier, Related roadmap rows, Questions.
TODOrows added so this copy stays identical to canonical and to the other repo copies:M1-38,M1-39,M1-40,M1-41,M2-20,M2-21,M3-27.Last updated; §3 progress counts recomputed withroadmap-progress.M2-14, Document the list API as a checked reference: docs/API.md plus a route-parity test #35 →M2-20, Pin the amount precision boundary: what toBaseUnits refuses at the i128 and NUMERIC(39,0) limits #36 →M2-21, Verify the README on a clean machine, then fix the counts and commands that are wrong #37 →W-04.Hard rules / invariants touched
None changed. The review block exists to make §1 (docs outrank initiative), §2 (ask-first list),
§3 (hard rules) and §4 (deferred list) legible to someone who has not read them.
Tests
Docs, template and roadmap rows only — no code changed, so no build or test suite in this repo is
affected and none was run. Commands actually run, real output:
Docs / ADR
Template and
ROADMAP.md. No behaviour, API, event or constant change, so no ADR. The issue-formatreference itself lives in
Kinlock-Org/.githubdocs/wave-issue-format.md(PR #26).Roadmap
Rows added, all
TODO:M2-20,M2-21(owned here) plusM1-38,M1-39,M1-40,M1-41,M3-27mirrored so all five copies match. No row moved toDONE;W-04andW-05are org-owned and change elsewhere.Changelog entry added: yes.
Last updatedand the §3 counts refreshed.Assumptions and open questions
ROADMAP.mdcopies (this one,Kinlock-Org/.github/docs/ROADMAP.mdand the three sibling repos) soscripts/roadmap-mergeseesno divergence for them. Changelog lines differ per repo by design and union at the next merge.
W-05is anorgrow and is deliberately leftTODOhere — §12 says a cross-cutting rowchanges only in the PR that completes it (
.githubdocs: link the live testnet app; add README badges #26).roadmap-mergewill take canonical'sside, the same way it took canonical's
F-11in the reconcile run.F-18,F-19,W-04,W-05) are not re-statused here for the same reason.