Add Rimsky orchestration bridge for RIFT

[oshaughnessy-junior]

Summary

• generate a RIFT follow-up analysis for Rimsky sample_sink orchestration
• normalize Rimsky/Bilby prior and PSD metadata into the RIFT Asimov schema
• create Rimsky-scoped LAL cache files for local frames and bootstrap RIFT from its PESummary output
• document the operator workflow and install rift-rimsky-analysis

The branch starts directly from oshaughn:rift_O4c at cac3b3e.

Validation

• 28 focused Rimsky/bootstrap tests pass with the O4c Asimov 0.5 environment
• 13 Rimsky integration tests pass with Asimov 0.6.1, the version locked by current Rimsky
• setup.py metadata resolves the RIFT package successfully
• git diff --check passes; the branch-wide diff contains no generated run products

[oshaughn]

Updated for the operational target requested here:

• the generated Rimsky config defaults Bilby to full-submit and automatically wires the post-PE RIFT follow-up;
• the RIFT production is Ready and bootstraps from the first bilby-online PESummary metafile;
• a real Rimsky → Asimov → RIFT end-to-end test now requires Asimov >=0.7;
• CI covers Rimsky 0.1.0rc1 on Python 3.12 and pinned Rimsky main on Python 3.14, forcing Asimov 0.7 and the merged bilby_pipe Asimov-0.7 adapter (be6c770).

Local verification passed for both published and current Rimsky combinations. External HTCondor submission is the only boundary excluded from the E2E test.

[oshaughnessy-junior]

Updated for the operational target requested here:

• the generated Rimsky config defaults Bilby to full-submit and automatically wires the post-PE RIFT follow-up;
• the RIFT production is Ready and bootstraps from the first bilby-online PESummary metafile;
• a real Rimsky → Asimov → RIFT end-to-end test now requires Asimov >=0.7;
• CI covers Rimsky 0.1.0rc1 on Python 3.12 and pinned Rimsky main on Python 3.14, forcing Asimov 0.7 and the merged bilby_pipe Asimov-0.7 adapter (be6c770).

Local verification passed for both published and current Rimsky combinations. External HTCondor submission is the only boundary excluded from the E2E test.

[interhost-cross-review-canary-v2]

Independent automated review completed at the recorded exact commit. Detailed findings were withheld from public output by the private-context egress policy and require private human declassification.

[interhost-cross-review-canary-v2]

Independent automated review completed at the recorded exact commit. Detailed findings were withheld from public output by the private-context egress policy and require private human declassification.