chore: rename core crate for release

[franciscojavierarceo]

Summary

• rename the publishable core package from agentic-core to agentic-server-core while preserving the Rust library target name agentic_core
• keep the workspace release version at 0.1.0 and point the server dependency at agentic-server-core = 0.1.0
• mark agentic-praxis as unpublished and update docs references to the new core crate name
• exclude local DB files, tests, and benches from the published core tarball

Test Plan

• cargo fmt -- --check
• cargo clippy --all-targets -- -D warnings
• cargo test
• cargo publish --dry-run -p agentic-server-core --allow-dirty
• cargo package -p agentic-server-core --allow-dirty --list

Note: agentic-server packaging/publish dry-run cannot complete until agentic-server-core v0.1.0 exists in the crates.io index; Cargo fails dependency resolution with no matching package named agentic-server-core found, which is expected before publishing the core crate first.

[ashwing]

One question on the version before this goes out for a release, inline.

[ashwing]

The description says 0.0.1 (workspace version + this pin), but it's 0.1.0 here and the workspace version at line 6 is unchanged too — the diff doesn't bump anything. Which one's intended for the release? Worth pinning down since crates.io versions are immutable once published.

Minor while you're here: the packaged tarball still ships tests/ and benches/ sources but excludes their cassette fixtures, so cargo test from the published crate can't find them. Harmless for consumers, but excluding tests/** + benches/** too would slim it if you want.

[franciscojavierarceo]

whoops this was a miss, fixed.

[maralbahari]

LGTM

[maralbahari]

@franciscojavierarceo @ashwing let's merge the rename after #83?
I added a comment for this. once addressed we can include this refactor with the release