Port post-migration Splice docs updates#616
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
My feedback via Slack I am looking at https://github.com/canton-network/cf-docs/pull/616/changes. I see sv-major-upgrade.mdx and validato-major-upgrade.mdx were deleted. I'm not sure that is the right thing. Those files may need to exist with a disclaimer that they don't apply to DevNet and that LSU is the mechanism. I think a similar thing DevNet/TestNet/MainNet tab is needed for the Grafana dashboards (docs-main/global-synchronizer/production-operations/splice-metrics-overview.mdx) where the release notes say You may need to check with @Itai Segall. For the other items, can you do a side by side comparison of the old splice docs and the new doc site. |
performed a comparison. confirming the copy worked faithfully. |
Summary
Ports the remaining documentation deltas from
canton-network/spliceafter the initial cf-docs copy and after the partial refresh in0baa65af.Changes included:
traffic_summaryandapp_activity_recordssections for CIP-0104 preview fields.activityIngestionUserVersion.additionalLegacysynchronizers.0.6.4and0.6.5.Notes
The audit found one remaining target-side provenance issue that this PR intentionally does not resolve:
docs-main/global-synchronizer/reference/splice-metrics.mdxpoints atsplice:docs/src/deployment/observability/metrics_reference.rst, but that source path is missing in currentsplice/main. That looks like stale source metadata rather than a source change to port.Validation
jq empty docs-main/docs.jsongit diff --checksplice-metrics.mdxprovenance marker remainsdirenv exec /Users/danielporter/control/.worktrees/splice-docs-migration-audit-cf-docs npx mintlify validatefromdocs-main