Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 34 additions & 0 deletions .github/workflows/registry_reconcile.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
name: Registry Reconcile

# The ONLINE lifecycle leg (`lifecycle.py issues`): registry entries
# cross-checked against live GitHub — a tracking issue closed, or a
# `status: pr-open` PR merged, while the entry still reads pending. That
# second case is the crashed-ship signature (2026-08-17,
# version-stamp-sync-guards: six PRs merged, the session died before the
# bookkeeping, and no offline check could see it). A red run means finished
# work is still listed as pending: run the wrap-up (record + retire + issue
# close), don't silence the job.
#
# Instance automation, NOT shipped into the fresh-slate template (spawn spec
# rule 9c): it runs on a schedule and reads sibling-repo issue/PR state
# across the org, neither of which a freshly-spawned repo can satisfy.
# lifecycle_drift.yml stays the hermetic shipped guard; this file is the
# networked companion that must live outside it.

on:
schedule:
- cron: "23 6 * * *" # daily 06:23 UTC — offset to dodge top-of-hour load
workflow_dispatch:

permissions:
contents: read

jobs:
reconcile:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: registry state vs GitHub (closed issues / merged pr-open PRs still listed pending)
env:
GH_TOKEN: ${{ github.token }}
run: python3 scripts/lifecycle.py issues
13 changes: 0 additions & 13 deletions active.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,16 +51,3 @@
- current verdict: Heart's last committed dashboard (2026-08-11T05:51Z, i.e. BEFORE the green run) reads STALE score 65, listing `no release validation for current source` among its evidence gaps. That is the STALE tier behaving correctly — an evidence gap, not a fault, and this ingest is its remedy.
- do-not: do NOT re-dispatch `Release Integrate` to "refresh" this. The run is green and its artifact is live; a re-dispatch costs ~70 minutes of CI and proves nothing new. Only re-dispatch if the artifact has expired or main has moved.
- repos-none-claimed: this entry claims NO repos — deliberately on one line, NOT as 2-space ` - Repo` bullets, because `worktree_check_conflict` treats any such bullet as a live claim.
## version-stamp-sync-guards
- issue: https://github.com/PyAutoLabs/PyAutoHands/issues/235
- prompt: active/version_stamp_sync_and_release_sed_guards.md
- session: claude --resume d73342fb-c33f-4028-8741-30cbe0c856a3
- status: pr-open (https://github.com/PyAutoLabs/PyAutoLens/pull/700)
- worktree: ~/Code/PyAutoLabs-wt/version-stamp-sync-guards
- repos:
- PyAutoNerves: feature/version-stamp-sync-guards
- PyAutoArray: feature/version-stamp-sync-guards
- PyAutoFit: feature/version-stamp-sync-guards
- PyAutoGalaxy: feature/version-stamp-sync-guards
- PyAutoLens: feature/version-stamp-sync-guards
- PyAutoHands: feature/version-stamp-sync-guards

This file was deleted.

115 changes: 0 additions & 115 deletions active/autolens_workspace_developer/visualization_profiling_cluster.md

This file was deleted.

This file was deleted.

54 changes: 0 additions & 54 deletions active/version_stamp_sync_and_release_sed_guards.md

This file was deleted.

Loading
Loading