feat: agent-memory v0.1.3

[kiloloop-release]

Promotes the 0.1.3 snapshot: 9 files changed, none added. Nothing is removed.

What lands

Fixed: sync on a home with local changes that is behind upstream. In 0.1.2 that home was stuck: pull refused because of the uncommitted changes, and push refused because the home was behind. Now:

• push and pull --agent NAME commit the allowlisted paths, fetch, rebase local commits onto upstream, then deliver.
• startup --pull supplies its runtime name as the agent, so SessionStart resolves the same case.
• A plain pull updates a clean home and reports any commits still ahead.
• A rebase conflict aborts, names the conflicting paths and keeps the local commit.
• Unrelated uncommitted paths are reported and never stashed; local merge commits and a git operation already in progress need manual resolution first.

The sync section of docs/commands.md and the README describe the new behaviour.

Snapshot integrity

• Every file matches the export. 84 files in the export and 84 in the staged tree, compared file by file with the same blob and mode; not judged from a diffstat.
• Nothing is deleted. No file tracked here is missing from the export, which matters because the export adds and overwrites but never removes.
• Size: measured at +360 / −79 across 9 files, against 84 files tracked here, so none are new.
• Scan: checked for absolute user paths, personal identifiers, bot account ids, secrets and secret names, with zero new hits.

Verification

Run against this exact content before the snapshot was taken:

• Full suite: 850 passed, 47 skipped.
• Installed-wheel suite: 853 passed, 44 skipped.
• Lint: ruff check . is clean.
• Build: python -m build and twine check both PASSED for the 0.1.3 sdist and wheel.
• CI: green on Python 3.10, 3.11, 3.12 and 3.13.
• Live check: a home one commit behind a local bare remote, with one uncommitted memory file:
  • 0.1.2: pull exits 1 (uncommitted changes present) and push --agent exits 1 (behind upstream by 1 commit).
  • 0.1.3: pull --agent exits 0 after it commits the file, rebases onto upstream and delivers; the home ends level with the remote and holds both changes.

Merging this and then tagging v0.1.3 publishes to PyPI, with build attestations from the pypi environment.