Convert gitgram/ and aitimemachine/ from embedded git repos (which showed as opaque submodule gitlinks on GitHub) into fully-tracked first-party content. AITM now merges its 7 vendored repos as first-party engines: - memory: beads (Go task DAG) + context7 (docs SDK), unified into saved_contexts - git: vendored C git (bundled binary) + gitnexus (in-process code intelligence) - agentic: a2a (@a2a-js/sdk) + pal (AITM-managed Python subprocess) Includes the full session's product build: Gitgram web/mobile/backend features, AITM website/CLI/MCP, the unified memory layer, engine build tooling (scripts/build-engines.sh, Dockerfile, CI), docs (README, ENGINES.md, ARCHITECTURE.md), and extensive test suites. Build artifacts, node_modules, external/, and gemini-cli are gitignored. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1.0 KiB
1.0 KiB
id, title, slug, sidebar_position
| id | title | slug | sidebar_position |
|---|---|---|---|
| restore | bd restore | /cli-reference/restore | 999 |
Generated from bd help --doc restore
bd restore
Restore the pre-compaction content of a compacted issue.
When an issue is compacted, its description/design/notes/acceptance criteria are summarized and the originals are archived to a compaction snapshot. This command recovers that original content.
By default it is read-only: it displays the archived content without modifying the database. Pass --apply to write the original content back into the issue and step its compaction level back down.
If no archived snapshot exists (e.g. the issue was compacted by an older bd before snapshot archiving), restore falls back to a best-effort reconstruction from Dolt version history, which can only be displayed, not applied.
bd restore <issue-id> [flags]
Flags:
--apply Write the restored content back into the issue (default: display only)
--json Output restore results in JSON format