AGENTS.md ยท diff

git:20260831.cc4095f to git:20260916.572e260

9 added, 53 removed. Audit A to A.

- # AGENTS.md
-
- Instructions for coding agents working on this repository.
-
- ## Installing Archify
-
- Installing, updating, removing, or reinstalling Archify changes live agent
- configuration outside this checkout. Do that only when the user names that exact
- action directly, such as "install Archify" or "update the global Archify Skill."
- An implied need or a request to edit, test, review, commit, push, merge, release,
- publish, or sync this repository is not consent.
-
- Before any live installation mutation:
-
- 1. Confirm the exact action, source, agent, and global or project scope. Do not
- infer `--all`; use `--yes` only after those values are explicit. A reinstall
- is an update/install operation, not permission to remove unrelated paths.
- 2. For a Skills CLI add, first run
- `npx -y skills add tt-a1i/archify --list --full-depth`. This documented
- `--list` mode must discover exactly one Skill named `archify`. On a command
- error, zero matches, or multiple matches, stop and report the output without
- running a mutating command.
- 3. Install from the canonical `tt-a1i/archify` source. Do not use a path under a
- system temporary directory, a Git worktree, or another session-scoped
- checkout as a local package source. A deliberate local-source install may
- use a clean, durable checkout only when the user explicitly asks for it;
- prefer `--copy` unless they explicitly request managed symlinks.
- 4. Before a manual copy or extraction, fail if the destination exists; report
- the exact path and never delete or replace it unless the user explicitly
- approves that named path after seeing the conflict. For Skills CLI and
- package-manager operations, use their own conflict handling,
- never add an unrequested force flag, and report every skipped, replaced, or
- failed destination.
- 5. Afterward, report the exact command, source, action, skill or package, agent,
- scope, and result. Never describe a partial installation as success.
+ # Agent instructions
- For `skills update`, name `archify` and pass `--global` or `--project` explicitly;
- do not run an unscoped bulk update. For `skills remove`, name `archify`, specify
- its scope and requested agents, and never use `--all`. Manual `archify.zip`
- extraction, Claude.ai upload, DSH plugin add/remove, and package-manager
- installation follow the same action/scope confirmation and reporting rules; use
- the documented exact destination or package version and preserve unrelated
- files. The Skill's update checker is notification-only, so an update notice
- never authorizes installation.
+ Follow [CONTRIBUTING.md](CONTRIBUTING.md) for repository changes and [REVIEWING.md](REVIEWING.md) for reviews.
- ## Repository workflow
+ ## Live Archify installations
- Follow [`CONTRIBUTING.md`](CONTRIBUTING.md) for planning, compatibility,
- validation, generated artifacts, and pull-request evidence. In particular:
+ Install, update, reinstall, or remove a live Archify installation only when the user explicitly requests that action. Repository editing, testing, reviewing, publishing, or syncing does not authorize installation. This applies to Skills CLI, manual ZIP copies, and DSH plugins. Reuse authorization already given for the same action and scope; ask only for unresolved decisions.
- - start from the latest `main` and keep one behavior per pull request;
- - run the narrowest relevant test first and `npm test` from `archify/` before
- final review;
- - rebuild `archify.zip` only when packaged Skill bytes change;
- - do not claim remote CI passed unless it ran on the current head;
- - never include secrets, private repository content, personal data, or customer
- data in repository artifacts.
+ - Keep the source, Skill/package, target agents, and global/project scope within the request. Avoid bulk operations or force flags that expand that scope. An update notification is informational.
+ - Before a Skills CLI install, run `npx -y skills add tt-a1i/archify --list --full-depth` and verify exactly one Skill named `archify`. Stop on failed or ambiguous discovery.
+ - Use the canonical remote source by default. Use a local source only when requested, from a durable checkout; live symlinks must not point into temporary directories or disposable worktrees.
+ - Preserve unrelated files and existing unmanaged destinations. Report a destination conflict before replacing it unless that exact replacement is already explicitly authorized; use the installer's documented conflict handling within the approved scope.
+ - Report the action, source, targets, and result, including skipped or failed destinations. A partial installation is not a complete success.