Repository navigation
Releases
@napplet/shim@0.38.1
Patch Changes
- Updated dependencies [c956b0f]
- @napplet/core@0.41.0
- @napplet/nap@0.40.0
@napplet/sdk@0.34.1
Patch Changes
- Updated dependencies [c956b0f]
- @napplet/core@0.41.0
- @napplet/nap@0.40.0
@napplet/nap@0.40.0
Minor Changes
-
c956b0f: Align intent delivery with the revised NAP-INTENT and NAP-NAVIGATION
drafts, which withdrew delivery identifiers and the nullable shell sender.IntentDeliverydropsid, andsenderis a requiredstringagain. A
shell replay to a selected instance is an ordinary delivery whosesender
is the target's own catalog identifier.NavigationReportdropsdeliveryId. A pending revisit settles on the
first accepted report above the revision the runtime recorded at dispatch,
matched by value.- The
@napplet/nap/intentbinding ignores deliveries without a non-empty
stringsender. - The conformance reference shell no longer assigns delivery IDs, and rejects
a report carryingdeliveryIdasinvalid.deliverIntentreplays with
the endpoint's own catalog identifier,retryIntentis removed, and
failNavigationDelivery(endpointId, definite?)no longer takes a delivery
ID.
Patch Changes
- Updated dependencies [c956b0f]
- @napplet/core@0.41.0
@napplet/core@0.41.0
Minor Changes
-
c956b0f: Align intent delivery with the revised NAP-INTENT and NAP-NAVIGATION
drafts, which withdrew delivery identifiers and the nullable shell sender.IntentDeliverydropsid, andsenderis a requiredstringagain. A
shell replay to a selected instance is an ordinary delivery whosesender
is the target's own catalog identifier.NavigationReportdropsdeliveryId. A pending revisit settles on the
first accepted report above the revision the runtime recorded at dispatch,
matched by value.- The
@napplet/nap/intentbinding ignores deliveries without a non-empty
stringsender. - The conformance reference shell no longer assigns delivery IDs, and rejects
a report carryingdeliveryIdasinvalid.deliverIntentreplays with
the endpoint's own catalog identifier,retryIntentis removed, and
failNavigationDelivery(endpointId, definite?)no longer takes a delivery
ID.
@napplet/conformance@0.28.0
Minor Changes
-
c956b0f: Align intent delivery with the revised NAP-INTENT and NAP-NAVIGATION
drafts, which withdrew delivery identifiers and the nullable shell sender.IntentDeliverydropsid, andsenderis a requiredstringagain. A
shell replay to a selected instance is an ordinary delivery whosesender
is the target's own catalog identifier.NavigationReportdropsdeliveryId. A pending revisit settles on the
first accepted report above the revision the runtime recorded at dispatch,
matched by value.- The
@napplet/nap/intentbinding ignores deliveries without a non-empty
stringsender. - The conformance reference shell no longer assigns delivery IDs, and rejects
a report carryingdeliveryIdasinvalid.deliverIntentreplays with
the endpoint's own catalog identifier,retryIntentis removed, and
failNavigationDelivery(endpointId, definite?)no longer takes a delivery
ID.
Patch Changes
- Updated dependencies [c956b0f]
- @napplet/core@0.41.0
@napplet/conformance-cli@0.7.1
Patch Changes
- Updated dependencies [c956b0f]
- @napplet/core@0.41.0
- @napplet/nap@0.40.0
- @napplet/conformance@0.28.0
- @napplet/shim@0.38.1
@napplet/vite-plugin@0.17.0
Minor Changes
-
6039389: Support the NAP-NAVIGATION draft with typed report/get APIs, runtime
injection, SDK and NAP subpaths, manifest requirement inference, and
endpoint-scoped reference history. The conformance runtime validates
advertised invocation parameters, preserves revision ordering, and revisits
retained entries through correlated intent deliveries. Browser and CLI
conformance runs bind navigation eligibility to the host-verified manifest.
Navigation is cataloged as exploratory, so hosts usingselectNapDomainsneed
a named opt-in.Implement the companion NAP-INTENT delivery draft:
IntentDelivery.idis now
required andsenderacceptsnullfor shell-originated requests. Runtime
integrations must assign a non-reused delivery ID within each target endpoint
lifetime, preserve it on retries, and derive sender provenance themselves.
This is a breaking pre-1.0 contract change.These interfaces follow the published drafts in napplet/naps#126 and
napplet/naps#128; they remain subject to upstream revision.
Patch Changes
- 926959f: Support the proposed NAP-CATALOG read-only discovery contract. Add
typed snapshots, catalog SDK and layered NAP exports, allowlisted runtime
injection, reference-shell discovery and envelope validation, and catalog
capability inference. Catalog queries work independently of intent dispatch
and shell readiness. See napplet/naps#95 for the
living draft. - cc27254: Add the draft NAP-SOULSEEK contract (napplet/naps#135) across types,
domain helpers, runtime injection, SDK, manifest inference, and conformance
tooling. Thesoulseekdomain exposes the fourteen request/result operations
for runtime-mediated search, peer browsing, paginated immutable snapshots,
endpoint-owned transfers, bounded base64 reads, user-mediated saving, and
release. Failures reject with the specification error code; 64-bit byte counts
travel as canonical decimal text. Accounts, peer networking, storage, content
disclosure, and saving remain owned by the host runtime. - fd715ac: Add the transfer-only draft NAP-TORRENT contract across types, domain
helpers, runtime injection, SDK, manifest inference, and conformance tooling.
Support full v1/v2/hybrid identities, bounded verified reads, metadata export,
separate file disclosure actions, cancellation, revisioned settings, and
retention/recovery schemas. Discovery, Nostr event conversion, publishing, and
comments remain outside the torrent domain. Torrent engines, consent, storage,
and network policy remain owned by the host runtime.
@napplet/shim@0.38.0
Minor Changes
-
6039389: Support the NAP-NAVIGATION draft with typed report/get APIs, runtime
injection, SDK and NAP subpaths, manifest requirement inference, and
endpoint-scoped reference history. The conformance runtime validates
advertised invocation parameters, preserves revision ordering, and revisits
retained entries through correlated intent deliveries. Browser and CLI
conformance runs bind navigation eligibility to the host-verified manifest.
Navigation is cataloged as exploratory, so hosts usingselectNapDomainsneed
a named opt-in.Implement the companion NAP-INTENT delivery draft:
IntentDelivery.idis now
required andsenderacceptsnullfor shell-originated requests. Runtime
integrations must assign a non-reused delivery ID within each target endpoint
lifetime, preserve it on retries, and derive sender provenance themselves.
This is a breaking pre-1.0 contract change.These interfaces follow the published drafts in napplet/naps#126 and
napplet/naps#128; they remain subject to upstream revision. -
926959f: Support the proposed NAP-CATALOG read-only discovery contract. Add
typed snapshots, catalog SDK and layered NAP exports, allowlisted runtime
injection, reference-shell discovery and envelope validation, and catalog
capability inference. Catalog queries work independently of intent dispatch
and shell readiness. See napplet/naps#95 for the
living draft. -
cc27254: Add the draft NAP-SOULSEEK contract (napplet/naps#135) across types,
domain helpers, runtime injection, SDK, manifest inference, and conformance
tooling. Thesoulseekdomain exposes the fourteen request/result operations
for runtime-mediated search, peer browsing, paginated immutable snapshots,
endpoint-owned transfers, bounded base64 reads, user-mediated saving, and
release. Failures reject with the specification error code; 64-bit byte counts
travel as canonical decimal text. Accounts, peer networking, storage, content
disclosure, and saving remain owned by the host runtime. -
fd715ac: Add the transfer-only draft NAP-TORRENT contract across types, domain
helpers, runtime injection, SDK, manifest inference, and conformance tooling.
Support full v1/v2/hybrid identities, bounded verified reads, metadata export,
separate file disclosure actions, cancellation, revisioned settings, and
retention/recovery schemas. Discovery, Nostr event conversion, publishing, and
comments remain outside the torrent domain. Torrent engines, consent, storage,
and network policy remain owned by the host runtime.
Patch Changes
@napplet/sdk@0.34.0
Minor Changes
-
6039389: Support the NAP-NAVIGATION draft with typed report/get APIs, runtime
injection, SDK and NAP subpaths, manifest requirement inference, and
endpoint-scoped reference history. The conformance runtime validates
advertised invocation parameters, preserves revision ordering, and revisits
retained entries through correlated intent deliveries. Browser and CLI
conformance runs bind navigation eligibility to the host-verified manifest.
Navigation is cataloged as exploratory, so hosts usingselectNapDomainsneed
a named opt-in.Implement the companion NAP-INTENT delivery draft:
IntentDelivery.idis now
required andsenderacceptsnullfor shell-originated requests. Runtime
integrations must assign a non-reused delivery ID within each target endpoint
lifetime, preserve it on retries, and derive sender provenance themselves.
This is a breaking pre-1.0 contract change.These interfaces follow the published drafts in napplet/naps#126 and
napplet/naps#128; they remain subject to upstream revision. -
926959f: Support the proposed NAP-CATALOG read-only discovery contract. Add
typed snapshots, catalog SDK and layered NAP exports, allowlisted runtime
injection, reference-shell discovery and envelope validation, and catalog
capability inference. Catalog queries work independently of intent dispatch
and shell readiness. See napplet/naps#95 for the
living draft. -
cc27254: Add the draft NAP-SOULSEEK contract (napplet/naps#135) across types,
domain helpers, runtime injection, SDK, manifest inference, and conformance
tooling. Thesoulseekdomain exposes the fourteen request/result operations
for runtime-mediated search, peer browsing, paginated immutable snapshots,
endpoint-owned transfers, bounded base64 reads, user-mediated saving, and
release. Failures reject with the specification error code; 64-bit byte counts
travel as canonical decimal text. Accounts, peer networking, storage, content
disclosure, and saving remain owned by the host runtime. -
fd715ac: Add the transfer-only draft NAP-TORRENT contract across types, domain
helpers, runtime injection, SDK, manifest inference, and conformance tooling.
Support full v1/v2/hybrid identities, bounded verified reads, metadata export,
separate file disclosure actions, cancellation, revisioned settings, and
retention/recovery schemas. Discovery, Nostr event conversion, publishing, and
comments remain outside the torrent domain. Torrent engines, consent, storage,
and network policy remain owned by the host runtime.
Patch Changes
@napplet/nap@0.39.0
Minor Changes
-
6039389: Support the NAP-NAVIGATION draft with typed report/get APIs, runtime
injection, SDK and NAP subpaths, manifest requirement inference, and
endpoint-scoped reference history. The conformance runtime validates
advertised invocation parameters, preserves revision ordering, and revisits
retained entries through correlated intent deliveries. Browser and CLI
conformance runs bind navigation eligibility to the host-verified manifest.
Navigation is cataloged as exploratory, so hosts usingselectNapDomainsneed
a named opt-in.Implement the companion NAP-INTENT delivery draft:
IntentDelivery.idis now
required andsenderacceptsnullfor shell-originated requests. Runtime
integrations must assign a non-reused delivery ID within each target endpoint
lifetime, preserve it on retries, and derive sender provenance themselves.
This is a breaking pre-1.0 contract change.These interfaces follow the published drafts in napplet/naps#126 and
napplet/naps#128; they remain subject to upstream revision. -
926959f: Support the proposed NAP-CATALOG read-only discovery contract. Add
typed snapshots, catalog SDK and layered NAP exports, allowlisted runtime
injection, reference-shell discovery and envelope validation, and catalog
capability inference. Catalog queries work independently of intent dispatch
and shell readiness. See napplet/naps#95 for the
living draft. -
cc27254: Add the draft NAP-SOULSEEK contract (napplet/naps#135) across types,
domain helpers, runtime injection, SDK, manifest inference, and conformance
tooling. Thesoulseekdomain exposes the fourteen request/result operations
for runtime-mediated search, peer browsing, paginated immutable snapshots,
endpoint-owned transfers, bounded base64 reads, user-mediated saving, and
release. Failures reject with the specification error code; 64-bit byte counts
travel as canonical decimal text. Accounts, peer networking, storage, content
disclosure, and saving remain owned by the host runtime. -
fd715ac: Add the transfer-only draft NAP-TORRENT contract across types, domain
helpers, runtime injection, SDK, manifest inference, and conformance tooling.
Support full v1/v2/hybrid identities, bounded verified reads, metadata export,
separate file disclosure actions, cancellation, revisioned settings, and
retention/recovery schemas. Discovery, Nostr event conversion, publishing, and
comments remain outside the torrent domain. Torrent engines, consent, storage,
and network policy remain owned by the host runtime.