chore: move project metadata to PCMStack and clarify CDB/database terminology

[mpicciolli]

Summary

Rehomes the project under the PCMStack organisation and cleans up the terminology used across the docs and the browser demo.

• Ownership / metadata: LICENSE copyright and package.json author now say PCMStack; repository points at PCMStack/converter, plus new bugs and homepage fields. README CI badge and demo footer links updated to the new repo URL.
• Terminology: adds a Terminology section to AGENTS.md pinning down CDB (the binary format, always handled as a buffer), database (the SQLite side), and save (a .cdb the game itself wrote — reserved for the reverse-engineering notes). README and the demo copy stop using "save" as a generic name for the input file and say "database" instead.
• Demo: adds a PCMStack eyebrow above the title and a note making it explicit that conversion happens entirely in the browser and no file is uploaded.
• Minor markdown table realignment in the README.

Notes

The two new demo elements (.page-header__eyebrow, .privacy-note) have no rules in samples/browser/style.css, so they currently render with default paragraph styling.

Test plan

• npm test
• Open samples/browser/index.html and check the header/privacy note render acceptably

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR rehomes the project metadata to the PCMStack organization and updates documentation/demo copy to clarify and standardize terminology around CDB vs SQLite database.

Changes:

• Updates repository/ownership metadata (README badge/links, package.json fields, LICENSE copyright line).
• Adds a Terminology section to AGENTS.md and adjusts README/demo wording to avoid calling .cdb inputs “saves”.
• Updates the browser demo header/footer and adds an in-browser privacy note.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
samples/browser/index.html	Updates demo title/subtitle, adds PCMStack eyebrow and privacy note, and repoints footer links to the new repo.
README.md	Updates CI badge URL, example filenames, and wording to align with clarified terminology; minor table formatting changes.
package.json	Updates author/repository metadata and adds bugs + homepage.
LICENSE	Updates the copyright holder string.
AGENTS.md	Adds a Terminology section defining CDB/database/save usage.

Suppressed comments (5)

samples/browser/index.html:39

• The privacy note says “Your database is never uploaded”, but the uploaded artifact is the .cdb (CDB) file. Using “CDB” / “.cdb file” here matches the terminology guidance and is more precise.

				<p class="privacy-note">
					Everything runs in your browser. Your database is never uploaded: it is
					read, converted and downloaded entirely on this machine.
				</p>

README.md:68

• These CLI examples use database.cdb / database.sqlite, but the terminology guidance says “database” refers to the SQLite side and shouldn’t be used bare for a .cdb. Consider switching to a neutral base name (e.g. input.*) throughout these examples.

# CDB → SQLite (default output: database.sqlite)
npx cdb-converter database.cdb

# SQLite → CDB (default output: database.cdb)
npx cdb-converter database.sqlite

README.md:75

• Same terminology issue as above: these examples show .cdb paths named database.*. Using input.cdb / input.sqlite (or another neutral name) avoids using “database” for the CDB file.

# Provide an explicit output path (directories are created as needed)
npx cdb-converter database.cdb data/database.sqlite

# Reconstruct PRIMARY KEY / FOREIGN KEY constraints (CDB → SQLite only)
npx cdb-converter database.cdb database.sqlite --normalize

README.md:104

• This Node example reads a .cdb file named database.cdb, but AGENTS.md defines “database” as the SQLite side and advises against using it bare for .cdb inputs. Renaming the example input/output to a neutral basename (e.g. input.*) keeps docs consistent.

// Read and convert a CDB file
const cdbBuffer = fs.readFileSync("database.cdb");
const db = cdbToSql(cdbBuffer, SQL);

README.md:160

• This reverse conversion example writes a .cdb file named database.cdb, which conflicts with the Terminology guidance that “database” should refer to the SQLite side. Using a neutral basename (e.g. input.*) avoids that ambiguity.

// Load a SQLite database and convert back to CDB
const sqliteBuffer = fs.readFileSync("database.sqlite");
const db = new SQL.Database(sqliteBuffer);

const cdbBuffer = sqlToCdb(db); // automatically compressed

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.