Remove --provenance from npm publish

[joalves]

Summary

Drop --provenance flag — matching the working pattern from absmartly-cli-ts. The OIDC token via id-token: write + registry-url handles authentication; --provenance was causing the 404.

Test plan

• Merge and verify 0.3.0 publishes to npm

Summary by CodeRabbit

Release Notes

• Chores
  • Updated CI publishing workflow configuration.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

Walkthrough

The publish workflow configuration in .github/workflows/publish.yml has been modified to remove the --provenance flag from the npm publish command. The --access public flag remains unchanged. This represents a single-line modification to the CI/CD workflow without alterations to other workflow logic, steps, conditions, or environment configuration.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A flag removed with gentle care,
No provenance cluttering the air,
The publish command runs clean and spry,
One small edit caught the eye!
A tiny change, yet swift and true,
The workflow skips along anew. 🌟

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely describes the primary change: removing the --provenance flag from npm publish, which directly matches the main modification in the pull request.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/remove-provenance

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}