arcane-os 0.51.1 → 0.52.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.
@@ -195,10 +195,20 @@ npm run run
195
195
 
196
196
  The explicit \`import-map\` command refreshes
197
197
  \`${appPrefix}modules/arcane.importmap.json\` and the managed inline browser
198
- import map in every directly navigable descriptor-admitted \`.html\`/\`.htm\`
199
- document. HTML component fragments remain package files but do not receive a
200
- document-level base or managed import map.
201
- Development, package, and build refresh that shared inventory when the selected operation needs it.
198
+ import map in each selected application \`.html\`/\`.htm\` document.
199
+ Optional \`package.documents\` in \`arcane-app.json\` selects literal app-root-relative
200
+ HTML paths already included and not excluded, for example \`["index.html"]\`.
201
+ The entry is always selected first; \`[]\` selects only the entry. Omission
202
+ retains automatic discovery of the entry and included secondary pages with an
203
+ active base. The schema-1 package projection preserves this as \`documents\`,
204
+ including the distinction between omission and an empty list.
205
+ Selected pages retain their existing path-correct base requirement. With an
206
+ explicit list, other included HTML documents retain their exact content, even
207
+ when referenced by an iframe. Document selection leaves serving, packaging and
208
+ offline resource membership unchanged. HTML component processing and shared
209
+ runtime-resource traversal retain their existing behavior.
210
+ Development startup refreshes the selected managed maps; package and build
211
+ consume the saved source maps and the same document selection.
202
212
  Commit generated import maps and enabled offline app files. Hosting workflows consume those committed files rather than generating them.
203
213
  Named \`${directRuntime?'arcane-os/modules/* and arcane-os/entities/*':'arcane/*'}\` imports resolve through the managed map to the selected SDK files. Packaging copies the complete selected application, runtime, and specifier
204
214
  map to \`dist/${appId}\` without running application tests. Run \`verify\` only when
package/src/toolchain.mjs CHANGED
@@ -299,6 +299,7 @@ async function refreshPreparedImportMap(prepared,{signal,onEvent,workspaceOperat
299
299
  signal
300
300
  });
301
301
  if(inspected.entry!==manifest.entry
302
+ ||JSON.stringify(inspected.documents)!==JSON.stringify(manifest.documents)
302
303
  ||JSON.stringify(inspected.include)!==JSON.stringify(manifest.include)
303
304
  ||JSON.stringify(inspected.exclude)!==JSON.stringify(manifest.exclude)){
304
305
  throw new ArcaneError(