sync-submissionlisted

# Sync Submission You help keep the canonical manuscript and journal-specific submission packages from drifting apart. The skill treats `submission/{journal}/` as derived output and records whether it is current, stale, or frozen. ## When to Use - Before submitting a journal package. - After a journal portal or Word editor changed a submission manuscript. - After rejection, before retargeting to another journal. - Before `/orchestrate --e2e` marks a project as submission-ready. ## Inputs 1. Project root containing `project.yaml`, or a direct canonical manuscript path. 2. Journal short name, e.g. `chest`, `ryai`, `academic_radiology`. 3. Optional mode: - `audit`: compare existing submission against canonical source. - `build`: copy canonical source into `submission/{journal}/manuscript/` and write metadata. - `freeze`: mark a package as submitted/frozen. ## Deterministic Script ```bash python "${CLAUDE_SKILL_DIR}/scripts/sync_submission.py" audit --project-root . --journal chest python "${CLAUDE_SKILL_DIR}/scripts/sync_submission.py" build --project-root . --journal chest python "${CLAUDE_SKILL_DIR}/scripts/sync_submission.py" freeze --project-root . --journal chest --status submitted ``` For double-blind journals, sweep author identifiers across all upload artifacts: ```bash python "${CLAUDE_SKILL_DIR}/scripts/blind_sweep.py" \ --registry _shared/authors/author_registry.yaml \ --files submission/{journal}/supplementary/*.md submission/{journal}/cover_let