chore(deps)(deps-dev): bump @oclif/plugin-help from 6.2.58 to 7.0.2

[dependabot]

Bumps @oclif/plugin-help from 6.2.58 to 7.0.2.

Release notes

Sourced from @​oclif/plugin-help's releases.

7.0.2

Bug Fixes

• deps: bump @​humanfs/node from 0.16.6 to 0.16.8 (23ea4be)

7.0.1

Bug Fixes

• deps: bump js-yaml from 4.3.1 to 4.3.2 (6c3ca98)

7.0.0

• feat!: upgrade oclif/core to v5 @​W-23512455@ (c01c5f4)

BREAKING CHANGES

• bump node engine to >=22.0.0

6.3.0

Features

• bumping eslint to v10 (W-23473845) (489a2a1)

Changelog

Sourced from @​oclif/plugin-help's changelog.

7.0.2 (2026-09-25)

Bug Fixes

• deps: bump @​humanfs/node from 0.16.6 to 0.16.8 (23ea4be)

7.0.1 (2026-09-25)

Bug Fixes

• deps: bump js-yaml from 4.3.1 to 4.3.2 (6c3ca98)

7.0.0 (2026-08-31)

• feat!: upgrade oclif/core to v5 @​W-23512455@ (c01c5f4)

BREAKING CHANGES

• bump node engine to >=22.0.0

6.3.0 (2026-08-24)

Features

• bumping eslint to v10 (W-23473845) (489a2a1)

Commits

• a4dab33 chore(release): 7.0.2 [skip ci]
• 61943a0 Merge pull request #1182 from oclif/dependabot-npm_and_yarn-humanfs-node-0.16.8
• 23ea4be fix(deps): bump @​humanfs/node from 0.16.6 to 0.16.8
• 594cde7 Merge pull request #1186 from oclif/k80/fix-release-workflow
• a9e3eec ci: fix trustedPublishing value for npm job in onRelease.yml
• 2054c1a chore(release): 7.0.1 [skip ci]
• ca86356 Merge pull request #1184 from oclif/dependabot-npm_and_yarn-js-yaml-4.3.2
• 6c3ca98 fix(deps): bump js-yaml from 4.3.1 to 4.3.2
• 524337d Merge pull request #1185 from oclif/k80/trusted-publishing
• d27fe62 ci: configure onRelease.yml for trusted publishing
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​oclif/plugin-help since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

📓 Docs Drift Check

Nothing in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 0 changed package(s)), so this run has no opinion about the docs.

What this run could not see

• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.
• a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 0 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json 2f2fa11d756f665a4c06160480c1dce15b9d67a4 → packageMentionDocs.

[objectstack-fleet]

Closed 2026-10-01T08:00Z in favour of #21125, on the maintainer's instruction.

Provenance:

• Who: the maintainer.
• Verbatim: 「三组大版本升级:同意 * oclif:关三个 PR,立卡(推荐)。」
• Where: PM seat session session_018gA1pE6eJtwHhqx72G8U9X, 2026-10-01.

@oclif/plugin-help 7.0.2 depends on @oclif/core ^5.0.0, but this PR leaves the CLI on core 4.13.3, so the lockfile ends up with two core copies. Note also that the plugin is a devDependency only, and oclif loads oclif.plugins only from dependencies, so a green CI here says nothing about the plugin itself. #21125 moves core, plugin-help and plugin-plugins together.

---

Generated by Claude Code

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.