Zotero Storage

Build the following focused alternative to Zotero Storage. This is a deliberately limited personal or small-team substitute, not parity with the paid service.

WORKING SLICE
Configure Zotero's supported personal-library attachment sync route and provide an operator checklist for upload, second-device download, conflict review and backup.

SETUP AND ARCHITECTURE
Use Zotero's built-in supported WebDAV attachment synchronization and a user-operated WebDAV service; no custom application database or model API. Prerequisites: Two Zotero clients with a personal library, a compatible HTTPS WebDAV account, supported Zotero setup documentation and an independent backup destination. Before integrating anything, record actual versions and permissions, plus model files or provider limits only where used, in the README; make unavailable dependencies visible rather than simulating success.

DOMAIN MODEL AND INVARIANTS
Track configuration, attachment filenames/hashes and transfer outcomes outside Zotero's live database; Zotero remains authoritative for bibliographic metadata and attachment identity.

IMPLEMENTATION CONTRACT
Keep bibliographic sync within Zotero's supported mechanism and never copy its live database between running clients. Back up files independently, protect WebDAV credentials and inspect partial transfer errors. Provide an operator checklist, the exact configuration files and a status/troubleshooting procedure in the existing tools; do not create a new application UI. Preserve the last saved state if a job or save fails. Include empty, loading, permission-denied, partial and retryable-error states. Log identifiers and error categories without secret values or unnecessary private content.

APP-SPECIFIC BOUNDARY AND RECOVERY
Correct the prior generic research-app scope. Evaluate supported WebDAV attachment sync for personal libraries using Zotero documentation; do not put its live database in a generic sync folder or claim group-library WebDAV support.

ACCEPTANCE SCENARIO
Add a PDF on device one, sync and download it on device two, then restore a backup copy after a deliberate local deletion; confirm metadata/attachment linkage remains intact. Also resume the configured workflow after an interrupted operation, confirm the saved record/export remains inspectable, and document the recovery action. These are implementation acceptance requirements, not a claim that this guide has been tested.

DELIVERY
Deliver a setup/runbook folder with configuration examples, permission instructions, troubleshooting steps, an independent backup/restore procedure and the exact acceptance walkthrough. Keep using the existing applications and their data formats; do not scaffold an unrelated app or database. Implement the working slice before optional integrations; list any deferred paid-product capabilities honestly. Do not add capabilities outside the working slice just to resemble the original product.

PROJECT RULES FOR AGENTS.md
Keep the domain invariants above executable at the write boundary. Propose scope changes before adding providers or permissions. Never fabricate source evidence, publish results, identity matches or successful delivery. Preserve user originals and require an explicit confirmation for destructive changes or external publication.

# AGENTS.md — Build guide for Zotero Storage

## Project scope
Configure Zotero's supported personal-library attachment sync route and provide an operator checklist for upload, second-device download, conflict review and backup.

Catalogue verdict: kinda. The narrow alternative is a personal-library file-sync setup, not a replacement reference manager. WebDAV can handle personal attachment syncing, while Zotero data sync remains separate and group-library file syncing needs Zotero Storage.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- Runtime and tools: Zotero's built-in supported WebDAV attachment synchronization and a user-operated WebDAV service; no custom application database or model API.
- Before starting: Two Zotero clients with a personal library, a compatible HTTPS WebDAV account, supported Zotero setup documentation and an independent backup destination.

## Stack and architecture
- Zotero's built-in supported WebDAV attachment synchronization and a user-operated WebDAV service; no custom application database or model API
- Data design: Track configuration, attachment filenames/hashes and transfer outcomes outside Zotero's live database; Zotero remains authoritative for bibliographic metadata and attachment identity.
- Setup: Two Zotero clients with a personal library, a compatible HTTPS WebDAV account, supported Zotero setup documentation and an independent backup destination

## Security and data integrity
- Keep bibliographic sync within Zotero's supported mechanism and never copy its live database between running clients. Back up files independently, protect WebDAV credentials and inspect partial transfer errors.
- Correct the prior generic research-app scope. Evaluate supported WebDAV attachment sync for personal libraries using Zotero documentation; do not put its live database in a generic sync folder or claim group-library WebDAV support.
- Keep secrets outside client bundles and exported projects; document what leaves the device and make retention/deletion controls visible.

## Agent implementation rules
- Project rule — domain: Track configuration, attachment filenames/hashes and transfer outcomes outside Zotero's live database; Zotero remains authoritative for bibliographic metadata and attachment identity.
- Project rule — scope and recovery: Correct the prior generic research-app scope. Evaluate supported WebDAV attachment sync for personal libraries using Zotero documentation; do not put its live database in a generic sync folder or claim group-library WebDAV support.
- Project rule — acceptance: Add a PDF on device one, sync and download it on device two, then restore a backup copy after a deliberate local deletion; confirm metadata/attachment linkage remains intact.
- Project rule — delivery: document real setup commands and permissions; do not claim a build, accuracy level, performance result or security certification that has not been demonstrated.

