Skip to content

chore(publish): publish scoped packages publicly (access: public) - #11

Merged
kreneskyp merged 1 commit into
mainfrom
chore/publish-access-public
Jun 27, 2026
Merged

chore(publish): publish scoped packages publicly (access: public)#11
kreneskyp merged 1 commit into
mainfrom
chore/publish-access-public

Conversation

@kreneskyp

Copy link
Copy Markdown
Contributor

Scoped @agent-ix/* packages default to restricted on npmjs (402 Payment Required without a private plan). Add publishConfig.access=public to the three published packages.

🤖 Generated with Claude Code

Scoped @agent-ix/* packages default to restricted on npmjs (402 Payment
Required without a private plan). Add publishConfig.access=public so the
three published packages publish publicly.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@kreneskyp
kreneskyp requested a review from a team as a code owner June 27, 2026 16:31
@kreneskyp
kreneskyp merged commit dcc911a into main Jun 27, 2026
3 checks passed
@kreneskyp
kreneskyp deleted the chore/publish-access-public branch June 27, 2026 16:32
kreneskyp pushed a commit that referenced this pull request Aug 7, 2026
spec-artifacts-iso#11. These documents wrote their criteria as a single
sentence in which the author had already enumerated them with explicit
`when` connectors:

  This need is satisfied when A, when B, and when C.
  Satisfaction is judged by D.

The lead-in is dropped, the sentence is split on the author own connectors,
and each clause becomes one row with its wording preserved. The trailing
"Satisfaction is judged by ..." sentence is kept below the table, since it
describes how satisfaction is judged overall and the `Validation` column
now records that per row.

The converter refuses rather than guesses: it requires the "satisfied when"
formula, at least two connector-separated clauses, no sentence boundary
inside a clause, and no clause short enough to suggest a mid-phrase split.
Anything refused is left for a human, so a paragraph that merely reads like
a list is never silently divided.

Only the `Validation` method is new, derived from what each criterion
describes. Demonstration dominates, as #11 predicts for stakeholder
requirements.

Every StR document in this repo validates clean against spec-artifacts-iso.

Refs agent-ix/spec-artifacts-iso#11

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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