@hachej/boring-files 0.3.1 → 0.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -62,7 +62,7 @@ Transport errors, mismatched or oversized acknowledgements and aborted observati
|
|
|
62
62
|
|
|
63
63
|
Revocation suppresses disclosure until the handler constructs its response; already delivered bytes cannot be retracted. Aborting observation does not prove provider termination, rollback or an atomic revocation fence. Provider exceptions and response serialization failures may follow a commit, so the client retains uncertainty. The workspace provider's declared guarantees remain unchanged.
|
|
64
64
|
|
|
65
|
-
Run `node
|
|
65
|
+
Run `node fixtures/resource-transport.mjs` for a fictional exact-save and lookup journey through real Request/Response objects. Public-output tests also compose a native ToolTask and lost-acknowledgement Markdown reconciliation. The isolated document consumer exercises this adapter with strict types and a browser bundle without Pi, agent or React installed. These checks do not qualify deployed HTTP, browser identity policy or remote provider lifecycle.
|
|
66
66
|
|
|
67
67
|
`@hachej/boring-files/text` supplies the shared pure `applyTextEdits` transform and input parser. Edits run in order, require unique nonempty exact matches and preserve untouched whitespace. A failed edit refuses the whole transformation. It performs no I/O and grants no permission.
|
|
68
68
|
|
|
@@ -89,14 +89,14 @@ SQLite reads and receipt lookups of the SQLite workspace backend use deferred re
|
|
|
89
89
|
|
|
90
90
|
The SQLite resource store of `@hachej/boring-files/sqlite` (`openSqliteResources`, `SqliteResourceProvider` and its option types) is
|
|
91
91
|
removed. Its documents become files of a workspace; `SqliteConnection` and `openNodeConnection` stay in `@hachej/boring-files/sqlite`.
|
|
92
|
-
A host that kept one store with rows per scope (the
|
|
92
|
+
A host that kept one store with rows per scope (the current-hub fixture here) opens one SQLite-backed workspace per
|
|
93
93
|
scope in the same database:
|
|
94
94
|
|
|
95
95
|
| Old call | New call |
|
|
96
96
|
| --- | --- |
|
|
97
97
|
| `openSqliteResources({ filename, providerId, authorize })` | `connection = openNodeConnection(filename)`, `journal = createWorkspaceJournal(connection)`, then per scope `fs = openSqliteFileSystem({ connection, workspace: scopeId, cwd: '/workspace' })` and `createWorkspaceProvider({ identity: { providerId, instanceId: scopeId, incarnation: fs.incarnation, viewId: 'published' }, fs, journal })` |
|
|
98
98
|
| `openSqliteResources({ connection, ... })` (a Durable Object) | the same calls with `durableObjectSqliteConnection(ctx.storage)` from `@hachej/boring-files/sqlite-durable-object` |
|
|
99
|
-
| `authorize(action, target, access)` inside the store | the host checks its policy before calling the workspace's provider; [`
|
|
99
|
+
| `authorize(action, target, access)` inside the store | the host checks its policy before calling the workspace's provider; [`shared/sqlite-workspaces.mjs`](../../shared/sqlite-workspaces.mjs) shows one way (a refused write whose operation committed and a refused lookup read `unknown`) |
|
|
100
100
|
| `provider.close()` | `connection.close()` by the connection's owner |
|
|
101
101
|
| a `delete` change | the workspace's own file tools (`fs.remove`, Pi's `bash`); publication refuses deletes |
|
|
102
102
|
| revisions were random ids; saving the same bytes made a new revision | revisions are Git blob ids: the same bytes keep their revision, and `before` equal to `after` is a valid committed change |
|