Skip to content

Vault ecosystem auto-setup on first activate (personal + public vault, mounts.toml) (#312) - #313

Draft
aarontrowbridge wants to merge 1 commit into
mainfrom
312-vault-ecosystem-auto-setup-on-first-activate-personal-+-public-vault-mountstoml
Draft

Vault ecosystem auto-setup on first activate (personal + public vault, mounts.toml) (#312)#313
aarontrowbridge wants to merge 1 commit into
mainfrom
312-vault-ecosystem-auto-setup-on-first-activate-personal-+-public-vault-mountstoml

Conversation

@aarontrowbridge

Copy link
Copy Markdown
Member

Closes #312.

Follow-up to #307 (armonia workspace). New Marketplace users get a working vault ecosystem with zero commands.

  • vault_setup.ts: ensureVaultEcosystem() — idempotent, never throws: ensureArmoniaDataDirs + ensurePersonalVault (no-op if exists) + ensurePublicVault (shallow clone harmoniqs/vault-public with 10s cap, placeholder if offline/no-git) + ensureMountsToml (absent-only, personal rw first, public ro second).
  • extension.ts: call it before the first prepareOpencodeProject so the mount stack is correct on boot; remove now-redundant ensureDefaultPersonalVault.
  • trees.ts: update Armonia placeholder to reflect auto-provision (personal + vault-public after first run).
  • tools/bootstrap-armonia.sh: mirror same three vault steps as idempotent block (CLI/extension order agnostic), curl-able.
  • tools/migrate-to-armonia.sh: three-bucket repos routing (packages/, demos/, flat), bucket-converging on re-run.
  • skills/amico-vault/SKILL.md: vault-* naming in kinds table, new First-run lifecycle subsection for vault-public (kind=public, ro).

Verification: rm -rf ~/.amico ~/armonia && install + open → personal + public present, mounts.toml written, second activate no-op, offline degrades to placeholder.

… vault, mounts.toml) (#312)

- vault_setup.ts: ensureVaultEcosystem() — idempotent, never throws:
  ensureArmoniaDataDirs, ensurePersonalVault, ensurePublicVault
  (shallow clone vault-public, 10s cap, offline placeholder),
  ensureMountsToml (absent-only, personal rw first, public ro second)
- extension.ts: call ensureVaultEcosystem() before first
  prepareOpencodeProject so mount stack is correct on boot;
  remove now-redundant ensureDefaultPersonalVault
- trees.ts: update Armonia placeholder to reflect auto-provision
- tools/bootstrap-armonia.sh: mirror same three vault steps as
  idempotent block (CLI/extension order agnostic), curl-able
- tools/migrate-to-armonia.sh: three-bucket repos routing
  (packages/, demos/, flat), bucket-converging on re-run
- skills/amico-vault/SKILL.md: vault-* naming in kinds table,
  new First-run lifecycle subsection for vault-public (kind=public, ro)
@aarontrowbridge
aarontrowbridge force-pushed the 312-vault-ecosystem-auto-setup-on-first-activate-personal-+-public-vault-mountstoml branch from 661778a to 904ab25 Compare August 20, 2026 08:48
@coderabbitai

coderabbitai Bot commented Aug 20, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: b868d93b-fbe9-44e0-ab2f-1c5241a7ec69

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Vault ecosystem auto-setup on first activate (personal + public vault, mounts.toml)

1 participant