Repository navigation
STATUS.md: make the snapshot true again - #51
Merged
Merged
Conversation
Fourteen merges left the file describing a repository that no longer exists, and its whole job is to be accurate at HEAD: * six closed issues were listed as open work -- #1 and #4 from the split, and #24, #25, #26 and #35 from yesterday. The open list is now what `gh issue list` actually returns. * the inventory said "3 labs in the README tables"; the tables carry six rows with pages, across four areas. * `data/` was described as four scripts. It is eight, including es_client.py and idmap/, so each is named with what it does rather than listed. * `_base/` had gained two services with no mention: the secured Elasticsearch on 9201 that the authenticated path is verified against, and the pinned migration target on 8124. * the CI line omitted the `terraform` job, and the pages line did not say where the site is or that a page now sits at its own repository path. No issue for this one: STATUS.md going stale is the file being out of date rather than work someone planned, and the repository's rule is to keep the snapshot current rather than to track it. Say so if you would rather it had one. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fourteen merges left
STATUS.mddescribing a repository that no longer exists, and beingaccurate at
HEADis the file's entire job.gh issue listreturns: #2, #3, #5, #19/#21, #32, #33, #34, #41labs/, two inworkshops/, plusotel-profiles/andclickstack-config/data/described as four scriptsplan.py,mapping_to_ddl.py,export.py,load.sh,run.py,parity_checks.py,es_client.py,idmap/_base/with no mention of its new servicesterraformjob; pages line not saying where the site is/labs/elastic-migration/)As of 2026-09-29As of 2026-09-30Also drops the
#24–#26reference in the version table, which pointed at closed issues toexplain why Elasticsearch is pinned at 8.17.0, and says the reason directly instead.
No issue for this one.
STATUS.mdgoing stale is the file being out of date rather thanwork someone planned, and
AGENTS.md's rule is to keep the snapshot current instead oftracking it as a to-do. Say so if you would rather it had one.
Every claim in the new text is something verified in the sessions that produced it; nothing
here adds a
Verified on …line.🤖 Generated with Claude Code