[package]
name = "flowrs-record"
version.workspace = true
edition.workspace = true
publish.workspace = true
rust-version.workspace = true
authors.workspace = true
license = "MIT OR Apache-2.0"
description = "The union test-record schema for FlowRS: one record that round-trips with OpenHTF, HardPy, WATS and SystemLink, so FlowRS drops into an existing test line instead of replacing it."

[lib]
crate-type = ["rlib"]

[dependencies]
# The one implementation of sin, exp, ln, atan2, powf and the rest, the same bits in the
# browser and in a generated program (crates/flowrs-math).
flowrs-math = { path = "../flowrs-math" }
serde = { workspace = true }
serde_json = { workspace = true }
flowrs-sequence = { path = "../flowrs-sequence" }
# JUnit XML, the interchange format every CI system and most test runners emit. The same
# version flowrs-ingest already pins, so nothing new enters the lock.
quick-xml = "0.42.0"

[dev-dependencies]

# Symposium (`cargo agents`): an agent working on a project that depends on this crate gets
# the flowRS skill (crates/flowrs-mcp/symposium/flowrs, rendered by flowrs-mcp's
# skills::symposium_plugin) and the flowRS MCP server under the read-only plan profile. Never
# the full profile: a dependency is not a trust root, and Symposium registers servers at user
# level. Symposium 0.5.1 parses a crate's MCP entry but does not dispatch it yet; a registry
# carrying symposium/flowrs/SYMPOSIUM.toml registers the same entry today.
[package.metadata.symposium]

[package.metadata.symposium.defaults]
skills = false

[[package.metadata.symposium.skills]]
source.path = "../flowrs-mcp/symposium/flowrs/skills/core"

[[package.metadata.symposium.mcp_servers]]
name = "flowrs"
command = "flowrs-mcp"
args = ["--profile", "plan"]
env = []