Added matching repository metadata to each publishable workspace package so npm trusted publishing from GitHub Actions can validate the repo/package relationship consistently. This does not solve the first-publish bootstrap for a brand-new package, but it removes a documented follow-up blocker once the package exists and trusted publishing is configured.
Constraint: npm trusted publishing docs require a package repository URL that exactly matches the GitHub repository for GitHub-based publishes
Constraint: Publishable workspace metadata should stay aligned across packages in the monorepo
Rejected: Updating only daiso-product-search | would leave the other publishable workspaces inconsistent under the same release workflow
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Keep repository metadata aligned on every publishable workspace package.json when the repo moves or renames
Tested: npm run ci
Not-tested: Live npm publish from GitHub Actions
This snapshots the current repository updates as a coherent release-prep
baseline: workspace/package scaffolding, release automation docs and
workflows, refreshed skill/setup documentation, roadmap expansion, and
the README thumbnail polish.
Constraint: Node packages in this repo must use npm workspaces and Changesets for releases
Constraint: Python release automation stays scaffold-only until a real package exists
Rejected: Split the current work into multiple commits | user asked to commit the current changes together
Confidence: medium
Scope-risk: moderate
Reversibility: clean
Directive: Keep release docs, workflows, and package metadata aligned when adding future packages
Tested: npm run ci
Not-tested: GitHub Actions execution on remote after push
github-actions[bot]