@sacho/sacho-x86_64-pc-windows-msvc 0.1.0-dev.12 → 0.1.0-dev.8

package/README.md

@@ -18,7 +18,7 @@ towncrier assumes Python; changesets assumes an npm monorepo. Sacho is a single
 static binary with no runtime dependencies, usable in any repository regardless
 of language, and it does not even assume Git.
 
-[*Sacho is opinionated.*](./PHILOSOPHY.md) It enforces one fragment format,
+[Sacho is opinionated.](./PHILOSOPHY.md) It enforces one fragment format,
 one output style, and one set of invariants. Configuration exists to describe
 your repository, not to customize the philosophy.
 
@@ -55,51 +55,6 @@ Without mise, npm, or Cargo, download the archive for your platform from
 [GitHub Releases]: https://github.com/dahlia/sacho/releases
 
 
-Agent Skill
------------
-
-Sacho ships an [Agent Skill] that teaches AI coding agents, such as Claude Code,
-how to adopt and operate Sacho: writing fragments for users, cutting releases,
-and forward-porting fixes across maintenance branches.
-
-In Claude Code, install it as a plugin. Add this repository as a plugin
-marketplace, then install the `sacho` plugin:
-
-~~~~ text
-/plugin marketplace add dahlia/sacho
-/plugin install sacho@sacho
-~~~~
-
-For other agents, or to install the skill without the plugin system, use the
-[`skills`] CLI, which reads the skill straight from this repository:
-
-~~~~ sh
-npx skills add dahlia/sacho
-~~~~
-
-Add `-a claude-code` to target one agent, `-g` to install it globally, and
-`--skill sacho` to select the skill by name.
-
-The skill is also bundled inside the `@sacho/sacho` npm package, following the
-[`skills-npm`] layout. In a project that depends on that package, run
-`npx skills-npm setup` once to link bundled skills from *node\_modules* into
-your agent on every install.
-
-[Agent Skill]: https://agentskills.io/
-[`skills`]: https://github.com/vercel-labs/skills
-[`skills-npm`]: https://github.com/antfu/skills-npm
-
-
-Documentation
--------------
-
-The [*Sacho documentation*] walks through adoption, everyday use, releases,
-CI, and version-control integration. It also explains Sacho's core concepts and
-provides complete command and configuration references.
-
-[*Sacho documentation*]: https://sacho.dev/guide/getting-started
-
-
 How it works
 ------------
 
@@ -181,9 +136,7 @@ sacho release --next 1.3.0
 
 If no next version has been set, pass the release version explicitly, for
 example `sacho release 1.2.0`. Use `--date YYYY-MM-DD` when the release date
-must be supplied rather than taken from the local clock. A repository with no
-released changelog sections can cut its first release without fragments. Later
-empty releases require an explicit `--allow-empty`.
+must be supplied rather than taken from the local clock.
 
 After committing a release, print its frozen Markdown section with `show`:
 
@@ -208,8 +161,7 @@ Version-control integration
 ---------------------------
 
 Sacho can enforce that commits changing configured source paths also carry a
-changelog fragment. Select the repository's VCS and the paths to check in
-*sacho.toml*:
+changelog fragment. Select the repository's VCS in *sacho.toml*:
 
 ~~~~ toml
 [vcs]
@@ -224,6 +176,41 @@ Git also supports `sacho check --staged`. The `none` preset explicitly skips
 VCS-backed checks while leaving fragment validation and changelog consistency
 checks enabled.
 
+Each preset supplies three subprocess commands. Repositories can override one
+command without repeating the other two:
+
+~~~~ toml
+[vcs]
+preset = "git"
+
+[vcs.commands]
+message = ["my-vcs-wrapper", "message", "${commit}"]
+~~~~
+
+The first array element is the executable and every remaining element is one
+literal argument; Sacho never invokes a shell. The commits command uses
+`${base}`, while changed-paths and message use `${commit}`. An overridden query
+is the complete query and does not invoke commands from its preset behind the
+scenes. The built-in Mercurial preset handles parent comparisons internally.
+
+The query output contracts are:
+
+ -  `commits` emits zero or more nonempty UTF-8 commit identifiers, oldest
+    first and one per line. The final line may end in LF; CRLF is also
+    accepted.
+ -  `changed-paths` emits concatenated NUL-terminated name-status records.
+    Ordinary records are `A\0PATH\0`, `D\0PATH\0`, `M\0PATH\0`, or
+    `T\0PATH\0`, where `T` denotes a file type change. Copy and rename records
+    are `C[SIMILARITY]\0OLD_PATH\0NEW_PATH\0` and
+    `R[SIMILARITY]\0OLD_PATH\0NEW_PATH\0`, where the optional similarity is a
+    decimal percentage from 0 through 100. Status fields are UTF-8 and paths
+    are nonempty repository-relative platform paths; path bytes need not be
+    UTF-8 on Unix. Nonempty output ends in NUL. A copied or renamed fragment
+    counts as new content only when similarity is present and below 100;
+    omitting it does not satisfy fragment coverage.
+ -  `message` emits the complete UTF-8 commit message verbatim. Sacho does not
+    trim it.
+
 `sacho init` installs Git merge attributes and drivers in Git repositories. In
 Mercurial repositories it installs an idempotent block in *.hg/hgrc* containing
 a successful-merge update hook and, when changelog materialization is enabled,
@@ -232,12 +219,6 @@ the changelog merge driver. These integrations invoke the executable that ran
 per-path merge-driver hook; after resolving a concurrent fragment merge, run
 `sacho sync --force`.
 
-See [*CI and hooks*] for fragment coverage and [*Version control*] for preset,
-merge-driver, and custom-query details.
-
-[*CI and hooks*]: https://sacho.dev/guide/ci-and-hooks
-[*Version control*]: https://sacho.dev/guide/version-control
-
 
 Etymology
 ---------
@@ -262,13 +243,3 @@ is the same insistence this tool makes against generating changelogs from
 commit messages after the fact.
 
 [1]: https://en.wikipedia.org/wiki/Veritable_Records_of_the_Joseon_Dynasty#Compilation_process
-
-
-License
--------
-
-Copyright (C) 2026 Hong Minhee.
-
-Sacho is free software licensed under the GNU General Public License version 3
-only. It comes with no warranty, to the extent permitted by law. See
-[*LICENSE*](./LICENSE) for the full terms.

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "@sacho/sacho-x86_64-pc-windows-msvc",
-  "version": "0.1.0-dev.12+df65120",
+  "version": "0.1.0-dev.8+a3ec562",
   "description": "The Sacho binary for x86_64-pc-windows-msvc",
   "license": "GPL-3.0-only",
   "author": "Hong Minhee <hong@minhee.org>",
-  "homepage": "https://sacho.dev/",
+  "homepage": "https://github.com/dahlia/sacho",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/dahlia/sacho.git"