schaefera/doubleo7
1
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions
doubleo7/Cargo.toml

30 lines
866 B
TOML
Raw Normal View History

Extract swear_cleanup to its own repo, flatten deep_research to root deep_research is the only project this repo is meant to showcase, so the Cargo workspace wrapping it and an unrelated side project no longer earns its keep: - swear_cleanup moved to a new standalone local repo (~/dev/swear_cleanup, not pushed anywhere) via `git subtree split`, with its pre-workspace- split history (when it lived at src/swear_cleanup/ in a single shared crate) spliced onto its post-split history rather than starting from a single flattened snapshot. FINDINGS.md, which was sitting at this repo's root but was actually swear_cleanup's own build log, went with it. - deep_research/{src,Cargo.toml,README.md,docs} moved to the repo root; the [workspace] table collapsed into a plain [package] manifest with dependency versions inlined from the old [workspace.dependencies]. - Cargo.toml keeps an explicit empty [workspace] table (not just omitted) so that checking this repo out as a nested git worktree — this project's own normal workflow — can't accidentally inherit a stale ancestor directory's workspace manifest, which is exactly what broke the build while testing this change from a worktree. - .forgejo/workflows/deep_research-ci.yml -> ci.yml, dropping the now- meaningless -p deep_research scoping and path filters (redundant when it's the only thing in the repo). - README.md and docs/case-study.md updated for the flattened commands (cargo run/test with no -p flag); their relative links to each other and to src/ were already correct since both moved together. Verified: cargo build/test/clippy/fmt all clean from the new repo root.
2026-08-18 11:43:26 +00:00
[package]
chore: rebrand project
2026-08-18 12:26:50 +00:00
name = "doubleo7"
version = "0.2.0"
Extract swear_cleanup to its own repo, flatten deep_research to root deep_research is the only project this repo is meant to showcase, so the Cargo workspace wrapping it and an unrelated side project no longer earns its keep: - swear_cleanup moved to a new standalone local repo (~/dev/swear_cleanup, not pushed anywhere) via `git subtree split`, with its pre-workspace- split history (when it lived at src/swear_cleanup/ in a single shared crate) spliced onto its post-split history rather than starting from a single flattened snapshot. FINDINGS.md, which was sitting at this repo's root but was actually swear_cleanup's own build log, went with it. - deep_research/{src,Cargo.toml,README.md,docs} moved to the repo root; the [workspace] table collapsed into a plain [package] manifest with dependency versions inlined from the old [workspace.dependencies]. - Cargo.toml keeps an explicit empty [workspace] table (not just omitted) so that checking this repo out as a nested git worktree — this project's own normal workflow — can't accidentally inherit a stale ancestor directory's workspace manifest, which is exactly what broke the build while testing this change from a worktree. - .forgejo/workflows/deep_research-ci.yml -> ci.yml, dropping the now- meaningless -p deep_research scoping and path filters (redundant when it's the only thing in the repo). - README.md and docs/case-study.md updated for the flattened commands (cargo run/test with no -p flag); their relative links to each other and to src/ were already correct since both moved together. Verified: cargo build/test/clippy/fmt all clean from the new repo root.
2026-08-18 11:43:26 +00:00
edition = "2024"
# Not part of a Cargo workspace — this crate is the whole repo. Declared
# explicitly (rather than just omitting it) so that checking this repo out
# as a nested git worktree (as this project's own workflow does) can't
# accidentally pick up an ancestor directory's workspace manifest.
refactor: split into a Cargo workspace with per-project dependency sets deep_research and swear_cleanup were sharing one Cargo.toml, so every build compiled clap/indicatif/scraper/chrono (only needed by deep_research) even when just building swear_cleanup for its own course work, and vice versa. Moves each into its own workspace member crate (deep_research/, swear_cleanup/) with an independent Cargo.toml declaring only the deps it actually uses; common deps/versions are pinned once via [workspace.dependencies] so the two don't drift. Verified `cargo build -p swear_cleanup` alone no longer pulls in clap/indicatif/scraper/chrono (schemars still compiles for it, but that's a direct transitive dependency of rig itself, not something this split can avoid). Also verified the relocated deep_research binary still runs end-to-end against live Ollama with correct footnote citations and sources. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-08-14 17:43:13 +00:00
[workspace]
cargo new scaffold
2026-07-31 08:20:46 +00:00
Extract swear_cleanup to its own repo, flatten deep_research to root deep_research is the only project this repo is meant to showcase, so the Cargo workspace wrapping it and an unrelated side project no longer earns its keep: - swear_cleanup moved to a new standalone local repo (~/dev/swear_cleanup, not pushed anywhere) via `git subtree split`, with its pre-workspace- split history (when it lived at src/swear_cleanup/ in a single shared crate) spliced onto its post-split history rather than starting from a single flattened snapshot. FINDINGS.md, which was sitting at this repo's root but was actually swear_cleanup's own build log, went with it. - deep_research/{src,Cargo.toml,README.md,docs} moved to the repo root; the [workspace] table collapsed into a plain [package] manifest with dependency versions inlined from the old [workspace.dependencies]. - Cargo.toml keeps an explicit empty [workspace] table (not just omitted) so that checking this repo out as a nested git worktree — this project's own normal workflow — can't accidentally inherit a stale ancestor directory's workspace manifest, which is exactly what broke the build while testing this change from a worktree. - .forgejo/workflows/deep_research-ci.yml -> ci.yml, dropping the now- meaningless -p deep_research scoping and path filters (redundant when it's the only thing in the repo). - README.md and docs/case-study.md updated for the flattened commands (cargo run/test with no -p flag); their relative links to each other and to src/ were already correct since both moved together. Verified: cargo build/test/clippy/fmt all clean from the new repo root.
2026-08-18 11:43:26 +00:00
[dependencies]
feat: Introduce two agent flow with profanity verification.
2026-08-05 12:21:38 +00:00
anyhow = "1.0.104"
Extract swear_cleanup to its own repo, flatten deep_research to root deep_research is the only project this repo is meant to showcase, so the Cargo workspace wrapping it and an unrelated side project no longer earns its keep: - swear_cleanup moved to a new standalone local repo (~/dev/swear_cleanup, not pushed anywhere) via `git subtree split`, with its pre-workspace- split history (when it lived at src/swear_cleanup/ in a single shared crate) spliced onto its post-split history rather than starting from a single flattened snapshot. FINDINGS.md, which was sitting at this repo's root but was actually swear_cleanup's own build log, went with it. - deep_research/{src,Cargo.toml,README.md,docs} moved to the repo root; the [workspace] table collapsed into a plain [package] manifest with dependency versions inlined from the old [workspace.dependencies]. - Cargo.toml keeps an explicit empty [workspace] table (not just omitted) so that checking this repo out as a nested git worktree — this project's own normal workflow — can't accidentally inherit a stale ancestor directory's workspace manifest, which is exactly what broke the build while testing this change from a worktree. - .forgejo/workflows/deep_research-ci.yml -> ci.yml, dropping the now- meaningless -p deep_research scoping and path filters (redundant when it's the only thing in the repo). - README.md and docs/case-study.md updated for the flattened commands (cargo run/test with no -p flag); their relative links to each other and to src/ were already correct since both moved together. Verified: cargo build/test/clippy/fmt all clean from the new repo root.
2026-08-18 11:43:26 +00:00
chrono = "0.4.45"
clap = { version = "4", features = ["derive"] }
feat: stream the report to the terminal as the writer generates it Wires up starter.rs -> core.rs (CLI parsing and observability init moved into core, main.rs left as a thin entry point) and switches the report phase from Agent::prompt to rig's stream_prompt, printing each text delta to stdout as it arrives instead of waiting for the full response. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-08-17 10:17:26 +00:00
futures = "0.3"
Extract swear_cleanup to its own repo, flatten deep_research to root deep_research is the only project this repo is meant to showcase, so the Cargo workspace wrapping it and an unrelated side project no longer earns its keep: - swear_cleanup moved to a new standalone local repo (~/dev/swear_cleanup, not pushed anywhere) via `git subtree split`, with its pre-workspace- split history (when it lived at src/swear_cleanup/ in a single shared crate) spliced onto its post-split history rather than starting from a single flattened snapshot. FINDINGS.md, which was sitting at this repo's root but was actually swear_cleanup's own build log, went with it. - deep_research/{src,Cargo.toml,README.md,docs} moved to the repo root; the [workspace] table collapsed into a plain [package] manifest with dependency versions inlined from the old [workspace.dependencies]. - Cargo.toml keeps an explicit empty [workspace] table (not just omitted) so that checking this repo out as a nested git worktree — this project's own normal workflow — can't accidentally inherit a stale ancestor directory's workspace manifest, which is exactly what broke the build while testing this change from a worktree. - .forgejo/workflows/deep_research-ci.yml -> ci.yml, dropping the now- meaningless -p deep_research scoping and path filters (redundant when it's the only thing in the repo). - README.md and docs/case-study.md updated for the flattened commands (cargo run/test with no -p flag); their relative links to each other and to src/ were already correct since both moved together. Verified: cargo build/test/clippy/fmt all clean from the new repo root.
2026-08-18 11:43:26 +00:00
indicatif = "0.18.6"
reqwest = { version = "0.13.4", features = ["query", "json"] }
chore: Update rig to 0.42
2026-08-19 10:11:47 +00:00
rig = "0.42.0"
Extract swear_cleanup to its own repo, flatten deep_research to root deep_research is the only project this repo is meant to showcase, so the Cargo workspace wrapping it and an unrelated side project no longer earns its keep: - swear_cleanup moved to a new standalone local repo (~/dev/swear_cleanup, not pushed anywhere) via `git subtree split`, with its pre-workspace- split history (when it lived at src/swear_cleanup/ in a single shared crate) spliced onto its post-split history rather than starting from a single flattened snapshot. FINDINGS.md, which was sitting at this repo's root but was actually swear_cleanup's own build log, went with it. - deep_research/{src,Cargo.toml,README.md,docs} moved to the repo root; the [workspace] table collapsed into a plain [package] manifest with dependency versions inlined from the old [workspace.dependencies]. - Cargo.toml keeps an explicit empty [workspace] table (not just omitted) so that checking this repo out as a nested git worktree — this project's own normal workflow — can't accidentally inherit a stale ancestor directory's workspace manifest, which is exactly what broke the build while testing this change from a worktree. - .forgejo/workflows/deep_research-ci.yml -> ci.yml, dropping the now- meaningless -p deep_research scoping and path filters (redundant when it's the only thing in the repo). - README.md and docs/case-study.md updated for the flattened commands (cargo run/test with no -p flag); their relative links to each other and to src/ were already correct since both moved together. Verified: cargo build/test/clippy/fmt all clean from the new repo root.
2026-08-18 11:43:26 +00:00
schemars = "1"
scraper = "0.27"
refactor: split into a Cargo workspace with per-project dependency sets deep_research and swear_cleanup were sharing one Cargo.toml, so every build compiled clap/indicatif/scraper/chrono (only needed by deep_research) even when just building swear_cleanup for its own course work, and vice versa. Moves each into its own workspace member crate (deep_research/, swear_cleanup/) with an independent Cargo.toml declaring only the deps it actually uses; common deps/versions are pinned once via [workspace.dependencies] so the two don't drift. Verified `cargo build -p swear_cleanup` alone no longer pulls in clap/indicatif/scraper/chrono (schemars still compiles for it, but that's a direct transitive dependency of rig itself, not something this split can avoid). Also verified the relocated deep_research binary still runs end-to-end against live Ollama with correct footnote citations and sources. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-08-14 17:43:13 +00:00
serde = { version = "1.0.229", features = ["derive"] }
Chunk uploaded documents instead of truncating them at 20K chars A flat 20K-char cutoff (copied from the fetched-web-page limit) silently dropped everything past the first ~20KB of a larger file, and even within the cutoff, embedding a whole multi-page document as one vector made retrieval coarse — the vector just averages out whatever topics the document covers. Split each file into ~1500-char chunks via text-splitter (recursive semantic-boundary splitting: paragraph > sentence > word, never mid-word) and embed each chunk as its own document, tagged with its source and part number. This removes the practical size ceiling — a large file chunks the same way a short one does — and sharpens retrieval by letting it surface the specific passage relevant to a query. It also incidentally caps the worst-case retrieval payload: 5 chunks now tops out around 7500 chars versus the old worst case of 5 full 20K-char documents. Verified against a live Ollama nomic-embed-text pull: a short document still embeds as a single chunk, unchanged from before.
2026-08-18 12:43:14 +00:00
text-splitter = "0.32"
cargo new scaffold
2026-07-31 08:20:46 +00:00
tokio = { version = "1.53.1", features = ["full"] }
feat: structured tracing observability Enable Rig's built-in tracing spans (model, token usage, cache hits, latency) via tracing-subscriber, filterable through RUST_LOG and defaulting to info level. Logs write to stderr so stdout stays reserved for program output. Standardizes the remaining ad-hoc println! diagnostics (server startup, per-iteration revision progress, non-convergence) into structured tracing events at appropriate levels.
2026-08-05 13:23:30 +00:00
tracing = "0.1"
tracing-subscriber = { version = "0.3.23", features = ["env-filter"] }
Extract swear_cleanup to its own repo, flatten deep_research to root deep_research is the only project this repo is meant to showcase, so the Cargo workspace wrapping it and an unrelated side project no longer earns its keep: - swear_cleanup moved to a new standalone local repo (~/dev/swear_cleanup, not pushed anywhere) via `git subtree split`, with its pre-workspace- split history (when it lived at src/swear_cleanup/ in a single shared crate) spliced onto its post-split history rather than starting from a single flattened snapshot. FINDINGS.md, which was sitting at this repo's root but was actually swear_cleanup's own build log, went with it. - deep_research/{src,Cargo.toml,README.md,docs} moved to the repo root; the [workspace] table collapsed into a plain [package] manifest with dependency versions inlined from the old [workspace.dependencies]. - Cargo.toml keeps an explicit empty [workspace] table (not just omitted) so that checking this repo out as a nested git worktree — this project's own normal workflow — can't accidentally inherit a stale ancestor directory's workspace manifest, which is exactly what broke the build while testing this change from a worktree. - .forgejo/workflows/deep_research-ci.yml -> ci.yml, dropping the now- meaningless -p deep_research scoping and path filters (redundant when it's the only thing in the repo). - README.md and docs/case-study.md updated for the flattened commands (cargo run/test with no -p flag); their relative links to each other and to src/ were already correct since both moved together. Verified: cargo build/test/clippy/fmt all clean from the new repo root.
2026-08-18 11:43:26 +00:00
[dev-dependencies]
serde_json = "1"
Reference in a new issue Copy permalink