docs: date the bundled skill with its release (FRK-025)

[any-victor]

Why

The vendored copy of the skill is a released snapshot, so a reader needs to know which forkctl release its text describes. ctl-bundle-contract asks every bundled skill to carry version:, kept current by a verctl pin, as qctl and verctl already do.

What

• .ctl/operator/SKILL.md.jinja imports ctl-core's version_line, and operator_docs passes version => CARGO_PKG_VERSION. The committed skills/forkctl/SKILL.md carries version: 0.0.38.
• .ctl/ver.yaml gains a skill pattern, version: {version}, matched once, with a pin on skills/forkctl/SKILL.md, so each Version PR moves the line with the release and the render test stays byte-equal.
• Cargo.toml drops package.homepage. It repeated package.repository, and nightly cargo reports it as redundant.
• AGENTS.md records how the version line is produced.

No changeset: no shipped behaviour changes.

Proof

PR CI runs verify, including operator_docs, which byte-compares the render. Pushed with the verify pre-push job excluded; every other pre-push job passed.

Closes FRK-025

[kodus-hostinger]

Review

Full · 1 open

@kody review after new commits. @kody full re-reads the whole PR.

Summary

This PR stamps the bundled operator skill (skills/forkctl/SKILL.md) with the forkctl release its text describes. The Version PR process keeps that stamp current from now on.

Changes

• Skill frontmatter gains a version: field. The .ctl/operator/SKILL.md.jinja template imports ctl-core's version_line macro and renders {{ version_line(version) }} into the frontmatter. The committed render now carries version: 0.0.38.
• The version comes from the crate. In src/operator_docs.rs, render_template passes version => env!("CARGO_PKG_VERSION") into the template context. As a result, the existing operator_docs byte-comparison test also checks that the skill's version matches the crate version.
• Release pinning. .ctl/ver.yaml adds a skill pattern (version: {version}, matched exactly once) and a pin for skills/forkctl/SKILL.md under the forkctl package. This lets the Version PR bump the skill's version along with the other pinned files.
• Docs and task tracking.
  • AGENTS.md now explains where the skill's version: comes from and how the skill pin in .ctl/ver.yaml moves it at release.
  • tasks.yaml adds queue item FRK-025. Its acceptance criteria are that the skill's version: equals the crate version and that the pin matches exactly once.
• Unrelated cleanup. Cargo.toml drops the homepage field, which duplicated repository.

Impact

Readers and agents using the installed skill can see which forkctl release the instructions correspond to. Drift between the skill and the crate version is caught by operator_docs and fixed automatically during release bumps.

Files

File	Status	+	−
.ctl/operator/SKILL.md.jinja	modified	+2	−0
.ctl/ver.yaml	modified	+6	−0
AGENTS.md	modified	+1	−1
Cargo.toml	modified	+0	−1
skills/forkctl/SKILL.md	modified	+1	−0
src/operator_docs.rs	modified	+1	−0
tasks.yaml	modified	+9	−0

Open

File	Severity	Finding
.ctl/operator/SKILL.md.jinja	medium	The new ctl-core template import may not exist in the pinned ctl-core 0.6.21.

History

When	Pass	Open
17 Oct 19:50 UTC	Full	1
17 Oct 13:06 UTC	Incremental	1

_{Inspect this review}