Updated: The file manifest carries the checksum of the JSON package format page

Updated: The JSON package format page shows rich text without the editor's namespace URIs

Updated: The file manifest carries the checksums of the JSON package format

Added: A JSON format for packages, an alternative serialization of the classic package model

A package can be written as package.json and JSON documents instead of
package.xml and XML documents. Every XML document of the package (the
definition, the files of its items, the object files) is mirrored element
for element in JsonML, rich text kept as its XML string, so the package
handlers and datatypes read the same DOM from either format and a package
converts from XML to JSON and back without loss. The classic format stays
the default; a classic package, its archive and its installation are
unchanged. Verified on every installer package of the 7x repository and a
test subtree: every document canonically equal after XML -> JSON -> XML,
every other file byte for byte, the JSON a fixed point.

- expPackageJson: the mapping, conversion of package directories and
  archives, validation, checksums (SHA-256 of every file in package.json)
- share/package/schema/package-v1.json, the JSON Schema of the format, and
  expJsonSchemaValidator to check documents against it
- eZPackage: export in either format (format json|xml), import and fetch
  detect the format by content, documents are read from XML or JSON,
  package metadata (<metadata><entry key>) for tools, archiveDirectory()
- Install as drafts, a generic install option: content objects become
  drafts, nothing is published, no published object changes; existing
  objects get a new draft or are left alone, an object of another class is
  a conflict; other items are listed instead of installed
- expPackageConflictReport: what an install meets here, by remote id
- ezpm: export --format=json, convert, validate, check, install --as-drafts
- Setup > Packages: Download as JSON, the package's format and metadata,
  the install page's report by remote id and the option to install as drafts
- The upload check and the package catalog accept package.json
- package.ini [PackageFormatSettings]; documentation in
  doc/bc/6.0/package-json-format.md; tests in expPackageJsonTest

Updated: The file manifest carries the checksums of the service declarations that opt in to the assistant

Updated: Read services can opt in to be tools of the assistant with 'ai' => true

A service declaration may carry 'ai' => true, or 'ai' => array( 'summary' => '...' ),
to say that the assistant of expai may call it: one declaration then serves HTTP
(ezjscore/call), MCP (the tools expmcp generates) and the assistant, each with the
caller's own permissions. Services stay private to the assistant by default, and a
service that writes is never offered. The catalogue reports the flag as ai.

Opted in, as reads checked by the content's own read access: expnode childrenNames,
childrenCount, breadcrumb, tree, latest and find; expsection list and ofNode; expstate
groups and ofObject; exptags roots, children, tree, search and ofnode. The services
documentation describes the flag and the three channels.

Updated: The file manifest carries the checksums of the Velocity streaming settings