Memory bundle modules fail to install because `amplifier-data` dependency points to inaccessible GitHub repo

### Summary

`amplifier-bundle-memory` currently fails to activate its memory
tool and hooks because several modules depend on `amplifier-data`
from a GitHub URL that is not publicly accessible:

```text
amplifier-data @
git+https://github.com/michaeljabbour/amplifier-data@09482f1fa569ba8
407894cad3a32f8ab6aecbc3d

GitHub returns:

remote: Repository not found.
fatal: repository
'https://github.com/michaeljabbour/amplifier-data/' not found

As a result, the bundle reports as prepared, but the actual memory
runtime modules fail to install and are not usable.

Impact

On startup / amplifier continue, these modules fail to activate:

modules/tool-memory
modules/hooks-memory-capture
modules/hooks-memory-briefing
modules/hooks-project-context
modules/hooks-memory-interject

The optional hooks-behavioral-write module appears to use the same
dependency pattern and is likely affected as well.

This prevents the memory bundle from providing:

• tool-memory
• memory capture hook
• memory briefing hook
• project-context hook
• memory interjection hook
• native persistent memory storage via amplifier-data

Error output excerpt

Failed to install module from
/home/amplifier/.amplifier/cache/amplifier-bundle-memory-f830422fc83
3887b/modules/tool-memory.

stderr: × Failed to download and build `amplifier-data @
│
git+https://github.com/michaeljabbour/amplifier-data@09482f1fa569ba8
407894cad3a32f8ab6aecbc3d`
├─▶ Git operation failed
├─▶ failed to fetch into: .cache/uv/git-v0/db/924724f38e505f7b
├─▶ failed to fetch branch, tag, or commit
│ `09482f1fa569ba8407894cad3a32f8ab6aecbc3d`
╰─▶ process didn't exit successfully: `/usr/bin/git
fetch --tags --force --update-head-ok
'https://github.com/michaeljabbour/amplifier-data'
'+refs/heads/*:refs/remotes/origin/*'
'+HEAD:refs/remotes/origin/HEAD'` (exit status: 128)
--- stderr
remote: Repository not found.
fatal: repository
'https://github.com/michaeljabbour/amplifier-data/' not found

The same dependency failure repeats for:

hooks-memory-capture
hooks-memory-briefing
hooks-project-context
hooks-memory-interject

Expected behavior

A fresh Amplifier user should be able to install/activate
amplifier-bundle-memory without needing access to a private or
unavailable repository.

The memory bundle should either:

1 depend on a public, reachable amplifier-data repository/commit, or
2 document that amplifier-data is private and required access must be
configured, or
3 provide a fallback/clear installation failure message explaining
the dependency requirement.

Actual behavior

The bundle is prepared successfully, but its runtime modules fail to
activate because uv pip install -e ... --no-sources cannot fetch the
pinned amplifier-data dependency.

The final startup output includes:

Failed to activate tool-memory
Failed to activate hooks-memory-capture
Failed to activate hooks-memory-briefing
Failed to activate hooks-project-context
Failed to activate hooks-memory-interject
Bundle 'memory' prepared successfully

This makes the “prepared successfully” message misleading, because the
core memory capabilities are unavailable.

Likely affected dependency declarations

The inaccessible dependency appears to be declared directly in
multiple module pyproject.toml files, likely because modules are
installed with --no-sources:

modules/tool-memory/pyproject.toml
modules/hooks-memory-capture/pyproject.toml
modules/hooks-memory-briefing/pyproject.toml
modules/hooks-project-context/pyproject.toml
modules/hooks-memory-interject/pyproject.toml
modules/hooks-behavioral-write/pyproject.toml

Each appears to reference:

amplifier-data @
git+https://github.com/michaeljabbour/amplifier-data@09482f1fa569ba8
407894cad3a32f8ab6aecbc3d

Requested fix

Please update the memory bundle so amplifier-data resolves for users
without private repository access.

Possible fixes:

• Move/publish amplifier-data to a public repository.
• Update all repeated dependency pins to a reachable repo/commit.
• If the repo is intentionally private, document the required access
and setup steps.
• Improve activation reporting so the bundle does not say it prepared
successfully without clearly indicating that memory modules failed
and memory functionality is unavailable.

Environment

OS: Ubuntu Linux
Architecture: aarch64
Command: amplifier continue
Bundle: amplifier-bundle-memory
Cache path observed:
/home/amplifier/.amplifier/cache/amplifier-bundle-memory-f830422fc83
3887b
Dependency URL failing:
https://github.com/michaeljabbour/amplifier-data
Pinned commit: 09482f1fa569ba8407894cad3a32f8ab6aecbc3d

Inspect the dependency declarations in the six module pyproject.toml files named in the issue, then reproduce installation with uv pip install -e ... --no-sources. Trace how the inaccessible amplifier-data pin affects activation. Done means the dependency resolves for fresh users, or private access and the resulting activation behavior are clearly documented.

Written by the indexing model from the issue text.