From 0de54d63c490fcf36a1ada74e0e7520d410a9346 Mon Sep 17 00:00:00 2001 From: jay Date: Sun, 2 Aug 2026 21:55:17 +0000 Subject: [PATCH] docs(tasks): remove artificial contributor backlog Remove the generated ready-work tasks and correct T010 so public issues are created only for accepted concrete work. Preserve the completed contributor foundation, Roadmap structure, and branch-protection state. --- docs/memory-bank/chat.md | 8 +- docs/tasks/README.md | 22 ++---- .../task.md | 34 ++++----- ...define-public-planning-and-task-linkage.md | 14 ++-- ..._05_complete-metadata-and-protect-main.md} | 75 ++++++------------- ...h-provider-implementation-specification.md | 65 ---------------- ...d-workspace-tools-configuration-example.md | 52 ------------- ...ve-reflection-metadata-consistency-test.md | 64 ---------------- 8 files changed, 57 insertions(+), 277 deletions(-) rename docs/tasks/T010_build-shared-github-contributor-foundation/tasks/{T010_05_publish-contributor-backlogs-and-protect-main.md => T010_05_complete-metadata-and-protect-main.md} (60%) delete mode 100644 docs/tasks/T011_refresh-provider-implementation-specification.md delete mode 100644 docs/tasks/T012_add-workspace-tools-configuration-example.md delete mode 100644 docs/tasks/T013_add-native-reflection-metadata-consistency-test.md diff --git a/docs/memory-bank/chat.md b/docs/memory-bank/chat.md index 671dd5f..48117e6 100644 --- a/docs/memory-bank/chat.md +++ b/docs/memory-bank/chat.md @@ -22,10 +22,10 @@ license-complete JVM/native release packaging. Shared community defaults in `codegeist-ai/.github`, personal profile content in `codegeist-ai/codegeist-ai`, the public Roadmap `https://github.com/users/codegeist-ai/projects/1`, T010 - coordination issue `codegeist-ai/codegeist#2`, and nine ready contributor issues - are published. All five repositories have complete metadata, private vulnerability - reporting, protected `main` branches, GitHub-detected `0BSD`, and 100 percent - community profiles. + coordination issue `codegeist-ai/codegeist#2`, and the issue/task linkage model + are published. No placeholder contributor backlog is retained. All five + repositories have complete metadata, private vulnerability reporting, protected + `main` branches, GitHub-detected `0BSD`, and 100 percent community profiles. - `.devcontainer` uses `.codegeist/.local.env` for ignored local runtime values and supports optional repository-specific Compose and image extensions under `.codegeist/`. Codegeist no longer checks in a mandatory NVIDIA extension, so diff --git a/docs/tasks/README.md b/docs/tasks/README.md index 2c05f56..d8b43fc 100644 --- a/docs/tasks/README.md +++ b/docs/tasks/README.md @@ -9,8 +9,8 @@ Codegeist also uses the account-wide [Code of Conduct](https://github.com/codegeist-ai/.github/blob/main/CODE_OF_CONDUCT.md), [Security Policy](https://github.com/codegeist-ai/.github/blob/main/SECURITY.md), and [Support Guide](https://github.com/codegeist-ai/.github/blob/main/SUPPORT.md). -The T010 account rollout is still open, so do not assume a shared policy or GitHub -setting has been published merely because its target link is recorded here. +The T010 account rollout is complete. Shared policy, CI, repository metadata, +private reporting, and branch-protection settings are published and verified. ## Statuses @@ -65,17 +65,9 @@ or merely open task records as ready work. rollout tracked by [codegeist-ai/codegeist#2](https://github.com/codegeist-ai/codegeist/issues/2). Shared policy and profile repositories, the Roadmap, source-repository pull - request checks, licensed kit releases, public ready-work issues, metadata, - private vulnerability reporting, branch protection, and the final - community-profile audit are complete. -- `T011_refresh-provider-implementation-specification.md` is a confirmed unmet - intermediate documentation task linked from - [issue #4](https://github.com/codegeist-ai/codegeist/issues/4). -- `T012_add-workspace-tools-configuration-example.md` is a confirmed unmet, - beginner-safe example/test task linked from - [issue #6](https://github.com/codegeist-ai/codegeist/issues/6). -- `T013_add-native-reflection-metadata-consistency-test.md` is a confirmed unmet - intermediate static-test task linked from - [issue #5](https://github.com/codegeist-ai/codegeist/issues/5). + request checks, licensed kit releases, metadata, private vulnerability reporting, + branch protection, and the final community-profile audit are complete. -These three tasks are publicly ready and labeled by contribution level and effort. +No contributor task is currently advertised as ready. New public tasks should be +created only after maintainers accept concrete repository work, not to populate the +Roadmap or meet an issue-count target. diff --git a/docs/tasks/T010_build-shared-github-contributor-foundation/task.md b/docs/tasks/T010_build-shared-github-contributor-foundation/task.md index ff9a3cb..524ded4 100644 --- a/docs/tasks/T010_build-shared-github-contributor-foundation/task.md +++ b/docs/tasks/T010_build-shared-github-contributor-foundation/task.md @@ -19,8 +19,9 @@ authoritative implementation specification for accepted work, whether that task uses the flat `TNNN_slug.md` form or nested `TNNN_slug/task.md` form. The completed foundation should let a contributor understand how the repositories -fit together, select the correct repository, find ready work, run that repository's -fast validation command, and submit a pull request with automatic feedback. +fit together, select the correct repository, find accepted ready work when it +exists, run that repository's fast validation command, and submit a pull request +with automatic feedback. ## Repository Scope @@ -41,8 +42,8 @@ This task also creates two account infrastructure repositories: root `README.md`. These account repositories provide community and discovery infrastructure. They do -not expand the set of source repositories that require implementation tasks, -normal source checks, ready issue backlogs, or protected source branches. +not require placeholder implementation tasks, normal source checks, or protected +source branches merely because they support the account. The rollout must include public repositories added before T010 completes. Future non-archived public repositories must follow the checklist established by this task. @@ -114,8 +115,8 @@ The source repositories already provide useful implementation foundations: check and pull-request CI to each source repository. - `tasks/T010_04_fix-onboarding-and-add-repository-examples.md` - explain the repository map, correct onboarding, and add repository-specific examples. -- `tasks/T010_05_publish-contributor-backlogs-and-protect-main.md` - publish work - across repositories, complete metadata, and protect each `main` branch. +- `tasks/T010_05_complete-metadata-and-protect-main.md` - complete metadata, + establish the accepted-work publication policy, and protect each `main` branch. ## Parent Acceptance Criteria @@ -146,9 +147,6 @@ The source repositories already provide useful implementation foundations: rejects force pushes and branch deletion. - Contributor-facing documentation explains repository ownership, source versus generated release branches, cross-repository changes, and where tasks belong. -- At least two ready public issues exist in each current source repository, with at - least eight total and at least one realistic `good first issue` per source - repository. - Repository descriptions, homepages, and topics are complete and consistent across the three source and two account infrastructure repositories. - All current repository community profiles reach the highest practical completion @@ -171,9 +169,8 @@ The source repositories already provide useful implementation foundations: - The Agent Kit and Devcontainer Kit generated `release` branches include the canonical license, and all source repositories pin those licensed releases. - The public [Codegeist Roadmap](https://github.com/users/codegeist-ai/projects/1) - contains the coordinating issue plus nine `Ready` issues across the three source - repositories. Each ready issue links its canonical local task and each task links - back to the issue. + provides the shared fields and status model. Issues enter it only after concrete + work is accepted; the rollout does not retain placeholder contributor work. - Every public `main` branch requires its proven CI context and a pull request, enforces linear history and conversation resolution, and rejects force pushes and deletion without requiring another maintainer's approval. @@ -187,8 +184,8 @@ The source repositories already provide useful implementation foundations: 3. Complete `T010_03` and prove each source repository's normal check before protecting its branch. 4. Complete `T010_04` and verify each source repository from a fresh checkout. -5. Complete `T010_05`, publish ready work across repositories, protect default - branches, and perform the final account-wide audit. +5. Complete `T010_05`, establish the accepted-work publication policy, protect + default branches, and perform the final account-wide audit. ## Non-Goals @@ -213,10 +210,11 @@ additionally requires an account-wide audit that confirms: - the public `.github` defaults are inherited where expected; - the root `README.md` in `codegeist-ai/codegeist-ai` renders the account profile; - each repository has local `0BSD` license detection; -- issue and task links include the repository and path and work in both directions; +- issue and task links include the repository and path and work in both directions + whenever accepted ready work is published; - each source repository's fast check passes from a fresh source checkout; - a test pull request receives the required CI check in each source repository; -- the Codegeist Roadmap project contains work from all current source repositories; +- the Codegeist Roadmap project provides the intended fields and status model; - all current `main` branches have the intended protection without impossible self-approval requirements; - private vulnerability and conduct-reporting routes are usable; and @@ -235,7 +233,7 @@ additionally requires an account-wide audit that confirms: - Shared kit changes must start on each kit's source `main`, pass that repository's tests, build its generated `release` branch through the existing workflow, and update consuming gitlinks separately. -- Prefer small public issues with observable acceptance criteria and explicit - repository ownership. +- Create public issues only for accepted concrete work with observable acceptance + criteria and explicit repository ownership. - Treat permission, workspace-containment, secret-redaction, release mutation, and other security-sensitive work as maintainer-led rather than beginner work. diff --git a/docs/tasks/T010_build-shared-github-contributor-foundation/tasks/T010_02_define-public-planning-and-task-linkage.md b/docs/tasks/T010_build-shared-github-contributor-foundation/tasks/T010_02_define-public-planning-and-task-linkage.md index 0dbe332..9587e53 100644 --- a/docs/tasks/T010_build-shared-github-contributor-foundation/tasks/T010_02_define-public-planning-and-task-linkage.md +++ b/docs/tasks/T010_build-shared-github-contributor-foundation/tasks/T010_02_define-public-planning-and-task-linkage.md @@ -71,9 +71,9 @@ Account Project -> repository Issue -> canonical local task file -> branch -> PR how Project, issue, task, and PR states stay synchronized. - Existing historical task records are not presented as ready public work. - The account-level Project can filter and group work by repository. -- A sample ready issue/task pair in each current source repository proves - bidirectional links before public backlog publication. -- A cross-repository sample proves that coordinating links do not replace local +- When a source repository has accepted ready work, a real issue/task pair proves + bidirectional links. The rollout does not create sample or placeholder work. +- Real cross-repository work uses coordinating links without replacing local implementation tasks. - Shared labels have the same meaning across repositories without requiring every repository to use irrelevant area labels. @@ -104,8 +104,8 @@ Account Project -> repository Issue -> canonical local task file -> branch -> PR - `codegeist-ai/codegeist-ai` personal profile repository - Common repository labels - Repository-specific milestones only where useful -- One sample issue/task pair per source repository -- One sample cross-repository relationship +- Real issue/task pairs and cross-repository relationships when accepted work + requires them ## Non-Goals @@ -121,6 +121,6 @@ Account Project -> repository Issue -> canonical local task file -> branch -> PR - Open the new-issue and pull-request flows in each current source repository. - Verify shared inheritance and every justified local override. -- Inspect Project repository/status fields and sample relationships. -- Confirm all sample issue/task links in both directions. +- Inspect Project repository/status fields. +- Confirm issue/task links in both directions when accepted ready work exists. - Run each changed repository's documentation checks and `git diff --check`. diff --git a/docs/tasks/T010_build-shared-github-contributor-foundation/tasks/T010_05_publish-contributor-backlogs-and-protect-main.md b/docs/tasks/T010_build-shared-github-contributor-foundation/tasks/T010_05_complete-metadata-and-protect-main.md similarity index 60% rename from docs/tasks/T010_build-shared-github-contributor-foundation/tasks/T010_05_publish-contributor-backlogs-and-protect-main.md rename to docs/tasks/T010_build-shared-github-contributor-foundation/tasks/T010_05_complete-metadata-and-protect-main.md index 4a06947..4387dc9 100644 --- a/docs/tasks/T010_build-shared-github-contributor-foundation/tasks/T010_05_publish-contributor-backlogs-and-protect-main.md +++ b/docs/tasks/T010_build-shared-github-contributor-foundation/tasks/T010_05_complete-metadata-and-protect-main.md @@ -1,4 +1,4 @@ -# T010_05 Publish Contributor Backlogs And Protect Main +# T010_05 Complete Metadata And Protect Main Parent: `T010_build-shared-github-contributor-foundation` @@ -8,22 +8,19 @@ Roadmap: https://github.com/users/codegeist-ai/projects/1 ## Goal -Finish the account-wide contributor rollout by publishing real scoped work in every -current source repository, completing discovery metadata, and protecting each -`main` branch with its proven CI gate. +Finish the account-wide contributor rollout by defining how accepted work is +published, completing discovery metadata, and protecting each `main` branch with +its proven CI gate. ## Scope - Set accurate descriptions, homepages, and topics for `.github`, `codegeist-ai`, `codegeist`, `codegeist-agent-kit`, and `codegeist-devcontainer-kit`. -- Populate the account-level Codegeist Roadmap Project with work from every current - source repository. - Add repository, status, area, effort, and contribution-level Project fields. -- Create at least two ready public issues in each current source repository, at - least eight meaningful issues overall across the three source repositories, and - at least one realistic `good first issue` in each source repository. -- Create or link the matching repository-local task specification for every issue - marked `Ready`. +- Publish repository Issues and Roadmap items only after maintainers accept concrete + work for implementation. +- Create or link a matching repository-local task specification for every accepted + issue marked `Ready`. - Use `help wanted` only for sufficiently specified intermediate work. - Keep security, permission, secret handling, generated-release mutation, and broad architecture decisions maintainer-led. @@ -35,39 +32,15 @@ current source repository, completing discovery metadata, and protecting each is created. - Run a final account-wide public-state and community-profile review. -## Candidate Issue Areas +## Work Publication Policy -Confirm each candidate is still unmet before publishing it. - -### Codegeist - -- Split `CodegeistLocalToolsTest` into focused per-tool test classes. -- Add native-image reflection metadata consistency coverage. -- Add architecture-boundary tests for provider, MCP, chat, and tool packages. -- Add a Maven Wrapper and enforce supported Java and Maven versions. -- Refresh stale provider implementation specifications against current architecture. -- Design maintainer-led permission and workspace-containment behavior. - -### Codegeist Agent Kit - -- Validate cross-references between commands, rules, skills, plugins, and config. -- Expand release-bundle manifest checks for required and forbidden paths. -- Add focused schema or structural validation for shared OpenCode configuration. -- Improve contributor documentation for generic versus repository-local behavior. -- Audit mutable tool/version references and propose reproducible pins where useful. - -### Codegeist Devcontainer Kit - -- Add focused shell syntax and generated-release manifest checks. -- Document image-extension, Compose-override, and consuming-repository boundaries. -- Add deterministic tests for release-copy path completeness. -- Audit mutable installer and package inputs and propose reproducibility improvements. -- Improve contributor guidance for browser, Docker, worktree, and environment setup. - -The first `good first issue` in each repository should come from documentation, -small deterministic tests, or safe structural validation. Do not label runtime -security policy, release publication, broad image builds, or provider work as -beginner work. +- Do not require a minimum number of open Issues, Roadmap items, or beginner tasks. +- Do not create work only to populate the Roadmap or demonstrate the contribution + workflow. +- Open an Issue after maintainers accept a concrete problem and repository owner. +- Add `status:ready` only after scope and verification are sufficiently specified. +- Use `good first issue` only for genuinely beginner-safe work, not to satisfy an + account-wide quota. ## Metadata Targets @@ -86,12 +59,11 @@ beginner work. - Every current public repository has a non-empty accurate description, homepage where applicable, and focused topics. -- The account Roadmap contains ready work from all current source repositories. -- Each current source repository has at least two ready scoped issues and one - realistic `good first issue`. -- At least eight issues are open across the three source repositories and no issue - exists only to meet the count. -- Every ready issue links a canonical local task file, and the task links back. +- The account Roadmap provides the intended repository, status, area, effort, and + contribution-level fields. +- No Issue or task exists only to meet a rollout count or populate a Project view. +- Every accepted ready issue links a canonical local task file, and the task links + back. - Project views can group work by repository and status. - Each current source repository's `main` requires its proven CI check and rejects force pushes and deletion. @@ -115,7 +87,6 @@ beginner work. - `codegeist-ai/.github/README.md` when documenting default-community ownership - Each source repository's `README.md` - Each source repository's local task guide -- New repository-local task specifications for ready issues - Relevant repository memory files - `docs/tasks/T010_build-shared-github-contributor-foundation/` @@ -139,8 +110,8 @@ beginner work. ## Verification -- Use GitHub UI or authenticated `gh` queries to verify metadata, issue labels, - Project membership, task links, and branch rules in every current repository. +- Use GitHub UI or authenticated `gh` queries to verify metadata, Project fields, + accepted-work linkage, and branch rules in every current repository. - Open a disposable test pull request in each source repository before enabling its required check. - Verify that failing CI blocks merge and successful CI permits the sole-maintainer diff --git a/docs/tasks/T011_refresh-provider-implementation-specification.md b/docs/tasks/T011_refresh-provider-implementation-specification.md deleted file mode 100644 index 124d3ea..0000000 --- a/docs/tasks/T011_refresh-provider-implementation-specification.md +++ /dev/null @@ -1,65 +0,0 @@ -# T011 Refresh Provider Implementation Specification - -Status: open - -Public Tracking: https://github.com/codegeist-ai/codegeist/issues/4 - -Contribution Level: intermediate (`help wanted` candidate, not `good first issue`) - -Effort: medium - -Confirmed Unmet: on 2026-08-02, -`docs/developer/specification/llm-provider-implementation.md` still models -`CodegeistConfig` as `@ConfigurationProperties`, puts provider config in the -planned `CodegeistChatRequest`, treats Ollama as the only implemented adapter, and -describes implemented tool/session behavior as future work. - -## Goal - -Refresh the provider implementation specification so it clearly separates current -Ollama/OpenAI runtime behavior from future provider guidance and no longer teaches -obsolete pre-implementation contracts. - -## Acceptance Criteria - -- The specification no longer describes `CodegeistConfig` as a Spring - `@ConfigurationProperties` provider map. -- The documented `CodegeistChatRequest` excludes provider configuration and matches - the current request/turn split. -- Current Ollama and OpenAI adapters, provider-owned default models, tool-aware - message flow, agent-loop dispatch, and session/harness ownership are described - accurately. -- Statements that only applied before OpenAI, tools, and resumable sessions were - implemented are removed or explicitly labeled historical/future. -- Provider categories and the no-provider-call default remain aligned with - `docs/tests/provider-feature-tests.md` and the canonical `task cli:check` gate. -- Diagrams render and distinguish implemented classes from illustrative future - provider classes. - -## Files - -- `docs/developer/specification/llm-provider-implementation.md` -- `docs/developer/architecture/provider-configuration.md` only if a cross-link or - current-state correction is required -- `docs/tests/provider-feature-tests.md` only if a stale shared statement is found - -## Non-Goals - -- Do not add or change Java runtime behavior, providers, models, dependencies, or - configuration fields. -- Do not make provider calls or require credentials. -- Do not redesign the provider architecture. -- Do not expand this into a general documentation rewrite; the contributor must - understand the current config, chat, agent-loop, and session boundaries, so this - is not beginner-safe work. - -## Verification - -```bash -task cli:check -git --no-pager diff --check -``` - -Review the final document against the current classes under -`app/codegeist/cli/src/main/java/ai/codegeist/app/chat` and -`app/codegeist/cli/src/main/java/ai/codegeist/app/config`. diff --git a/docs/tasks/T012_add-workspace-tools-configuration-example.md b/docs/tasks/T012_add-workspace-tools-configuration-example.md deleted file mode 100644 index a044df0..0000000 --- a/docs/tasks/T012_add-workspace-tools-configuration-example.md +++ /dev/null @@ -1,52 +0,0 @@ -# T012 Add Workspace And Local Tool Configuration Example - -Status: open - -Public Tracking: https://github.com/codegeist-ai/codegeist/issues/6 - -Contribution Level: beginner (`good first issue` candidate) - -Effort: small - -Confirmed Unmet: on 2026-08-02, `examples/` has parser-checked Ollama, OpenAI, -and MCP files but no example for the implemented `workspace:` and `tools:` roots. - -## Goal - -Add one credential-free example for the implemented workspace, edit-preview, and -shell-timeout settings and keep it on the same production-parser test path as the -existing contributor examples. - -## Acceptance Criteria - -- `examples/codegeist.tools.yml` contains only implemented `workspace:` and - `tools:` fields. -- The example uses a relative workspace, keeps the directory guard enabled, and - demonstrates bounded edit-preview and positive shell-timeout settings. -- The example contains no credentials, provider, MCP process, command prefix, or - executable command. -- `examples/README.md` explains that parsing the file has no tool side effects and - that running Codegeist tools can still read, mutate, or execute on the host. -- `CodegeistExamplesTest` includes the new file and loads it through - `CodegeistConfigService` without provider, MCP, Docker, or tool calls. - -## Files - -- `examples/codegeist.tools.yml` -- `examples/README.md` -- `app/codegeist/cli/src/test/java/ai/codegeist/app/config/CodegeistExamplesTest.java` - -## Non-Goals - -- Do not change production configuration classes or tool behavior. -- Do not disable the workspace directory guard or present any setting as a - sandbox, permission system, or secret-redaction mechanism. -- Do not add a provider or MCP client to this example. - -## Verification - -```bash -task cli:test-jvm TEST=CodegeistExamplesTest -DOCKER_HOST=tcp://127.0.0.1:1 task cli:check -git --no-pager diff --check -``` diff --git a/docs/tasks/T013_add-native-reflection-metadata-consistency-test.md b/docs/tasks/T013_add-native-reflection-metadata-consistency-test.md deleted file mode 100644 index 1d8b787..0000000 --- a/docs/tasks/T013_add-native-reflection-metadata-consistency-test.md +++ /dev/null @@ -1,64 +0,0 @@ -# T013 Add Native Reflection Metadata Consistency Test - -Status: open - -Public Tracking: https://github.com/codegeist-ai/codegeist/issues/5 - -Roadmap: https://github.com/users/codegeist-ai/projects/1 - -Contribution Level: intermediate (`help wanted` candidate, not `good first issue`) - -Effort: medium - -Confirmed Unmet: on 2026-08-02, -`app/codegeist/cli/src/main/resources/META-INF/native-image/reflect-config.json` -manually lists config models, local-tool input records, and session-store types, -but no JVM test parses that file or detects duplicate, missing, or stale class -registrations. - -## Goal - -Add deterministic JVM coverage that keeps Codegeist-owned native reflection -metadata aligned with the classes reached through Jackson config mapping, local -tool input parsing, and session-store serialization. - -## Acceptance Criteria - -- A focused JVM test parses `reflect-config.json` through a real JSON parser. -- The test rejects duplicate `name` entries and reports the duplicate class names. -- Every configured Codegeist class name resolves through the test runtime - classpath, so renamed or removed classes fail with the stale metadata entry. -- The test defines and checks the current required Codegeist-owned reflection set: - concrete config root/payload and provider/MCP dispatch types, local-tool input - records passed to Jackson, and session aggregate/part types serialized by the - session store. -- Missing required entries fail with a message that names every missing class. -- Assertions cover required constructor, field, and public-method access flags - where the current Jackson/native contract depends on them. -- The focused test and `task cli:check` pass with provider category `none`, no - Docker access, and no provider or MCP calls. - -## Files - -- `app/codegeist/cli/src/main/resources/META-INF/native-image/reflect-config.json` -- A focused test under `app/codegeist/cli/src/test/java/ai/codegeist/app/` -- Native/reflection documentation only if the test establishes a maintenance - contract not already documented - -## Non-Goals - -- Do not build a native executable; static JVM consistency is sufficient for this - task. -- Do not replace GraalVM metadata generation or prove third-party dependency - reachability. -- Do not add broad classpath scanning, architecture-test frameworks, or production - reflection registries. -- Do not add or remove runtime features merely to satisfy the metadata test. - -## Verification - -```bash -task cli:test-jvm TEST= -DOCKER_HOST=tcp://127.0.0.1:1 task cli:check -git --no-pager diff --check -```