fix(content): use text+lp fences for line protocol syntax examples

[jstirnaman]

What changed

• Adds a Hugo render hook for lp fences. It preserves source text, highlights field-family syntax, and falls back to escaped plain text for malformed input.
• Adds a dependency-free lp validator to the code-block linter and makes invalid lp fences blocking CI errors. Intentionally invalid fixtures can use lint="false".
• Adds formatter fixtures; validator, extractor, and CLI tests; Cypress coverage; and documentation and generated instruction updates.
• Retains the earlier syntax-fence correction for issues Change comments in line protocol syntax to be self-descriptive # #7678 and Change comments in line protocol syntax to be self-descriptive # #5821.

Why

Line protocol examples need syntax-aware rendering and validation. The former js and sh labels incorrectly represented line protocol as executable JavaScript or shell code, and the new lp support prevents malformed examples from silently reaching the docs.

Impact

Docs rendering now gives lp fences dedicated syntax markup. CI rejects malformed lp fences unless they are explicitly exempted. No runtime dependency or product behavior changes.

Verification

• yarn test:lint-codeblocks (65 passing)
• yarn test:render-regression (12 passing)
• yarn build:agent:instructions
• yarn validate:agent-instructions
• Pre-commit and pre-push hooks passed.

Closes #7678
Closes #5821

[github-actions]

Vale Style Check Results

Metric	Count
Errors	0
Warnings	4

Warnings (4)

File	Line	Rule	Message
content/AGENTS.md	11	Google.Colons	': D' should be in lowercase.
content/AGENTS.md	12	InfluxDataDocs.Spelling	Did you really mean 'Shortcodes'?
content/AGENTS.md	12	Google.Colons	': D' should be in lowercase.
content/AGENTS.md	291	Google.Colons	': S' should be in lowercase.

---

✅ Check passed

[github-actions]

🔗 Link Check Results — Link Check Bot

❌ 3 broken link(s) found — fix them before merging.

Metric	Value
Files Checked	10
Total Links	4082
Errors	3
Warnings	10
Success Rate	99.191574%

Broken Links

Source File	Broken URL	Error	Report
content/influxdb3/cloud-serverless/reference/syntax/line-protocol/_index.md	/influxdb3/cloud-serverless/write-data/#timestamp-precision	Fragment not found: #timestamp-precision	Report
content/influxdb/v2/reference/syntax/line-protocol/_index.md	/influxdb/v2/write-data/#timestamp-precision	Fragment not found: #timestamp-precision	Report
content/influxdb/cloud/reference/syntax/line-protocol/_index.md	/influxdb/cloud/write-data/#timestamp-precision	Fragment not found: #timestamp-precision	Report

⚠️ 10 warning(s) (do not fail CI)

Source File	URL	Issue
content/enterprise_influxdb/v1/guides/write_data/_index.md	https://support.influxdata.com/	Network error: SSL certificate not trusted. Use --insecure if site is trusted (e…
content/example/_index.md	https://support.influxdata.com/	Network error: SSL certificate not trusted. Use --insecure if site is trusted (e…
content/influxdb/cloud/reference/syntax/line-protocol/_index.md	https://support.influxdata.com/	Network error: SSL certificate not trusted. Use --insecure if site is trusted (e…
content/influxdb/v2/reference/syntax/line-protocol/_index.md	https://support.influxdata.com/	Network error: SSL certificate not trusted. Use --insecure if site is trusted (e…
content/influxdb3/cloud-dedicated/reference/syntax/line-protocol/_index.md	https://support.influxdata.com/	Network error: SSL certificate not trusted. Use --insecure if site is trusted (e…
content/influxdb3/cloud-serverless/reference/syntax/line-protocol/_index.md	https://support.influxdata.com/	Network error: SSL certificate not trusted. Use --insecure if site is trusted (e…
content/influxdb3/cloud/reference/syntax/line-protocol/_index.md	https://support.influxdata.com/	Network error: SSL certificate not trusted. Use --insecure if site is trusted (e…
content/influxdb3/clustered/reference/syntax/line-protocol/_index.md	https://support.influxdata.com/	Network error: SSL certificate not trusted. Use --insecure if site is trusted (e…
content/influxdb3/core/reference/line-protocol/_index.md	https://support.influxdata.com/	Network error: SSL certificate not trusted. Use --insecure if site is trusted (e…
content/influxdb3/enterprise/reference/line-protocol/_index.md	https://support.influxdata.com/	Network error: SSL certificate not trusted. Use --insecure if site is trusted (e…

---

_{Full details: workflow run summary and artifact. Last updated: 2026-08-25 21:59:23 UTC}

[jstirnaman]

## Known gap: lp fence has no syntax highlighting

Converting these blocks from js/sh to lp fixes the mislabeling (they were never valid JS/shell), but introduces a visual regression worth tracking.

What's lost: assets/styles/layouts/_syntax-highlighting.scss has a .language-js rule (originally added for Flux duration/time values, e.g. 1h30m) that colors a number token immediately followed by an identifier token:

// Javascript / Flux specific styles (duration and time values)
.language-js {
  .mi + .nx, .mf + .nx { color: $article-code-accent5; }
}

This incidentally colorized line protocol's integer/uinteger suffixes (12485903i, 1u) when those blocks were fenced js. Chroma has no lp lexer, so class=language-lp blocks render with zero token spans — confirmed via build output on this branch. Result: the float/integer/uinteger/boolean/timestamp/special-characters/comment field-value examples in content/shared/v3-line-protocol.md and content/shared/influxdb-v2/reference/syntax/line-protocol.md go from (wrongly-labeled but) colorized to flat, unhighlighted text.

Not a template bug — nothing breaks, no build/render error. lp fence support is new to this repo; this is the first real-world content landing on lp for these particular blocks, so there's no prior precedent being broken, just no highlighting gained either.

[jstirnaman]

## Known gap: lp fence has no syntax highlighting

Converting these blocks from js/sh to lp fixes the mislabeling (they were never valid JS/shell), but introduces a visual regression worth tracking.

What's lost: assets/styles/layouts/_syntax-highlighting.scss has a .language-js rule (originally added for Flux duration/time values, e.g. 1h30m) that colors a number token immediately followed by an identifier token:

// Javascript / Flux specific styles (duration and time values)
.language-js {
  .mi + .nx, .mf + .nx { color: $article-code-accent5; }
}

This incidentally colorized line protocol's integer/uinteger suffixes (12485903i, 1u) when those blocks were fenced js. Chroma has no lp lexer, so class=language-lp blocks render with zero token spans — confirmed via build output on this branch. Result: the float/integer/uinteger/boolean/timestamp/special-characters/comment field-value examples in content/shared/v3-line-protocol.md and content/shared/influxdb-v2/reference/syntax/line-protocol.md go from (wrongly-labeled but) colorized to flat, unhighlighted text.

Not a template bug — nothing breaks, no build/render error. lp fence support is new to this repo; this is the first real-world content landing on lp for these particular blocks, so there's no prior precedent being broken, just no highlighting gained either.

Fixed with:

• b776526 feat(line-protocol): add fences highlighting and validation
• e691ae2 style(test): format line protocol regression check

[sanderson]

I think there's a lot more we could do for syntax highlighting line protocol, but it's probably beyond this PR and may even be worth contributing to Chroma upstream. I think this is good enough for now.

[jstirnaman]

I think there's a lot more we could do for syntax highlighting line protocol, but it's probably beyond this PR and may even be worth contributing to Chroma upstream. I think this is good enough for now.

My thoughts exactly. I considered starting the Chroma work, but it'll have to wait for now.