prompt 2 to let claude loose on the implemenation after I reviewed

You are working in the cross-project layer, using the tasking project's 'css-archiver-query-tool-development' branch to capture progress. The subject is the use of the Experimental Physics Industrial Control System (EPICS) system as it is implemented at the Spallation Neutron Source (SNS). The goal of this session is to add the capability of agent(s) to make queries directly to the PV archive database directly whenever they need to interrogate the current or historical state of a real instrument that they are investigating or performing an analysis for. This has proven effective in the 'bl4a-DANGLE-investigation' branch (you may read the git log). On this machine, an "office" version of CSS/Phoebus runs in ~/opt/css/ (via ~/opt/css/product-sns-4.7.4-SNAPSHOT/phoebus.sh). This program is able to access the archive database without authorization (whatever credentials are needed are embedded in the configuration files). Please study this code carefully. Review the plan that was developed earlier to see if any refinements are needed after gaining an understanding of the CSS/Phoebus code. If it helps you, I have cloned the source code to "Phoebus" at '/home/controls/src/phoebus/' where the scan server source code is located in that repository at '/home/controls/src/phoebus/services/scan-server/src/main/java/org/csstudio/scan/server/'. Be thorough and systematic, using all the cross-project knowledge we have gained so far. If you are missing an item of information, please ask me to fetch it for you. If you run into an issue where you need sudo, please ask me to execute the line in a separate terminal.

Claude created [css-rdb-reader-analysis.md](css-rdb-reader-analysis.md) and [step1-live-test-results.md](step1-live-test-results.md) in this repository,

and updated [archiver-query-tool.md](https://code.ornl.gov/6ov/claude/-/blob/uvdl3/plan/archiver-query-tool.md) in the machine repository.

## Prompt 2

You are working in the cross-project layer, using the tasking project's 'css-archiver-query-tool-development' branch to capture progress. Please read 'plan/archiver-query-tool.md' thoroughly. Please implement the steps recommended in the 'Path forward' section:

1. Read this plan document in its entirety. ( *that is 'plan/archiver-query-tool.md'* )

2. Read `tasking/css-rdb-reader-analysis.md` on the

   `css-archiver-query-tool-development` branch of the tasking submodule for

   the source-code references that justify each design decision below.

3. Read the relevant context from `tasking/DANGLE-Motion-Failure-Analysis.md`

   Appendix D (the exact file paths, PV names, and time window that will be

   used as the correctness test) — note: this file is on the

   `bl4a-DANGLE-investigation` branch of the tasking submodule.

4. Begin Step 1 by asking the operator for greenlight to do the live read.

5. Only proceed to Step 2 after Step 1's exit criteria are met.

Also, if it not too much trouble, per the 'Knowledge capture / follow-up', step 6. You may apply/update this knowledge to each of the tasking branches:

```

  origin/bl4a-DANGLE-investigation

  origin/bl4a-S3-investigation

  origin/bl4b-alignment-integration

```

Thanks alot for this really important capability!  Have fun!