Skip to content

Write Data\LastRun.json at the end of every run; retire the Beacon PostRun plugin template — release 26.9.21.0 - #13

Merged
SamSCN merged 2 commits into
mainfrom
claude/lastrun-summary-release
Sep 21, 2026
Merged

SamSCN merged 2 commits into
mainfrom
claude/lastrun-summary-release

Conversation

@SamSCN

@SamSCN SamSCN commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

Summary

Beacon now collects IDBridge from the box: its collector reads the IDBridge Sync scheduled task and a run summary the module writes natively. This release is the IDBridge half of that design (Beacon's docs/idbridge-plan.md, "The IDBridge side").

  • Write-IDBridgeRunSummary (Private\Core) replaces <DataRoot>\LastRun.json whole from the finally block of Invoke-IDBridge, after telemetry and before the PostRun plugins, on every run that is not a -Preview. Schema version 1, grown additively only: module version, run start/end/duration, success/readOnly/testRun, the enabled directories, the applied counts, thresholdExceeded, errorType/errorFunction (class and throwing function only, never the message) and lastSuccessAt (runEnd on a success, carried forward from the previous file on a failure). A write failure logs a Warn and never affects the run. No name, id, UPN, DN or group name is ever written.
  • Invoke-PluginPostRunBeacon retired: the template, its descriptor (config template moves to TemplateVersion: 3), its tests and its docs entries. A district that copied it can delete the plugin file, its descriptor and the ApiKey-Beacon vault secret.
  • Docs: PRIVACY.md gains "Not telemetry: the run summary file" naming every key; architecture step 13b, a functions.md entry, the DataRoot row in configuration.md and getting-started's PostRun bullet follow.
  • Release 26.9.21.0: the changelog heading rolled and ModuleVersion bumped, as the last commit.

Verification

  • Pester before: 240 passed, 0 failed. After: 238 passed, 0 failed (the deleted template's 10 cases out, 7 new cases and 1 structural case in).
  • Test-ModuleManifest passes at 26.9.21.0.
  • A file written by the new function was fed through Beacon's own ConvertTo-IdbridgeRunSummary parser: accepted, all twenty keys, carry-forward intact, no BOM.
  • Not executed: a real Invoke-IDBridge run against an install, AD or Google.

After merge

Dispatch the Publish workflow (Actions → Publish → Run workflow); it mints the v26.9.21.0 tag from main and publishes to the Gallery.

🤖 Generated with Claude Code

https://claude.ai/code/session_0144DV5TZ5tuFoUefCSp549T


Generated by Claude Code

…stRun plugin template

Beacon now collects IDBridge from the box: its collector reads the IDBridge Sync
task and a run summary the module writes natively. Write-IDBridgeRunSummary
(Private\Core) replaces <DataRoot>\LastRun.json whole from Invoke-IDBridge's finally
block, after telemetry and before the PostRun plugins, on every run that is not a
Preview: schemaVersion 1, module version, run start/end/duration, success/readOnly/
testRun, the enabled directories, the applied counts, thresholdExceeded, and
lastSuccessAt (runEnd on a success, carried forward from the previous file on a
failure). A failed run contributes the exception class and throwing function only,
never the message. A write failure logs a Warn and never affects the run.

The Invoke-PluginPostRunBeacon template, its descriptor (config template moves to
TemplateVersion 3), its tests and its docs entries are removed; PRIVACY.md names
the file and its keys, and the architecture, functions, configuration and
getting-started docs follow.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0144DV5TZ5tuFoUefCSp549T
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0144DV5TZ5tuFoUefCSp549T
@SamSCN
SamSCN merged commit df386a2 into main Sep 21, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants