chore: advance the four task lists against what landed - #87
Merged
Conversation
osapi's conversion (osapi-io/osapi#450) closes the task that blocked three other changes: it was the only repository with neither a root CONTRIBUTING.md nor an AGENTS.md. Verification found five things the task lists asserted but nobody had checked. Four now pass: the required files, the absent docs/contributing and docs/development, the archived deprecated repositories, and the react module already taking its directory as configuration. One did not -- specs/LICENSE carried a differently titled and wrapped variant, replaced here with the canonical copy. Four remain open with the reason recorded rather than the box ticked: redocly is invoked but undeclared, three mocks are hand-written, go is pinned locally and floating in CI, and the export_test.go audit has not been done. Task 6.1 is dropped: osapi-io-taskfiles is archived and cannot be pushed to, and the archived state is accepted as the deprecation signal. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Thank you for contributing to this project! 😊🕹️ |
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.
Works the task lists for all four in-flight changes against what is now true, following the keystone landing in osapi-io/osapi#450.
What the conversion closed
osapiwas the only repository with neither a rootCONTRIBUTING.mdnor anAGENTS.md. That single task blocked four others across three changes, all now checked:standardize-repository-layoutosapispecify-agent-tool-invocationosapiAGENTS.mdspecify-go-code-standardsCLAUDE.mddrops Code Standardsspecify-documentation-homesspecify-documentation-homesCONTRIBUTING.mdWhat verification found
Five verification tasks asserted things nobody had checked. Four pass and are now recorded with their evidence: required files present in all seven repositories, no
docs/contributing.mdordocs/development.mdanywhere, all three deprecated repositories archived, and thereactmodule already takingreact_diras configuration (6a.1/6a.2 were done and unticked).One failed.
specs/LICENSEwas not byte-identical — it carriedMIT Licenserather thanThe MIT Licenseand a different line wrap. This PR replaces it with the canonical copy.What stays open, and why
Four tasks keep their reason instead of their tick:
specify-agent-tool-invocation3.2 —osapi'sgeneraterecipe invokesredocly, declared nowhere. Not a one-line fix: mise supplies 2.46.1 against 2.19.1 on the developer's path, and the two quote YAML scalars differently, so the committed combined spec and both generated SDKs change the first time anyone runsjust generate. Nothing in CI runsgenerate, so the drift is invisible until someone does.specify-go-code-standards3.4 — three hand-written mocks remain (gohai,osapi-orchestrator,osapi). Two of the three repositories declare no mocking library, so this needs a decision, not a regeneration.specify-go-code-standards3.6 —gohaiandosapi-orchestratorpoint at the capability and restate it. Removing the restatements reverses a choice made deliberately at conversion time.standardize-repository-layout5.2/5.3/7.6 —gois1.25in.mise.tomlandstablein every workflow, across all five Go repositories. They agree today and diverge when 1.26 ships. The requirement's own logic points atgo = "latest"locally rather than pinning CI, which changes the toolchain every developer builds with.Task 6.1 dropped
osapi-io-taskfilesis archived and cannot be pushed to. Of the two ways out the task named, the archived state is accepted as the deprecation signal — GitHub already marks it read-only, which is the half of the requirement a reader sees.just testpasses (10/10).🤖 Generated with Claude Code