# copilot-sync - Doramagic AI Context Pack > Purpose: pre-work context for the user's host AI. This pack does not prove that the project has been installed, run, or validated. ## Project - canonical_name: `lvxiaoxin/copilot-sync` - capability: A tiny, cross-platform CLI (macOS / Linux / Windows) to **sync your Copilot configuration** — skills, MCP servers, agents, prompts, settings, and even session history, etc. — across multiple devices using a GitHub repository you own. - expected_user_outcome: A tiny, cross-platform CLI (macOS / Linux / Windows) to **sync your Copilot configuration** — skills, MCP servers, agents, prompts, settings, and even session history, etc. — across multiple devices using a GitHub repository you own. ## Operating Boundaries - Do not claim that the project has been installed, run, called through an API, or used on local files unless separate evidence proves it. - Project facts must come from repo evidence, Claim Graph, or explicit source references. - When a capability is not verified, mark it as unverified instead of completing it as fact. - publish_status: `publishable` - blocking_gaps: none --- ## Doramagic Context Augmentation The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints. ## Human Manual Outline Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph. Host AI hard rules: - Do not treat page titles, section order, summaries, or importance values as factual project evidence. - When explaining the Human Manual outline, state that it is only a reading route or salience signal. - Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph. - **Project Overview**: importance `high` - source_paths: package.json, bin/copilot-sync.js, src/cli.js, README.md - **Installation and Onboarding**: importance `high` - source_paths: src/commands/onboard.js, src/config.js, src/commands/status.js, src/prompt.js - **Configuration Push and Pull**: importance `high` - source_paths: src/commands/push.js, src/commands/pull.js, src/manifest.js, src/collect.js, src/repo.js - **Session History Sync**: importance `high` - source_paths: src/commands/history.js, src/history.js, src/history-store.js, src/cli.js ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `60aae5aa977081c54bb28d7451b7f779df06b7b2` - inspected_files: `README.md`, `package.json`, `src/cli.js`, `src/collect.js`, `src/commands/history.js`, `src/commands/onboard.js`, `src/commands/pull.js`, `src/commands/push.js`, `src/commands/status.js`, `src/config.js`, `src/fsutil.js`, `src/git.js`, `src/history-store.js`, `src/history.js`, `src/log.js`, `src/manifest.js`, `src/prompt.js`, `src/repo.js`, `src/secrets.js`, `src/tree.js` Host AI hard rules: - Without repo_clone_verified=true, do not claim that the source code has been read. - Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts. - Without quick_start_verified=true, do not claim that the Quick Start path has run successfully. ## Doramagic Pitfall Constraints These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes. ### Constraint 1: Capability evidence risk requires verification - Trigger: README/documentation is current enough for a first validation pass. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: capability.assumptions | https://github.com/lvxiaoxin/copilot-sync - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: Maintenance risk requires verification - Trigger: Project evidence flags a maintenance risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: evidence.maintainer_signals | https://github.com/lvxiaoxin/copilot-sync - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: Security or permission risk requires verification - Trigger: no_demo - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: downstream_validation.risk_items | https://github.com/lvxiaoxin/copilot-sync - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Security or permission risk requires verification - Trigger: no_demo - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: risks.scoring_risks | https://github.com/lvxiaoxin/copilot-sync - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: Maintenance risk requires verification - Trigger: issue_or_pr_quality=unknown。 - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: evidence.maintainer_signals | https://github.com/lvxiaoxin/copilot-sync - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: Maintenance risk requires verification - Trigger: release_recency=unknown。 - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: evidence.maintainer_signals | https://github.com/lvxiaoxin/copilot-sync - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.