Offer: triage the issue backlog

[rmdes]

There are 44 open issues and 11 PRs. Over half the issues are 3+ years old, and 11 of those have no comments at all — opened, never discussed, never closed. Eleven were filed in December 2022 alone.

If it's useful, I'd like to do the legwork on that so the decisions are cheap for you:

• Testable claims — run them and report. docs: add npm install to getting started instructions #553 is an example: npm create indiekit in an empty directory reaches the wizard with no prior npm install, so the step it proposes isn't needed where it's placed. Two minutes to settle, four years open.
• Already fixed — issues resolved incidentally, still open because nobody rechecked.
• Duplicates — cross-linked.
• Stale — filed against an architecture that's since changed.

I'd produce a list with evidence, not close anything myself — what stays open is your call. Happy to start with the December 2022 batch rather than all 44.

Not urgent, and it doesn't block v1.0 — the milestone is only 9 items.

[paulrobertlloyd]

I’d dearly love to resolve/close #553! And if some of the issues are now fixed, let's get them closed. So maybe we start with the first 2 categories?