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>
Windows Package Manager (winget) Manifest
This directory contains the winget manifest files for publishing beads to the Windows Package Manager.
Installation (once published)
winget install SteveYegge.beads
Manifest Files
SteveYegge.beads.yaml- Version manifest (main file)SteveYegge.beads.installer.yaml- Installer configurationSteveYegge.beads.locale.en-US.yaml- Package description and metadata
Submitting to winget-pkgs
- Fork https://github.com/microsoft/winget-pkgs
- Create directory:
manifests/s/SteveYegge/beads/<version>/ - Copy the three manifest files to that directory
- Submit a PR to microsoft/winget-pkgs
Or use the wingetcreate tool:
wingetcreate update SteveYegge.beads --version <new-version> --urls <new-url> --submit
Updating for New Releases
When releasing a new version:
- Update the version in all three manifest files
- Update the InstallerUrl in the installer manifest
- Update the InstallerSha256 (get from checksums.txt in the release)
- Update the ReleaseNotesUrl
- Submit PR to microsoft/winget-pkgs
Getting the SHA256
curl -sL https://github.com/gastownhall/beads/releases/download/v<VERSION>/checksums.txt | grep windows