fix(ci): remove consumed changeset assertion for used-car-price-search

The test asserted a changeset entry for used-car-price-search existed in
.changeset/*.md, but changesets are deleted by `changeset version` during
the release flow. On the resulting version-bump commit (#85) the test
fails and blocks the release pipeline — same anti-pattern already
documented in CLAUDE.md and fixed before in #50 / #78.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

scripts/skill-docs.test.js

@@ -1365,19 +1365,6 @@ test("pack:dry-run includes the toss-securities workspace", () => {
   assert.match(packageJson.scripts["pack:dry-run"], /workspace used-car-price-search/);
 });
 
-test("used-car-price-search ships with a changeset for release automation", () => {
-  const changesetDir = path.join(repoRoot, ".changeset");
-  const changesetFiles = fs
-    .readdirSync(changesetDir)
-    .filter((name) => name.endsWith(".md"))
-    .map((name) => read(path.join(".changeset", name)));
-
-  assert.ok(
-    changesetFiles.some((doc) => /["']used-car-price-search["']:\s*(patch|minor|major)/.test(doc)),
-    "expected a changeset entry that releases used-car-price-search",
-  );
-});
-
 test("package-lock captures the toss-securities workspace metadata for npm ci", () => {
   const packageLock = readJson("package-lock.json");