Skip to content

Rebrand to LavaCat and enhance contribution documentation - #19

Merged
Ink-dark merged 6 commits into
mainfrom
rename/nexty-to-lavacat
Nov 14, 2026
Merged

Ink-dark merged 6 commits into
mainfrom
rename/nexty-to-lavacat

Conversation

@Ink-dark

Copy link
Copy Markdown
Member

No description provided.

…oal, replacing the inherited MusKitty branch description
crates/nexty-* -> crates/lavacat-* (package + lib ids follow: lavacat_dom ...), bin nexty -> lavacat (src/bin/lavacat.rs), UA string / window titles / wgpu labels now LavaCat. Cargo.lock packages moved to their alphabetical slot. .github workflows (-p, --bin, artifact names), tools/acceptance, AGENTS.md and about.hbs synced; docs/ left untouched as historical record.
CONTRIBUTING.md: environment, verification commands, Hard Rules digest, commit/version discipline, acceptance-asset workflow, PR steps. CODE_OF_CONDUCT.md: Contributor Covenant 2.1 (zh translation, English prevails). Issue forms: bug report (commit, layer, platform, minimal repro, spec citation) and feature request (kind, layer, proposal, alternatives, impact, acceptance criteria), blank issues disabled with links to AGENTS.md/docs/CONTRIBUTING. PR template mirrors the repo gates: feature map, ADR for new deps, version bump, fmt/clippy/test/deny, architect-run spec comparison, real-machine acceptance page registration.
Six call sites sat at the 100-column budget with the old five-letter prefix; the longer lavacat_/LavaCat names pushed them over, so rustfmt wraps the argument lists and use imports. No behaviour change, no version bump.
…overed by .gitignore

The 30 files under crates/*/.mimosa/ are agent-hook baselines that record absolute local paths and session ids; they were force-added at some point despite the .mimosa/ ignore rule. Remove them from the index only - the live state stays on disk for the tool.
@Ink-dark
Ink-dark merged commit 22bdf71 into main Nov 14, 2026
15 of 16 checks passed
@Ink-dark
Ink-dark deleted the rename/nexty-to-lavacat branch November 14, 2026 17:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant