fix(skills): honor legacy clawdbot metadata#71346
Conversation
Greptile SummaryThis PR adds Confidence Score: 5/5Safe to merge — the change is minimal, well-scoped, and covered by new regression tests. The only production change is adding one string to a constants array; LEGACY_PROJECT_NAMES is used only to derive LEGACY_MANIFEST_KEYS, which is already consumed correctly by resolveOpenClawManifestBlock. The frontmatter parser's shouldPreferInlineLineValue logic ensures the raw JSON5 metadata string is preserved when YAML would otherwise parse it as a flow mapping, so the end-to-end path is correct. No security implications, no interface changes. No files require special attention. Reviews (1): Last reviewed commit: "fix(skills): honor legacy clawdbot metad..." | Re-trigger Greptile |
a48e931 to
9f4cbed
Compare
|
Landed via rebase onto
Thanks @chen-zhang-cs-code! |
Summary
metadata.clawdbotmanifest blocks alongsidemetadata.openclawCloses #71323.
Verification
pnpm exec oxfmt --check --threads=1 src/compat/legacy-names.ts src/shared/frontmatter.test.ts src/agents/skills.buildworkspaceskillstatus.test.tsnode scripts/run-vitest.mjs run --config test/vitest/vitest.agents.config.ts src/agents/skills.buildworkspaceskillstatus.test.tsnode scripts/run-vitest.mjs run --config test/vitest/vitest.unit-fast.config.ts src/shared/frontmatter.test.tspnpm check:changedgit diff --check