chore(): Update module github.com/yuin/goldmark-meta to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/yuin/goldmark-meta	v1.1.0 → v2.0.2

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

yuin/goldmark-meta (github.com/yuin/goldmark-meta)

v2.0.2

Compare Source

• chore: update goldmark/v2 dependency

v2.0.1

Compare Source

• chore: update goldmark/v2 dependency

v2.0.0

Compare Source

• chore: initial commit of v2

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM (* 0-3 * * *)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[Darkness4]

Risk Assessment

Risk: High (80-90%)

What changed

• goldmark-meta upgraded from v1.1.0 → v2.0.2 (major version bump)
• Module path changes from github.com/yuin/goldmark-meta → github.com/yuin/goldmark-meta/v2
• v2 is designed to work with goldmark v2 — the release notes confirm: "chore: update goldmark/v2 dependency"

Why risk is high

goldmark-meta v2 is not a standalone upgrade — it depends on github.com/yuin/goldmark/v2. This PR only adds the goldmark-meta/v2 dependency but does NOT update the main goldmark import from v1 to v2. The result is:

• web/build.go imports meta "github.com/yuin/goldmark-meta" (v1) and uses meta.New() and meta.Meta with a goldmark v1 instance
• web/index/index.go imports meta "github.com/yuin/goldmark-meta" (v1) and uses document.OwnerDocument().Meta()
• These v1 imports will still work with goldmark v1, but the v2 dependency in go.mod is orphaned — nothing in the codebase imports github.com/yuin/goldmark-meta/v2
• If the main goldmark is later upgraded to v2 (as in PR chore(): Update module github.com/yuin/goldmark to v2 #216), the meta imports need to change to v2 too

Failure modes

• PR builds pass because the v2 dependency is added but unused — no compile error from the dependency alone
• When combined with PR chore(): Update module github.com/yuin/goldmark to v2 #216 (goldmark v2 upgrade), both PRs together create a partially migrated state: goldmark v2 is imported but goldmark-meta v1 is still used with a v2 goldmark instance → incompatible types at compile time
• The meta.Get(ctx) and document.OwnerDocument().Meta() APIs may have changed between goldmark-meta v1 and v2