# Rebuild this exact release

Version 0.1.11 adds independent paired task stores, a shared-only exchange,
a narrow loopback A2A 1.0 receiver/client and an attended launcher. One base-store
claim check prevents the paired installation from executing its peer's next stage.
The source index identifies every changed file. No household database, token,
model reply, test library or private checkpoint is part of this package.

Version 0.1.10 connects the board to the existing workshop database. It adds a
read-only projection and synthetic examples, extends the local UI and launcher,
and retains the memory engine and task execution code from 0.1.9 byte-for-byte.
Its source index lists the exact changed files. The default practice uses only
invented records; no household task database is included.

Version 0.1.9 adds the optional read-only task board, a synthetic demonstration,
a standalone launcher and focused tests. The board adapts the working Relay
projection; it does not include the household database or Relay dispatch service.
Existing memory, workshop and private-dialogue code is retained from 0.1.8.
The runtime helper changes only its reported release version.

The extracted plugin is also its complete build input tree. No developer home
directory, installed plugin cache, private library, or running Hearth is needed.
Python 3.11 or newer is sufficient; no pip dependencies are required.

From the extracted folder:

```sh
python -B tools/build_plugin_bundle.py --source-root . --output-dir ../rebuilt-plugin
```

The output directory must be outside the source folder. An existing archive or
checksum is never overwritten. The recipe checks every listed input before
writing, uses a fixed date, file permissions, ordering and compression settings,
and leaves the source tree unchanged. It prints the Python and zlib versions.
Exact compressed ZIP matching is established in the tested environment; another
compression library version may produce different ZIP bytes from identical files.

`BUILD_INPUTS.json` lists exact payload inputs, including the recipe and this
guide. It excludes itself and generated `manifest.json` to avoid circular hashes.
The resulting package manifest covers the input manifest too. `SOURCE_INDEX.json`
explains the retained baseline and selective additions without host-specific paths.
Compare the final ZIP digest to the independently published release checksum.
Changing both code and its local manifest is not authenticated provenance.

Version 0.1.8 extends that updater to existing Grok Build and Antigravity
connections. Each update selects one explicit project or global configuration;
no precedence, mirror update or additional rights are inferred. The same launcher
and runtime-check mechanism remain, with the reported release version updated.
The source index binds every changed updater, test, guide and metadata file.

Version 0.1.7 adds the guided existing-connection updater, a separate launcher,
runtime observations and the one-time client challenge check. The MCP observer
is optional; ordinary memory policy and existing calls remain compatible. The
package keeps source and launcher bindings distinct so a household's extended
core is not replaced by a portable policy. Config edits and runtime evidence
are tested with synthetic fixtures; package verification is not a reconnect.
Every retained and changed file is bound in SOURCE_INDEX.json.

Version 0.1.6 adds the reviewed empty-own-page hint and measured browse_scope
receipt metadata in the SQLite adapter and portable host. Defaults and rights
are unchanged. Its portable twelve-case regression preserves the reviewed test
assertions and binds them to the shipped host and engine. The exact three repair
inputs, other content changes and retained members are in SOURCE_INDEX.json.

Version 0.1.5 added the continue-tomorrow guide and onboarding corrections. The
setup helper now distinguishes a preview from an installed or retained connection,
and points first-time users to explicit library creation. MCP browse descriptions
and its JSON-schema default annotation explain own versus shared/all scope.
For that 0.1.5 release, store behavior, permissions, workshop execution, model
transport and the optional private-dialogue runtime were byte-identical to 0.1.4. SOURCE_INDEX.json binds
the guide, focused test changes and every other changed member.

Version 0.1.4 retains the complete 0.1.3 payload except its named source-index
updates. It adds the active SQLite local-dialogue adapter and pure dialogue
engine, plus updated terminal/inbox reporting. The optional stdlib host facade,
synthetic exercise and integration checks are new portable code, not the running
Hearth server. No house service, experimental ledger, private library or provider
client is included. Terminal tools retain the previous release's explicit host
path requirement. See `PRIVATE_LOCAL_DIALOGUE.md` for the executable example and
what a real host must supply. All changes are identified in SOURCE_INDEX.json.

Version 0.1.3 adds the shared workshop: the workshop task store and runner,
the `scripts/workshop.py` launcher, the example task, the Codex app-server
transport-kind fix and the Claude Max login policy check. The task store,
transport and memory runner retain the tested local source bytes. The workshop
prompt uses operator-neutral wording in this portable release. Launcher help
and the workshop guide include small integration corrections. SOURCE_INDEX.json
records the exact changed files, retained basis and packaging transformations.
The earlier live demonstration is evidence for the retained runtime mechanics;
it is not a live test of this new launcher or its revised prompt opening.

Version 0.1.2 extended the continuity 0.6.1 basis with six participant namespaces,
current per-operation access checks and runtime catalog diagnostics, plus the
tested one-message inbox carry. The experimental rights ledger is omitted;
boot reports that status explicitly. The source index identifies each retained
or updated member and the packaging transformations. The household Relay MCPs
and Hearth service are not included. Extraction does not replace an installed
client, memory library or service.

For a changed fork, deliberately create a new version and new input manifest;
do not label changed bytes as the unchanged release.