@seedprotocol/publish 0.7.4 → 0.7.5-next.850.g9ab585b

package/CHANGELOG.md

@@ -6,6 +6,95 @@ All notable changes to this project will be documented in this file.
 
 ### Breaking
 
+- **Number properties register `string <name>` EAS schemas instead of `uint8 <name>`** (ADR 0010, through `@seedprotocol/sdk`'s data types). The first publish of a Number property after upgrading registers its new schema.
+- **Direct EAS needs a wallet that says it is an EOA.** Without `useDirectEas`, a publisher with no contract attests straight to EAS only when its `PublishWallet` has `kind: 'eoa'` and signs as the publisher. `fromEip1193Provider` and `fromEthersWallet` set `kind: 'eoa'`; `fromThirdwebAccount(account, { kind })` takes it, and `ConnectButton` and the managed-account helpers set it. A wallet without a kind uses its registered session's kind when the signer is the same, and is refused otherwise. To migrate a hand-built wallet, set `kind`, or set `useDirectEas` to attest directly anyway. (Before, admins were guessed through factory reads, which let an undeployed thirdweb smart wallet through.)
+- **`initPublish` requires `uploadApiBaseUrl`** when the operator pays for storage (the default), and checks that it is an http(s) URL or a path from the page's origin.
+- **`PublishManager.query(seedLocalId)` only reads.** It returns the publish's current snapshot. It used to stop the publish.
+- **`ensureWalletThenPublish` / `ensureSmartWalletThenPublish`** wait for the publish to spawn (not to finish). `'started'` carries the actor as `publish`; a new `'already_publishing'` outcome means nothing started. `started` is deprecated and already resolved.
+
+### Changed
+
+- `useCanPublishItem` is `false` until its check finishes, and checks again when owned addresses change.
+- `ConnectButton` stops running publishes only when another wallet takes over, not on every wallet sync.
+- `pollForConfirmation` fails after 30 min, or after 12 failed status requests in a row.
+- Cost estimates: an Arweave L1 upload is charged for at least 256 KiB, a bundle once, and Turbo uploads up to 100 KiB are free (`arweave.chargedBytes`). Gas on a testnet is priced at $0 (`evm.testnet`).
+- Deprecated: `useLocalWalletAccount` (always `null`), and the `gatewayTransport` and `modularAccountModuleData` config fields (not read).
+
+## 0.7.4 (2026-10-15)
+
+### Commits
+
+#### Features
+
+- authorizePublish approves a publish before it spends (165481fa)
+- users can pay for storage with Turbo credits (7d22873e)
+- payment config and one resolution of who pays (f9fd4fe0)
+
+#### Fixes
+
+- ensureEasSchemas looks schemas up under the published name (1da9dc94)
+- sdk, react: one easName for every name that reaches EAS (eec5ded5)
+- disconnecting a wallet stops treating it as owned (d12c64c1)
+- sdk: addresses saved by init are announced; connecting keeps watched addresses (a8029bcc)
+- load the undeployed-account check only on the direct-EAS branch (b98ea731)
+- refuse direct EAS for an undeployed smart account (ef06cf94)
+- direct-EAS publish records each seed as it is attested (6819bb97)
+- domain ownership attests what was proven and honours expiry (8c5ef8e3)
+- revoke from the attester and skip already-revoked uids (220dcb0e)
+- keep arweaveJwk and dataItemSigner out of saved publish snapshots (01d2d008)
+- estimatePublishCost reports Arweave storage as not user-paid (0039b18d)
+- estimatePublishCost reports who pays gas from the real sender (4655d738)
+
+## 0.7.3 (2026-10-14)
+
+### Commits
+
+#### Features
+
+- register publishItem as the executor behind item.publish() (79e461ec)
+
+#### Other
+
+- item.publish() needs @seedprotocol/publish (b90bc321)
+- use the SDK's getPublishUploadData (fa8f2f84)
+
+## 0.7.1 (2026-10-10)
+
+### Commits
+
+#### Features
+
+- sdk: seed:property/<name> placeholders in Html resolve to the property's upload (ef4c28e9)
+
+#### Fixes
+
+- direct-to-EAS publish attests every list member's seed uid (9ff27038)
+- sdk: publish the full graph of related drafts (c115dc30)
+
+## 0.7.0 (2026-10-08)
+
+### Commits
+
+#### Features
+
+- sdk: elect a leader tab for automatic EAS sync and the L1 worker (1d828074)
+- sdk: record version revocations in versions.revoked_at (09649128)
+
+#### Fixes
+
+- resume each in-progress publish in one tab only (8d2c0d18)
+- sdk: co-publish images embedded in related drafts' Html (0c47942e)
+- direct-to-EAS publish records every request's own seed (0c4732ac)
+- record every request of a one-transaction publish (a1875916)
+- match each multiPublish request to its own receipt events (7505a50d)
+- sdk: a patch publish's existing version uid is not recorded again (ecce0332)
+- sdk: publishing a reference to an unpublished item fails (3c05c13c)
+- sdk: propagate property revocations and replacements to stored metadata (13ddb58d)
+
+## 0.6.10 (2026-10-04)
+
+### Breaking
+
 - **`waitForPublishReceipt` throws on a reverted transaction** (`PublishTransactionRevertedError`, with `transactionHash` and `receipt`). It used to return the reverted receipt, so callers treated a revert as success. Functions that return its receipt (`attestPublishAuthorization`, `revokePublishAuthorization`, domain ownership and publishedBy attest/revoke) now throw instead.
 - **`ensureExecutorModuleInstalled` no longer calls `installModule` on thirdweb ModularCore accounts.** That path could never work: ModularCore installs modules by `delegatecall`, and the Seed executor is an ERC-7579 module without `getModuleConfig`. Accounts without the `SeedExecutorRouterExtension` are skipped, and `assertExecutorModuleReadyForAccount` reports why the executor can't act for them. `ensureExecutorModuleInstalled` now returns `{ status: 'skipped' | 'already-installed' }` or `{ status: 'installed', eas, transactionHash }`. `PublishConfig.modularAccountModuleData` is unused.
 
@@ -15,20 +104,116 @@ All notable changes to this project will be documented in this file.
 - **`seedPaymaster(client, chain, bundlerUrl?)`** is exported from `@seedprotocol/publish/thirdweb` for smart wallets the SDK doesn't build, such as a server's `smartWallet()` with an automation session key: pass it as `overrides.paymaster` when `sponsorGas` is on.
 - **Executor install race in `enrollPublishAutomation`:** turning on automation could fail with "The Seed executor is not installed for this ManagedAccount" right after a successful `installSeedExecutor`, because the follow-up `isInitialized` read hit a load-balanced RPC node that hadn't seen the block yet. The install is now confirmed from the receipt's `SeedExecutorInstalled` and `ModuleInitialized` logs, and the readiness check uses the EAS from that event instead of re-reading. When the executor was already installed, the `isInitialized` read is retried briefly. `ensureAutomationSessionKey` retries the `isActiveSigner` read after `addSessionKey` for the same reason.
 - **Failed executor installs report why:** an install whose receipt lacks the install events (a reverted transaction, or a sponsored EIP-7702 relayer transaction that succeeded while the inner call reverted) throws `EXECUTOR_MODULE_NOT_INSTALLED` with the decoded revert reason, instead of a misleading "not installed" from the readiness check.
+
+### Added
+
+- **`readFactorySeedExecutor(factory?)`:** the executor and EAS that a ManagedAccount factory's `SeedExecutorRouterExtension` pins, or `null` when it routes none. Compare it with `modularAccountModuleContract` at startup instead of finding a stale address at the first publish or enroll.
+- **`assertExecutorModuleReadyForAccount(address, { installedEas, readAttempts })`:** pass the EAS confirmed from an install receipt to skip the read, or retry a not-initialized read.
+
+### Commits
+
+#### Breaking
+
+- confirm executor installs from the receipt, not a lagging read (e111c5d0)
+
+#### Other
+
+- Fixing gas estimation. v0.6.10 (d5b161a1)
+
+## 0.6.9 (2026-10-03)
+
+### Commits
+
+#### Breaking
+
+- encode multiPublish with publishIndex for SeedProtocolExtension (69318de1)
+
+#### Other
+
+- one multiPublish struct for the extension and the executor (ab765b75)
+
+## 0.6.8 (2026-10-03)
+
+### Fixed
+
 - **List-of-relation EAS names:** a list relation such as `staff` (List → Identity) was attested as `bytes32[] staff` or `bytes32[] staff_identity_ids` depending on whether the model was loaded before the item. `getPublishPayload` and `ensureEasSchemasForItem` now derive the name from the property definition with `listRelationEasPropertyName` (exported from `@seedprotocol/sdk`) and ignore a cached `schemaUid` for list relations. `ensureEasSchemasForItem` refuses to register a list-relation schema that doesn't end in `_ids`. Locally, `createMetadata` writes list-relation rows under the storage name (`staffIdentityIds`), and an `ItemProperty` that receives its schema after construction moves to the storage name while `propertyName` stays `staff`. Already-published data (`author_identity_ids` and the like) is unchanged.
 - **Missing property schemas fail publish validation:** when a property's EAS schema can't be found, `getPublishPayload` now reports `publish_schema_not_found` instead of attesting the value under the Version schema. Call `ensureEasSchemasForItem` first, as the publish flow already does.
 - **`parseEasRelationPropertyName`** (`@seedprotocol/query`) pluralizes list names with `pluralize`: `staff_identity_ids` → `staff` (was `staffs`). Single relations return the singular (`cover_image_id` → `cover`).
 - **Failed UserOps on the permissionless / EIP-7702 sender:** a UserOp that failed inside a successful bundle transaction was returned as a success, so publish went on with no attestations. It now throws with the decoded revert reason.
 - **Readable publish failures:** every publish route now simulates `multiPublish` from the sending account before sending, and a call that would revert throws `PUBLISH_PREFLIGHT_FAILED` with the decoded Seed, EAS or `Error(string)` reason (automation keeps `AUTOMATION_PREFLIGHT_FAILED`). Outside automation, a simulation that can't run doesn't block the send. thirdweb's bare `UserOp failed at txHash: 0x…` (usually out of gas) and its undecodable custom-error message are rewritten to say what happened, as `ManagedAccountPublishError` with code `USEROP_FAILED_NO_REASON` (no revert reason; usually out of gas) or `USEROP_REVERTED`, keeping the original as `underlyingCause`. Failed UserOps on the permissionless sender use the same codes.
-- **Publish automation on legacy ManagedAccounts:** `enrollPublishAutomation` no longer fails when the account is an ERC-7504 Router (`Router: function does not exist`) instead of ModularCore. Those accounts cannot `installModule`; enroll adds the module-only session key and attests the sidecar. ModularCore accounts still require the executor module to be installed.
 - **EAS schema lookup:** `ensureEasSchemasForItem` normalizes property data types (`html` → `Html`) before choosing the on-chain schema, so an existing `bytes32 html` schema is reused instead of registering `string html`. `normalizeDataType` is exported from `@seedprotocol/sdk`.
 - **Automation schema registration:** session keys no longer send SchemaRegistry or EAS UserOps when a schema is missing. Publish fails first with `schema "…" is not registered; automation keys can't register schemas`. Register once with the owner wallet via `ensureEasSchemasForItem`.
+
+### Commits
+
+#### Features
+
+- error codes for failed UserOps (72211c67)
+- twin robustness and a twin.json config helper (b72399a9)
+- local twin support and the contract rollout's client changes (65bbde80)
+- verify the publish chain before writing; hold EAS sync until the chain is known (5f4fc0ee)
+- sdk: record the EAS chain in the local DB and refuse cross-chain writes (7d8af9d5)
+- sdk: read EAS from the configured chain and register base schemas on new chains (91e0290e)
+- make the publish chain and EAS addresses configurable (811b8fc5)
+
+#### Fixes
+
+- attest list relations under one EAS name (55d6cbe2)
+- readable UserOp failures and a pre-send check on every route (06f8674d)
+- rollout and twin follow-ups from protocol review (415c9c1b)
+- check executor module readiness before automation publish and revoke (4e8a4f8a)
+- treat relations to published seed uids as already published (8133d761)
+- normalize EAS schema types and refuse automation registration (b68fef38)
+
+#### Other
+
+- Lots of bug fixes (a3a7f146)
+
+## 0.6.7 (2026-10-01)
+
+_Also covers 0.6.4, 0.6.5, 0.6.6, published from commits in this range._
+
+### Fixed
+
+- **Publish automation on legacy ManagedAccounts:** `enrollPublishAutomation` no longer fails when the account is an ERC-7504 Router (`Router: function does not exist`) instead of ModularCore. Those accounts cannot `installModule`; enroll adds the module-only session key and attests the sidecar. ModularCore accounts still require the executor module to be installed.
 - **First-time modular publish:** `isAutomationSessionActive` returns `false` when the ManagedAccount has no bytecode instead of throwing `MODULAR_SIGNER_ACTIVATION_FAILED` on viem `0x` / “not a contract”. Interactive first publish can reach `runModularExecutorPublishPrep` / `autoDeployManagedAccount`. Deployed-account RPC or `isActiveSigner` read failures still throw so unattended automation does not fall through to in-app bootstrap.
 
+### Commits
+
+#### Features
+
+- add PublishedBy batch sidecar attest/revoke/query APIs (14233083)
+
+#### Fixes
+
+- support Node server publishes without a browser Thirdweb client (7ef2fe66)
+- import listCreatedAttestationPairsFromReceipt for PublishedBy batch (4da2fc80)
+
+#### Other
+
+- Final edits (687d320b)
+- Build fixes (15ab8cdc)
+- Fixing Vite plugin bugs (59fad217)
+- Fix first-publish failing when the ManagedAccount is still undeployed. (84a921d6)
+
+## 0.6.3 (2026-09-25)
+
+_Also covers 0.6.1, 0.6.2, published from commits in this range._
+
+### Commits
+
+#### Other
+
+- Fixing item ownership bugs/gaps (2539c65c)
+- Adding publish cost estimator tooling (6d2f170c)
+- Fixing bug so uid doesn't depend on CreatedAttestation (5e64192b)
+
+## 0.5.3 (2026-09-17)
+
+_Also covers 0.5.2, published from commits in this range._
+
 ### Added
 
-- **`readFactorySeedExecutor(factory?)`:** the executor and EAS that a ManagedAccount factory's `SeedExecutorRouterExtension` pins, or `null` when it routes none. Compare it with `modularAccountModuleContract` at startup instead of finding a stale address at the first publish or enroll.
-- **`assertExecutorModuleReadyForAccount(address, { installedEas, readAttempts })`:** pass the EAS confirmed from an install receipt to skip the read, or retry a not-initialized read.
 - **Publish automation grants:** ManagedAccount-hosted session keys (executor-module-only `approvedTargets`), `seedprotocol.publishAuthorization` sidecar, `enrollPublishAutomation` / `revokePublishAutomation`, and `assertStorageBoundToIdentity`. See `docs/PUBLISH_AUTOMATION.md`.
 - **`prepareEasMultiRevoke`:** When `modularAccountModuleContract` is set, routes `multiRevoke` to the executor module so automation session keys can revoke as the ManagedAccount.
 - **`resolveRevokeAccount` / `revokeAttestations`:** No longer hard-block ManagedAccount attesters; legacy module-attester path attempts ManagedAccount + executor revoke when configured.
@@ -40,6 +225,41 @@ All notable changes to this project will be documented in this file.
 - **Domain ownership tooling:** `createDomainOwnershipChallenge`, multi-resolver DNS TXT verify, RDAP snapshot via `rdapper`, `ensureDomainOwnershipSchema` / `attestDomainOwnership` / `revokeDomainOwnership`, `verifyAndAttestDomainOwnership`, and `assessDomainOwnershipLive`. See `docs/DOMAIN_OWNERSHIP.md`.
 - Dependency: `@seedprotocol/eas`, `rdapper`.
 
+### Commits
+
+#### Features
+
+- route automation session keys through the executor (5894cbc2)
+- add ManagedAccount publish automation enrollment (db6d752f)
+
+#### Other
+
+- Add domain ownership DNS challenge, RDAP snapshot, and EAS sidecar tooling. (c51a1226)
+
+## 0.5.1 (2026-08-29)
+
+### Commits
+
+#### Features
+
+- add permissionless EIP-7702 sender for gasless publish (1c907e64)
+- add EIP-1193 PublishWallet and useSeedWallet (fb5dfdab)
+- make Thirdweb an optional peer behind /thirdweb (2bc918dc)
+- resolve chain and RPC from PublishConfig (23b24b66)
+
+#### Fixes
+
+- sync in-app auth tokens for managed wallet connect (4e1caadf)
+- sdk: guard BaseDb readiness before platform classes init (425883c3)
+
+#### Other
+
+- replace setPlatformClass with instance + static facade (0bca44b7)
+- Fixing imports/exports (3869c666)
+- document EIP-1193, permissionless, and Thirdweb recipes (221e007f)
+- split SeedSigner and SeedTxSender (11c0d8e1)
+- Decouple publish contract/tx layer via SeedSigner and viem. (537c0e15)
+
 ## 0.5.0
 
 ### Breaking

package/README.md

@@ -1,12 +1,24 @@
 # @seedprotocol/publish
 
-Publish UI components and helpers for Seed Protocol.
+[![npm](https://img.shields.io/npm/v/@seedprotocol/publish.svg)](https://www.npmjs.com/package/@seedprotocol/publish)
+
+Publish UI components and helpers for [Seed Protocol](https://seedprotocol.io): upload item content to Arweave and attest it on EAS from [`@seedprotocol/sdk`](https://www.npmjs.com/package/@seedprotocol/sdk) items, with React providers/hooks and optional Thirdweb wallets.
 
 The publish flow (ConnectButton, etc.) runs `ensureEasSchemasForItem` before `getPublishPayload`, which registers EAS schemas and adds naming attestations so EASSCAN displays them. If you build a custom publish flow that calls `item.getPublishPayload()` directly, you must run schema setup first or use this package's flow.
 
-**`item.publish()` and `item.unpublish()` need this package.** `initPublish()` (or `<PublishProvider config>`) registers the executors behind them: `publishItem` for `item.publish()` and the revocation executor for `item.unpublish()`. Until it runs, both throw. `item.publish(options)` passes `options` through as `CreatePublishOptions`, uses the wallet registered with `useSeedWallet().connect` or `setPublishWallet`, and resolves when the publish has finished (it rejects if it fails). See [docs/ATTESTATION_REVOCATION.md](../../docs/ATTESTATION_REVOCATION.md) for permanence and UX guidance.
+**`item.publish()` and `item.unpublish()` need this package.** `initPublish()` (or `<PublishProvider config>`) registers the executors behind them: `publishItem` for `item.publish()` and the revocation executor for `item.unpublish()`. Until it runs, both throw. `item.publish(options)` passes `options` through as `CreatePublishOptions`, uses the wallet registered with `useSeedWallet().connect` or `setPublishWallet`, and resolves when the publish has finished (it rejects if it fails). See [docs/ATTESTATION_REVOCATION.md](https://github.com/JournoLabs/seed-protocol-sdk/blob/main/docs/ATTESTATION_REVOCATION.md) for permanence and UX guidance.
+
+**Badges / on-chain vs pending:** use `@seedprotocol/sdk` `getSeedPublishState` for “any on-chain anchor for this seed”, `getPublishPendingDiff` for per-property heads missing attestation UIDs, and `Item.all` (or `useItems` from `@seedprotocol/react`) with `includeEas` (compare `publishedVersionUid` vs `latestVersionUid`) for list rows. When a publish run finishes, observe `usePublishProcess(seedLocalId)` or the `publishProcesses` table instead of ad hoc window events.
+
+## Installation
 
-**Badges / on-chain vs pending:** use `@seedprotocol/sdk` `getSeedPublishState` for “any on-chain anchor for this seed”, `getPublishPendingDiff` for per-property heads missing attestation UIDs, and `getItemsData` (`includeEas`, `publishedVersionUid` vs `latestVersionUid`) for list rows. When a publish run finishes, observe `usePublishProcess(seedLocalId)` or the `publishProcesses` table instead of ad hoc window events.
+```bash
+npm install @seedprotocol/publish @seedprotocol/sdk @seedprotocol/react react react-dom @tanstack/react-query
+# Optional, only for @seedprotocol/publish/thirdweb (ConnectButton, in-app / managed wallets):
+npm install thirdweb
+```
+
+Peer dependencies: `@seedprotocol/sdk` and `@seedprotocol/react` (the same version as this package; all Seed Protocol packages are released together), `react` / `react-dom` 18 or 19, `@tanstack/react-query` 5, and optionally `thirdweb` 5. The SDK is a peer so your app and this package share one SDK instance (one client, one local database).
 
 ## Setup
 
@@ -34,6 +46,9 @@ initPublish({
   rpcUrl: import.meta.env.VITE_RPC_URL,
   chain: optimismSepolia,
   accountMode: 'eoa',
+  // Files (images, Html, ...) go to Arweave as data items the wallet signs. Without this, uploads
+  // take the L1 path, which needs an Arweave key: arweaveJwk or signArweaveTransactions.
+  useArweaveBundler: true,
 })
 
 function Connect() {
@@ -59,7 +74,9 @@ function App() {
 // Later, once the wallet is connected:
 // await item.publish()   // resolves when uploads and attestations are done
 // or, to start without waiting:
-// await ensureWalletThenPublish(item, { dataItemSigner: /* from useSeedWallet().signer */ })
+// const result = await ensureWalletThenPublish(item)  // signs data items with the wallet
+// if (result.outcome === 'started') watch(result.publish)   // the publish actor
+// if (result.outcome === 'already_publishing') ...          // this item is publishing already
 ```
 
 ### Recipe 2: EIP-1193 + permissionless EIP-7702 (gasless, no Thirdweb)
@@ -238,7 +255,7 @@ Twin quirks the SDK handles: automation pre-flight simulations retry with a bala
 
 When using your own gateway with an Arweave bundler, you can enable instant uploads instead of the default reimbursement + chunk upload flow. **This is experimental and not yet validated for production.**
 
-**Memory:** Large publishes hold signed DataItems and a single packed batch body in memory briefly. Electron and other Chromium renderers often cap near ~4 GB JS heap. See [docs/PUBLISH_MEMORY.md](../../docs/PUBLISH_MEMORY.md) for scaling, `publishMode`, and path differences (`signDataItems` vs `dataItemSigner`).
+**Memory:** Large publishes hold signed DataItems and a single packed batch body in memory briefly. Electron and other Chromium renderers often cap near ~4 GB JS heap. See [docs/PUBLISH_MEMORY.md](https://github.com/JournoLabs/seed-protocol-sdk/blob/main/docs/PUBLISH_MEMORY.md) for scaling, `publishMode`, and path differences (`signDataItems` vs `dataItemSigner`).
 
 Set `useArweaveBundler: true`. The bundler uses the same `uploadApiBaseUrl` (e.g. `${uploadApiBaseUrl}/upload/batch`).
 
@@ -273,7 +290,7 @@ PublishManager.createPublish(item, address, account, {
 
 You can also provide `signDataItems` or `dataItemSigner` in the PublishProvider config as a fallback when the signer is available at startup.
 
-**Html properties with embedded `data:image/...;base64,...` (materialization):** When `useArweaveBundler: true`, the publish machine runs the same two-phase flow as L1: phase 1 uploads non-deferred payloads (including materialized Image DataItems), rewrites Html files on disk with Arweave URLs, then phase 2 builds and uploads Html-only DataItems. **`signDataItems` is invoked twice per publish** in that scenario (once per phase)—implementations should sign/upload the `uploads` array they receive each time. The in-process **`dataItemSigner`** path performs two HTTP batch uploads to your bundler API. Per-property `htmlEmbeddedDataUriPolicy: 'preserve'` skips materialization and keeps a single phase, unless the Html has `seed:property/<name>` placeholders (see docs/PUBLISHING.md), which always take the two-phase path.
+**Html properties with embedded `data:image/...;base64,...` (materialization):** When `useArweaveBundler: true`, the publish machine runs the same two-phase flow as L1: phase 1 uploads non-deferred payloads (including materialized Image DataItems), rewrites Html files on disk with Arweave URLs, then phase 2 builds and uploads Html-only DataItems. **`signDataItems` is invoked twice per publish** in that scenario (once per phase)—implementations should sign/upload the `uploads` array they receive each time. The in-process **`dataItemSigner`** path performs two HTTP batch uploads to your bundler API. Per-property `htmlEmbeddedDataUriPolicy: 'preserve'` skips materialization and keeps a single phase, unless the Html has `seed:property/<name>` placeholders (see [docs/PUBLISHING.md](https://github.com/JournoLabs/seed-protocol-sdk/blob/main/docs/PUBLISHING.md)), which always take the two-phase path.
 
 ### Arweave upload tags
 
@@ -311,7 +328,7 @@ await deletePublishProcessById(runId) // numeric row id from `records`
 
 ### Publish automation (ManagedAccount grants)
 
-Apps can enroll a server-held session key to publish/revoke on a user’s ManagedAccount without taking the user’s root key. Requires `modularAccountModuleContract` (executor-module-only `approvedTargets`). See [docs/PUBLISH_AUTOMATION.md](../../docs/PUBLISH_AUTOMATION.md).
+Apps can enroll a server-held session key to publish/revoke on a user’s ManagedAccount without taking the user’s root key. Requires `modularAccountModuleContract` (executor-module-only `approvedTargets`). See [docs/PUBLISH_AUTOMATION.md](https://github.com/JournoLabs/seed-protocol-sdk/blob/main/docs/PUBLISH_AUTOMATION.md).
 
 APIs live on `@seedprotocol/publish` (sidecar attest/revoke) and `@seedprotocol/publish/thirdweb` (`enrollPublishAutomation`, `revokePublishAutomation`, session-key helpers, `assertStorageBoundToIdentity`).
 
@@ -331,7 +348,7 @@ With **`useModularExecutor`**, two Thirdweb in-app wallets share one login:
 
 **Session keys** may only target the executor (`approvedTargetsForAutomationPublish`). `ensureManagedSignerSessionKey` and `defaultApprovedTargetsForModularPublish` are deprecated: interactive publishing needs no session key, and both now grant the executor only, never the account (which would allow any self-call) or EAS.
 
-**Automation** session keys publish through the executor only (see [PUBLISH_AUTOMATION.md](../../docs/PUBLISH_AUTOMATION.md)) and cannot revoke. **Revocation** is owner-only: `revokeAttestations` sends `multiRevoke` to EAS from the publishing account.
+**Automation** session keys publish through the executor only (see [PUBLISH_AUTOMATION.md](https://github.com/JournoLabs/seed-protocol-sdk/blob/main/docs/PUBLISH_AUTOMATION.md)) and cannot revoke. **Revocation** is owner-only: `revokeAttestations` sends `multiRevoke` to EAS from the publishing account.
 
 **Routing:** `multiPublish` calldata uses the ABI generated from the reference deployment `MULTI_PUBLISH_ABI_REFERENCE_ADDRESS_OP_SEPOLIA` (`0xcd8c…`). The transaction `to` is the managed account for interactive publish, or the executor module for automation keys. Non-modular publish targets the deployed publisher contract. **EOAs** (no contract at `address`) never use `multiPublish`; they attest on EAS directly (`createAttestationsDirectToEas`). Set **`useDirectEas: true`** to force that path.
 
@@ -341,7 +358,13 @@ With **`useModularExecutor`**, two Thirdweb in-app wallets share one login:
 
 ## Development
 
+From a checkout of the monorepo:
+
 ```bash
 bun install
 bun run build
 ```
+
+## License
+
+MIT