.pubignore

# Patterns excluded from `dart pub publish` (in addition to / replacing
# the rules in the root `.gitignore`). Per dart.dev/go/pubignore, a
# .pubignore in a directory replaces the .gitignore in the same
# directory for publishing purposes, so the patterns below mirror the
# root .gitignore and then add the agent-tooling files that should not
# ship to package consumers.

# --- Mirror of root .gitignore ---------------------------------------

# Rust build artefacts
rust/target/

# cargo-fuzz workspace (separate Cargo workspace under rust/fuzz/ that
# pulls in libfuzzer-sys and is only ever exercised by maintainers
# running `cargo +nightly fuzz run`). Not part of the build the
# Native Assets hook performs for consumers, so the entire directory
# — sources, manifest, regression seed corpus, and target/ — is
# excluded from the published tarball.
rust/fuzz/

# Dart/Flutter
.dart_tool/
.flutter-plugins
.flutter-plugins-dependencies
.packages
build/
pubspec.lock

# CocoaPods (regenerated by `pod install`)
example/ios/Podfile.lock
example/macos/Podfile.lock
example/ios/Pods/
example/macos/Pods/

# Beads / Dolt files (added by bd init)
.dolt/
*.db
.beads-credential-key

# IDE — JetBrains
.idea/
*.iml
*.ipr
*.iws

# FVM Version Cache
.fvm/

# Coverage artefacts. Both `flutter test --coverage` (Dart) and
# `cargo tarpaulin --output-dir coverage` (Rust) write `lcov.info`
# into a sibling `coverage/` directory. Each CI run regenerates and
# uploads the file to Codecov directly from the workflow; the
# in-tree copy is purely a local artefact and must not ship inside
# the published tarball. Mirrors root .gitignore.
coverage/

# macOS Finder metadata. Mirrors root .gitignore; if a maintainer
# happens to publish from a directory a Finder window has visited,
# the local-only `.DS_Store` files must not ship in the tarball.
.DS_Store

# --- Additional publish-only exclusions ------------------------------

# AI-agent guidance files. Tracked in git (so contributors and the
# coding agents pick them up from the repo) but not useful to package
# consumers, who never run those agents against the published tarball.
AGENTS.md
CLAUDE.md

# Contributor documentation. Both files explicitly state at the top
# that they are for contributors / integrators and that day-to-day API
# users only need the README. Keeping them in git for the repo audience
# but excluded from the published surface.
ARCHITECTURE.md
DEVELOPMENT.md

# flutter_rust_bridge codegen config. The generated bindings are
# committed under lib/src/ffi/** and rust/src/frb_generated.rs and ship
# pre-built; the FRB codegen CLI is only ever run by maintainers on
# this repo, never by package consumers.
flutter_rust_bridge.yaml

# Maintainer's analyzer configuration. A consumer's analyzer reads the
# consumer's own analysis_options.yaml; ours does not influence their
# lints, so shipping it is noise on the package surface.
analysis_options.yaml

# Maintainer's test-runner configuration. Defines the `live` tag-skip
# directive that keeps the opt-in network suite under test/ out of the
# default `flutter test` gate; consumers never run this repo's test
# suite (test/ itself is excluded above), so the config is pure noise
# on the published surface.
dart_test.yaml

# Maintainer's SonarCloud/SonarQube project configuration. Read solely by
# the SonarCloud CI analysis that runs against this repo; package
# consumers never invoke SonarCloud against the published tarball, so
# the file is pure noise on the published surface — same rationale as
# the analyzer/test-runner/FRB configs above.
sonar-project.properties

# Maintainer-only Rust tool configs. rust/clippy.toml is read solely by
# `cargo clippy` and rust/tarpaulin.toml solely by `cargo tarpaulin`,
# both of which run only in this repo's CI / local maintainer workflow.
# The Native Assets build hook compiles consumer-side via `cargo build`
# (RustBuilder), which never reads either file, so they are pure noise on
# the published surface — same rationale as the analyzer/test-runner/FRB
# /Sonar configs above. (rust/rust-toolchain.toml is deliberately NOT
# excluded: RustBuilder reads it via rustup for the channel pin and the
# cross-compile targets used by consumer builds.)
rust/clippy.toml
rust/tarpaulin.toml

# Internal tooling. tool/check_bindings.dart is a CI drift check for
# the FRB codegen step that only runs when rust/src/api/*.rs changes;
# consumers never invoke it.
tool/

# Internal tests. test/ffi_smoke_test.dart exercises the FFI bridge
# in this repo's CI; it is not part of the public API and does not
# help consumers verify their integration.
test/

# Test-only Rust modules. Each external `tests.rs` sibling file (and
# the shared `test_helpers` module under nts/) is referenced via
# `#[cfg(test)] mod tests;` / `#[cfg(test)] pub(crate) mod
# test_helpers;` in the parent file, so Native Assets'
# `cargo build --release` against the consumer's machine never
# compiles or even parses them — the `#[cfg(test)]` attribute removes
# the module reference before file lookup. Inline
# `#[cfg(test)] mod tests { … }` blocks inside files like
# `rust/src/nts/cookies.rs` / `dns.rs` / `aead.rs` stay in place
# because those parent files are required by release builds; only the
# inner `tests` mod is cfg-gated. Excluding the sibling test files
# shaves ~243 KB uncompressed (~60 KB compressed, ~11% of the 4.0.0
# archive) without breaking any consumer-visible build path. Glob
# form so future test-module extractions are covered automatically.
rust/src/**/tests.rs
rust/src/**/test_helpers.rs