Merge pull request #167 from posit-dev/feat/read-edit-tool

feat: Add hashline-based file read and edit tools

Author: gadenbuie

DESCRIPTION

@@ -71,10 +71,10 @@ Suggests:
     roxygen2,
     shiny,
     shinychat (>= 0.3.0),
-    tibble,
     testthat (>= 3.0.0),
+    tibble,
     usethis
-Config/Needs/website: tidyverse/tidytemplate
+Config/Needs/website: brand.yml, tidyverse/tidytemplate
 Config/testthat/edition: 3
 Config/testthat/parallel: true
 Config/testthat/start-first: web, news, covr, search
@@ -106,8 +106,12 @@ Collate:
     'tool-docs.R'
     'tool-env-df.R'
     'tool-env.R'
+    'tool-files-edit.R'
+    'tool-files-list.R'
+    'tool-files-read.R'
+    'tool-files-replace.R'
     'tool-files-search.R'
-    'tool-files.R'
+    'tool-files-write.R'
     'tool-git.R'
     'tool-github.R'
     'tool-ide.R'

NAMESPACE

@@ -40,10 +40,12 @@ export(btw_tool_docs_vignette)
 export(btw_tool_env_describe_data_frame)
 export(btw_tool_env_describe_environment)
 export(btw_tool_files_code_search)
+export(btw_tool_files_edit)
 export(btw_tool_files_list)
 export(btw_tool_files_list_files)
 export(btw_tool_files_read)
 export(btw_tool_files_read_text_file)
+export(btw_tool_files_replace)
 export(btw_tool_files_search)
 export(btw_tool_files_write)
 export(btw_tool_files_write_text_file)

NEWS.md

@@ -1,5 +1,17 @@
 # btw (development version)
 
+* New `btw_tool_files_edit()` tool makes targeted, validated line-based edits
+  to files using `replace`, `insert_after`, and `replace_range` actions. Edits
+  are anchored to content hashes, so stale edits are rejected if the file has
+  changed. To support this, `btw_tool_files_read()` now annotates each line
+  with a short hash (e.g. `2:f1a|  return("world")`) when called as a tool
+  (#167).
+
+* New `btw_tool_files_replace()` tool finds and replaces exact string
+  occurrences in a file. By default it requires the string to appear exactly
+  once to prevent unintended changes; set `replace_all = TRUE` to replace all
+  occurrences (#167).
+
 * `btw_tool_files_read()` now correctly reads valid UTF-8 files containing non-ASCII characters (e.g., Cyrillic). Previously, these files were incorrectly rejected on Windows with non-English locales when `Encoding()` returned "unknown" even though they were valid UTF-8 (thanks @RKonstantinR, #160).
 
 * BREAKING CHANGE: Several tool groups and tool names have been renamed for clarity (#159):