{"version":"2.1.229","anchor":"job-timelines-get-their-own-storage-address-and-config-copie","canonical_anchor":"job-timelines-get-their-own-storage-address-and-config-copie","heading":"Job timelines get their own storage address, and config copies are validated","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/job-timelines-get-their-own-storage-address-and-config-copie","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Job timelines get their own storage address, and config copies are validated\n\nBackground job timelines get their own storage namespace and config backups must be stamped and named.\n\n**What**\n\nBackground job timeline streams are now addressed through a dedicated namespace key rather than by file path, with an error that redirects anyone addressing the stream file directly. Recovery copies of the global config must name one of the recognised copy kinds and carry a stamp.\n\n**Evidence**\n\n`must be one of the global-config copy kinds (`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}