chore: prepare v1.0.0 release

[sting8k]

Summary

• finalize the v1.0.0 changelog section used for release notes
• bump Cargo and npm package metadata to 1.0.0
• update Cargo.lock for the new package version

Validation

• release-note extraction for 1.0.0: PASS
• version consistency across Cargo.toml, Cargo.lock, and npm/package.json: PASS
• forbidden wording scan for release metadata: PASS
• cargo fmt --check: PASS
• git diff --check: PASS
• cargo package -p srcwalk --locked --no-verify: PASS

[greptile-apps]

Greptile Summary

This PR finalizes the 1.0.0 release by writing the CHANGELOG section, bumping Cargo.toml, Cargo.lock, and npm/package.json from 0.5.0 to 1.0.0. The four changed files are mechanical and internally consistent.

• CHANGELOG.md adds the full 1.0.0 entry with highlights, a breaking-change section, migration table, and added/changed/fixed notes that align with the feature commits already on the branch.
• Cargo.toml, Cargo.lock, and npm/package.json all move to 1.0.0 with no other changes.
• skills/srcwalk/SKILL.md was not changed in this PR, leaving compatible_srcwalk: \">=0.3.0\" — a lower bound that now permits using the updated GUIDE.md routing (which relies on 1.0.0-only commands) against a pre-1.0.0 binary.

Confidence Score: 4/5

The four changed files are correct version-bump mechanics; the risk lies in an unchanged file outside the diff.

The four changed files are correct and consistent. The concern is that skills/srcwalk/SKILL.md still advertises compatible_srcwalk >= 0.3.0, which allows a pre-1.0.0 binary to load the updated GUIDE.md and then fail on every 1.0.0-only command. AGENTS.md explicitly requires keeping SKILL.md in sync when the compatibility contract changes.

skills/srcwalk/SKILL.md — the compatible_srcwalk lower bound should be raised to >=1.0.0 before the release ships

Important Files Changed

Filename	Overview
CHANGELOG.md	1.0.0 section added with highlights, breaking changes, migration table, added/changed/fixed entries; content is consistent with the feature commits preceding this PR
Cargo.toml	Version bumped from 0.5.0 to 1.0.0; no other changes
Cargo.lock	srcwalk package version updated from 0.5.0 to 1.0.0 to match Cargo.toml; no dependency changes
npm/package.json	Version bumped from 0.5.0 to 1.0.0; no other changes

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR: chore prepare v1.0.0] --> B[CHANGELOG.md\n1.0.0 section finalized]
    A --> C[Cargo.toml\n0.5.0 → 1.0.0]
    A --> D[Cargo.lock\nsrcwalk 0.5.0 → 1.0.0]
    A --> E[npm/package.json\n0.5.0 → 1.0.0]
    A --> F{skills/srcwalk/SKILL.md\nNOT changed}
    F -->|compatible_srcwalk still >=0.3.0| G[⚠ Agent with srcwalk ≤0.5.0\nsatisfies constraint]
    G --> H[GUIDE.md routes to\n1.0.0-only commands\nreview, diff, discover --as access]
    H --> I[❌ CLI failures at runtime]
    C --> J[✅ Version consistency\nCargo.toml = Cargo.lock = npm = 1.0.0]

Loading

_{Reviews (1): Last reviewed commit: "chore: prepare v1.0.0 release" | Re-trigger Greptile}