## Optional agent skills and references
- Recommended skill: [sharp-edges](https://github.com/trailofbits/skills/blob/main/plugins/sharp-edges/skills/sharp-edges/SKILL.md) — review configuration and API defaults against the app-specific invariants and recovery boundaries above; this is not a security certification. Follow the maintainer's installation instructions and match its requirements to the chosen runtime.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Demonstrate this working slice using synthetic or explicitly authorized non-sensitive examples: Configure Zotero's supported personal-library attachment sync route and provide an operator checklist for upload, second-device download, conflict review and backup.
- Share a synthetic example export and the acceptance walkthrough; keep real customer, health, financial and source data private: Add a PDF on device one, sync and download it on device two, then restore a backup copy after a deliberate local deletion; confirm metadata/attachment linkage remains intact.
- State the limits before asking someone to replace their existing tool: Correct the prior generic research-app scope. Evaluate supported WebDAV attachment sync for personal libraries using Zotero documentation; do not put its live database in a generic sync folder or claim group-library WebDAV support.

## Engineering roadmap
1. Phase 1 — Pin the working slice and create its example input: Configure Zotero's supported personal-library attachment sync route and provide an operator checklist for upload, second-device download, conflict review and backup. Confirm setup: Two Zotero clients with a personal library, a compatible HTTPS WebDAV account, supported Zotero setup documentation and an independent backup destination.
2. Phase 2 — Document authoritative storage and configure these safeguards in the existing tools: Track configuration, attachment filenames/hashes and transfer outcomes outside Zotero's live database; Zotero remains authoritative for bibliographic metadata and attachment identity.
3. Phase 3 — Configure the existing tools and document status/troubleshooting without building another app. Keep bibliographic sync within Zotero's supported mechanism and never copy its live database between running clients. Back up files independently, protect WebDAV credentials and inspect partial transfer errors.
4. Phase 4 — Expose the app-specific limits and recovery path in context: Correct the prior generic research-app scope. Evaluate supported WebDAV attachment sync for personal libraries using Zotero documentation; do not put its live database in a generic sync folder or claim group-library WebDAV support.
5. Phase 5 — Walk through this concrete acceptance case and preserve its exported evidence: Add a PDF on device one, sync and download it on device two, then restore a backup copy after a deliberate local deletion; confirm metadata/attachment linkage remains intact. Finish the README and backup/restore instructions; report unfinished capabilities explicitly.

## Paid-product capabilities outside this build
- Zotero-operated attachment storage and its integrated support path
- group-library file syncing through the WebDAV alternative
- access to WebDAV-stored files through the zotero.org library
- freedom from operating or choosing a separate WebDAV service

## Implementation prompt
Build the following focused alternative to Zotero Storage. This is a deliberately limited personal or small-team substitute, not parity with the paid service.

WORKING SLICE
Configure Zotero's supported personal-library attachment sync route and provide an operator checklist for upload, second-device download, conflict review and backup.

SETUP AND ARCHITECTURE
Use Zotero's built-in supported WebDAV attachment synchronization and a user-operated WebDAV service; no custom application database or model API. Prerequisites: Two Zotero clients with a personal library, a compatible HTTPS WebDAV account, supported Zotero setup documentation and an independent backup destination. Before integrating anything, record actual versions and permissions, plus model files or provider limits only where used, in the README; make unavailable dependencies visible rather than simulating success.

DOMAIN MODEL AND INVARIANTS
Track configuration, attachment filenames/hashes and transfer outcomes outside Zotero's live database; Zotero remains authoritative for bibliographic metadata and attachment identity.

IMPLEMENTATION CONTRACT
Keep bibliographic sync within Zotero's supported mechanism and never copy its live database between running clients. Back up files independently, protect WebDAV credentials and inspect partial transfer errors. Provide an operator checklist, the exact configuration files and a status/troubleshooting procedure in the existing tools; do not create a new application UI. Preserve the last saved state if a job or save fails. Include empty, loading, permission-denied, partial and retryable-error states. Log identifiers and error categories without secret values or unnecessary private content.

APP-SPECIFIC BOUNDARY AND RECOVERY
Correct the prior generic research-app scope. Evaluate supported WebDAV attachment sync for personal libraries using Zotero documentation; do not put its live database in a generic sync folder or claim group-library WebDAV support.

ACCEPTANCE SCENARIO
Add a PDF on device one, sync and download it on device two, then restore a backup copy after a deliberate local deletion; confirm metadata/attachment linkage remains intact. Also resume the configured workflow after an interrupted operation, confirm the saved record/export remains inspectable, and document the recovery action. These are implementation acceptance requirements, not a claim that this guide has been tested.

DELIVERY
Deliver a setup/runbook folder with configuration examples, permission instructions, troubleshooting steps, an independent backup/restore procedure and the exact acceptance walkthrough. Keep using the existing applications and their data formats; do not scaffold an unrelated app or database. Implement the working slice before optional integrations; list any deferred paid-product capabilities honestly. Do not add capabilities outside the working slice just to resemble the original product.

PROJECT RULES FOR AGENTS.md
Keep the domain invariants above executable at the write boundary. Propose scope changes before adding providers or permissions. Never fabricate source evidence, publish results, identity matches or successful delivery. Preserve user originals and require an explicit confirmation for destructive changes or external publication.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.