docs: cross-reference the identifier-naming contributor guide

[miacycle]

Summary

Adds a "Naming conventions" section to README.md pointing at the ecosystem-wide canonical reference at https://github.com/meshery/schemas/blob/master/docs/identifier-naming-contributor-guide.md.

Sistent components that surface API data (tables, form fields, charts) must use the camelCase-on-the-wire identifiers defined by the Meshery / Layer5 ecosystem contract. The new pointer sits above "Contributing to Sistent" so it is visible to anyone adding or reviewing component props that map to a Meshery or Layer5 Cloud response shape. No inline rules are duplicated here — the guide is the single authoritative directory.

Paired cross-reference PRs are being opened in meshery/schemas, meshery/meshery, layer5io/meshery-cloud, layer5labs/meshery-extensions, and meshery/meshkit.

Test plan

• git diff --stat shows 1 doc-only file, +4 lines / -0 lines, no code modified.
• Branch opened off origin/master, signed off per DCO.

[gemini-code-assist]

Code Review

This pull request adds a new 'Naming conventions' section to the README.md, outlining the requirement for Sistent components to use camelCase identifiers for API data. Feedback was provided to remove a specific row count reference in the documentation to prevent it from becoming outdated as the linked guide grows.

[gemini-code-assist]

The specific mention of "26-row" is a maintenance risk as the naming guide is likely to grow or change over time. Removing this specific count makes the documentation more durable.

Suggested change

Sistent components that surface API data (tables, form fields, charts) must use the camelCase-on-the-wire identifiers defined by the Meshery / Layer5 ecosystem contract. See the [identifier-naming contributor guide](https://github.com/meshery/schemas/blob/master/docs/identifier-naming-contributor-guide.md) in `meshery/schemas` — the reader-friendly 26-row naming directory with before/after and do/don't examples — before adding props, column keys, or query-arg types that map to a Meshery or Layer5 Cloud response shape.

Sistent components that surface API data (tables, form fields, charts) must use the camelCase-on-the-wire identifiers defined by the Meshery / Layer5 ecosystem contract. See the [identifier-naming contributor guide](https://github.com/meshery/schemas/blob/master/docs/identifier-naming-contributor-guide.md) in `meshery/schemas` — the reader-friendly naming directory with before/after and do/don't examples — before adding props, column keys, or query-arg types that map to a Meshery or Layer5 Cloud response shape.

[Copilot]

Pull request overview

This PR updates Sistent’s top-level documentation to cross-reference the ecosystem’s canonical identifier naming guidance, helping contributors align component props/keys with Meshery / Layer5 API field naming.

Changes:

• Adds a new “Naming conventions” section to README.md.
• Links to the meshery/schemas identifier-naming contributor guide as the authoritative reference.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This sentence hard-codes a potentially fast-stale detail ("26-row") and links to a moving branch ref (blob/master). Consider removing the row count/extra descriptive claims and linking via a permalink (commit SHA) or another stable reference to avoid the README drifting over time.

Suggested change

Sistent components that surface API data (tables, form fields, charts) must use the camelCase-on-the-wire identifiers defined by the Meshery / Layer5 ecosystem contract. See the [identifier-naming contributor guide](https://github.com/meshery/schemas/blob/master/docs/identifier-naming-contributor-guide.md) in `meshery/schemas` — the reader-friendly 26-row naming directory with before/after and do/don't examples — before adding props, column keys, or query-arg types that map to a Meshery or Layer5 Cloud response shape.

Sistent components that surface API data (tables, form fields, charts) must use the camelCase-on-the-wire identifiers defined by the Meshery / Layer5 ecosystem contract. See `meshery/schemas/docs/identifier-naming-contributor-guide.md` before adding props, column keys, or query-arg types that map to a Meshery or Layer5 Cloud response shape.

[leecalcote]

Cross-reference pointer to the meshery/schemas identifier-naming contributor guide. README-only add.