@nextcommerce/campaigns-os 1.43.1 → 1.46.0

package/AGENTS.md

@@ -40,6 +40,11 @@ every read, so nothing shifts under you mid-orientation.
 | 8 | `contracts/agent-relevant-change-policy.v1.json` | What this repository counts as agent-relevant, and why a path was excluded. |
 | 9 | `docs/orientation-contract-reference.md` | Every enum, reason code, remedy, bound, and a worked example per terminal outcome. |
 
+The ledger may declare a `baseline_floor`. History before it lives in dated
+files under `contracts/archive/`; those are optional reads, not part of this
+order. A reviewed baseline older than the floor is refused with
+`baseline_below_floor`: adopt a newer reviewed baseline.
+
 Apply the limits from step 4 **before** you finish assembling. Exceeding one is
 a refusal with reason code `orientation_too_large`. Never truncate: a partial
 view of a release is worse than no view, because you cannot tell which part you
@@ -117,8 +122,10 @@ appends no lifecycle entry and creates no file of its own. One effect does
 precede argument refusal: `start`, `prepare-build`, `build`, `run start` and
 `run end` close out a stale run session at the root they are about to act on
 before argv is refused, which is a declared effect of those commands and is
-suppressed by `--no-write`. Every remitting command's effect declaration, when
-published, names its destination as open-world, and the agent onboarding skill
+suppressed by `--no-write`. Commands implementing `--dry-run` also suppress
+that closeout whenever the flag is present, including a value that will be
+refused (such as `run end --dry-run yes`). Every remitting command's effect
+declaration, when published, names its destination as open-world, and the agent onboarding skill
 records an explicit telemetry choice before the first remitting command.
 
 1.37.0 adds `demo --target <new-directory>`, an offline visual sample