Repository navigation
Conversation
Partial work saved after the session limit interrupted the agent. A follow-up commit on this branch completes and cleans it up before review. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…script scripts/github_metadata.py parses public_metadata in repository-lifecycle.yml with a strict parser for the small YAML subset the registry uses, so the profile check needs no YAML package. It checks the formats GitHub enforces (topic names and count, https websites, six pins at most) plus our short-copy rules (ASCII only, no dashes, 160 characters at most). render-apply prints a bash script with the exact gh commands that apply the registry. It runs as a dry run by default, checks every command, reads GitHub back after --apply, and prints a success line only when every value matches. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ript Rewrite the profile headline to match the launcher README's opening line. Keep MCP out of the pinned agent description, say what the engine does without implying every run checks the record, and describe the private Cloud and website repositories in plain words. The header comment now names the apply script instead of a command that didn't exist. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The profile now opens with one plain sentence, a faxed-referral before and after with sourced baseline times, the five ways a run can end, and two paths: hand off a workflow, or run the engine yourself. Developer content, the product surfaces, evidence, research, and contribution notes follow. The fault-test numbers now use the claim of record. A screen-only check passed 54 of the 72 runs that left the record wrong (75.0%); the old text paired that rate with 54 of 90 runs. The over-halt count sits beside it, and every figure on the page is bound to its artifact again. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
check_profile.py now reads public_metadata through github_metadata.py and checks that: - the pins are the five product repositories plus the EHR Integration Directory, and no pin is a Research, Labs, Experimental, or retired repo - every described repository is a product repository or has a lifecycle - product and pinned descriptions carry no static lifecycle label, while Experimental, Research, Labs, and Superseded descriptions open with theirs - the organization description, profile headline, pinned descriptions, and the profile's business section avoid the internal vocabulary - the profile opens with the registry's headline, keeps business sections before developer sections, uses the launcher's quickstart, and never prints 54 of 90 - .overhaul/APPLY.sh matches what the registry renders .overhaul/APPLY.sh is the rendered script for this change. A read-only --verify run against GitHub on 2026-10-09 listed 45 of 90 values that differ today, the six current pins, and six public forks that have no registry entry. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… script The apply-script tests run a rendered script against a fake gh that keeps GitHub state in a file. They check that a dry run calls nothing, that one failed write or one unreadable value fails the run without a success line, that pins left for an owner exit 2, and that a non-owner or signed-out account changes nothing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The root README replaced its list of hand-copied settings with four steps that use the rendered apply script: review the dry run, apply, pin by hand, and verify. REPOSITORY_LIFECYCLE.md lists the EHR Integration Directory under Support, says the registry also holds the public GitHub metadata, and uses sentence-case headings. Heading anchors don't change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…rallel Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The pins check passes a GraphQL query that names $org itself, so the single quotes are deliberate. Say so in the script and silence SC2016. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
An agent stopped at the weekly usage limit on 2026-10-09 with these edits uncommitted. They are unreviewed and may be half-applied; the next resume judges them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Keep the interrupted edits and finish them: - The --break-it run ends with "Check the record". Flow records that run as RECONCILIATION_REQUIRED, so the profile now names the plain result. - The OpenEMR field test says it used a development build of Flow 0.1.0, which matches the benchmark's own method note. Rewrap that paragraph. - Name the customer story in its link text instead of "written up here". - State the fault test's scope as two plain sentences. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The fault test's 72 wrong-record runs include two classes the old list left out: a stale write that deleted the patient's other records, and a stray billing row. The next paragraph already names the billing write, so the list now covers it. The counts are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Remove the case study link from the profile and drop "customer stories" from the openadapt-web description in the registry. Render the apply script again from the registry. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
"No OpenAdapt customer has measured" presumes there are customers. Use the launcher README's wording, which states the same limit without that presumption. Co-Authored-By: Claude Opus 5.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
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.
This rewrites the OpenAdaptAI organization profile so that a business reader learns from the first screen what OpenAdapt does, what changes for their team, and how to start. It corrects the fault-test figure: the screen-only check passed 54 of the 72 runs that left the record wrong, not "54 of 90". It also makes
repository-lifecycle.ymlthe source of truth for the GitHub settings that visitors see, and it adds a script that an owner runs to apply them after merge.What changes
Organization profile (
profile/README.md)openadapt quickstart --break-ityourself. The billing-audit case study is withdrawn, so the profile doesn't link to it.pip install --upgrade 'openadapt[browser]'andopenadapt quickstarttopip install --upgrade openadaptandopenadapt quickstart --break-it. In the current release (1.16.0), the baseopenadaptpackage already includes browser support, and the CLI has--break-it.Registry and checks
repository-lifecycle.ymlholds the organization description and website, the headline, the six pins, and a description, website, and topic list for 29 repositories.ehr-integration-directoryreplacesopenadapt-evalsamong the pins and joins Support.public_metadata.repository_descriptions(description only) is replaced bypublic_metadata.repositories(description, homepage, and topics).schema_versionstays 2. A code search of the organization found no other reader of the old key, and the lifecycle validator reads only thelifecycleandpublic_surfacesgroups.scripts/github_metadata.pyreads the registry without a YAML dependency and enforces GitHub's topic and pin limits and short-copy rules.scripts/check_profile.pychecks the pins, lifecycle labels, plain terms in business-facing copy, section order, the headline, the absence of "54 of 90", and that the apply script matches the registry.benchmark-claims.jsonbinds the 12 figures on the new profile to pinned artifacts and drops the entries for the removed figures.README.mdreplaces the manual list of GitHub settings with the apply-script steps.REPOSITORY_LIFECYCLE.mdaddsehr-integration-directoryto Support and uses sentence-case headings.Apply script (
.overhaul/APPLY.sh, rendered from the registry)ghcommand and calls nothing.--applyrequires an organization owner, reports each failed command, and then compares every value on GitHub with the registry.--verifyonly reads. It exits 0 only when everything matches, and 2 when only the hand-set pins remain.Screenshots
After: developers get a table that maps each plain result to the engine outcome it comes from.
The read-only check of live GitHub settings shows today's descriptions and pins next to the values the apply script sets.
How it was tested
These were run on 2026-10-09:
python3 -m unittest discover -s tests -p 'test_*.py': 400 tests pass. The 30 new tests cover the registry parser, the profile rules, and the apply script, and 11 of them run the script against a fakegh.python3 scripts/check_profile.py: 29 descriptions, 6 pins, and 45 Markdown links validated.python3 scripts/validate_evidence_registry.py: valid.python3 scripts/check_benchmark_claims.py --online --allow-recorded-drift: 12 figures bound, and all 4 upstream artifacts matched.shellcheck,bash -n, andruff checkon the changed files: clean.--verifyagainst GitHub exited 1 as expected: 45 of 90 values differ today, and the pins differ.After merging
Merging updates the profile. GitHub settings change only when an owner applies them:
.overhaul/APPLY.shand review the 59 commands.gh auth refresh -s admin:org,repoas an owner of OpenAdaptAI..overhaul/APPLY.sh --apply. It also sets the privateopenadapt-webandopenadapt-clouddescriptions, and an empty website or topic list clears that field..overhaul/APPLY.sh --verifyand confirm that it exits 0.Decisions for the owner:
ehr-integration-directorybelongs in Support.The launcher README in
OpenAdaptAI/OpenAdapt(branchfeat/business-clarity-launcher) uses the same headline. No merge order is required. If its first line changes, updateprofile_headlinein the registry and the first bold line of the profile. The profile check fails until the two match.🤖 Generated with Claude Code