Roll out the mongodb extension per AGENTS.md (tracking issue, branch, PR) #149

New issue

Closed

opened 2026-08-31 22:07:50 +00:00 by david · 1 comment

david commented

2026-08-31 22:07:50 +00:00

Owner

Summary

Ship the completed mongodb extension per the repo's AGENTS.md conventions: tracking issue (label feature), branch feature/issue-<N>/mongodb-extension, commits prefixed issue-<N>: , and a PR titled issue-<N>: <title> with body Closes #<N> — then hand the merge decision to the repo owner.

Background

Depends on: #148

Per AGENTS.md (this repo): feature work is issue-number-driven. A tracking issue labeled feature anchors the branch name, commit prefixes, and PR. The issues created from the implementation plan (including this one) are the tracked work items for the feature; the tracking issue referenced here is the feature's umbrella issue. Merging is the repo owner's decision — the implementer opens the PR and asks whether to merge; never merge on your own initiative. PRs are squash-merged and the source branch deleted when the owner approves.

Implementation Details

Tracking issue — ensure a feature-labeled tracking issue for the mongodb extension exists (e.g. titled "MongoDB extension: read-only query tools"). If one already exists (for example created alongside the plan's issues), reuse it; otherwise create it. Use its number as <N>.
Branch — create feature/issue-<N>/mongodb-extension from main.
Commits — commit the extension work (all of extensions/mongodb/, the root manifest/README changes) with messages prefixed issue-<N>: <summary>.
PR — push and open a PR titled issue-<N>: MongoDB extension (or similar), body Closes #<N> plus a summary of what was built (tools, config, tests, docs).
Merge decision — ask the repo owner whether to merge. If approved, squash-merge and delete the source branch. If not, leave the PR open.

Acceptance Criteria

Tracking issue for the feature exists with label feature (reused or created).
Branch is named feature/issue-<N>/mongodb-extension.
Commit messages are prefixed issue-<N>: .
PR is open with title issue-<N>: MongoDB extension and body Closes #<N>.
The merge decision is explicitly handed to the repo owner — the PR is not merged on the implementer's own initiative.

Test Plan

git log --oneline -10          # commits prefixed issue-<N>:
git branch --show-current      # feature/issue-<N>/mongodb-extension

Confirm the PR is visible on the host with the correct title/body, and that no merge was performed without owner approval.

## Summary Ship the completed mongodb extension per the repo's AGENTS.md conventions: tracking issue (label `feature`), branch `feature/issue-<N>/mongodb-extension`, commits prefixed `issue-<N>: `, and a PR titled `issue-<N>: <title>` with body `Closes #<N>` — then hand the merge decision to the repo owner. ## Background **Depends on:** #148 Per AGENTS.md (this repo): feature work is issue-number-driven. A tracking issue labeled `feature` anchors the branch name, commit prefixes, and PR. The issues created from the implementation plan (including this one) are the tracked work items for the feature; the tracking issue referenced here is the feature's umbrella issue. **Merging is the repo owner's decision** — the implementer opens the PR and *asks* whether to merge; never merge on your own initiative. PRs are squash-merged and the source branch deleted when the owner approves. ## Implementation Details 1. **Tracking issue** — ensure a `feature`-labeled tracking issue for the mongodb extension exists (e.g. titled "MongoDB extension: read-only query tools"). If one already exists (for example created alongside the plan's issues), reuse it; otherwise create it. Use its number as `<N>`. 2. **Branch** — create `feature/issue-<N>/mongodb-extension` from `main`. 3. **Commits** — commit the extension work (all of `extensions/mongodb/`, the root manifest/README changes) with messages prefixed `issue-<N>: <summary>`. 4. **PR** — push and open a PR titled `issue-<N>: MongoDB extension` (or similar), body `Closes #<N>` plus a summary of what was built (tools, config, tests, docs). 5. **Merge decision** — ask the repo owner whether to merge. If approved, squash-merge and delete the source branch. If not, leave the PR open. ## Acceptance Criteria - [ ] Tracking issue for the feature exists with label `feature` (reused or created). - [ ] Branch is named `feature/issue-<N>/mongodb-extension`. - [ ] Commit messages are prefixed `issue-<N>: `. - [ ] PR is open with title `issue-<N>: MongoDB extension` and body `Closes #<N>`. - [ ] The merge decision is explicitly handed to the repo owner — the PR is not merged on the implementer's own initiative. ## Test Plan ```bash git log --oneline -10 # commits prefixed issue-<N>: git branch --show-current # feature/issue-<N>/mongodb-extension ``` Confirm the PR is visible on the host with the correct title/body, and that no merge was performed without owner approval.

david added this to the MongoDB: M7 - Reconciliation & Rollout milestone

2026-08-31 22:07:50 +00:00

david added the

feature

ready

labels

2026-08-31 22:07:50 +00:00

david removed the

feature

label

2026-09-14 23:22:41 +00:00

david commented

2026-09-18 06:54:11 +00:00

Author

Owner

Closing: the rollout was completed incrementally rather than via a single PR.

All implementation issues #133–#148 (including dependency #148) are closed, and their per-issue PRs (#152–#164) are all squash-merged into main.
extensions/mongodb/ is complete on main: mongo_find, mongo_count, mongo_list_collections tools plus client/env/errors/serialize/defaults, unit tests (98 passing), README, DESIGN.md, IMPLEMENTATION_PLAN.md.
Registered in the root package.json manifest (mongodb ^7.6.0) and documented in the root README extension table + setup section.
The single rollout branch/PR prescribed here would be an empty diff — there is nothing left to merge. The stale local branch feature/issue-149/roll-out-the-mongodb-extension-per-agents-md-track (0 commits ahead of main, never pushed) has been deleted.

Closing: the rollout was completed incrementally rather than via a single PR. - All implementation issues #133–#148 (including dependency #148) are closed, and their per-issue PRs (#152–#164) are all squash-merged into `main`. - `extensions/mongodb/` is complete on `main`: `mongo_find`, `mongo_count`, `mongo_list_collections` tools plus client/env/errors/serialize/defaults, unit tests (98 passing), README, DESIGN.md, IMPLEMENTATION_PLAN.md. - Registered in the root `package.json` manifest (`mongodb ^7.6.0`) and documented in the root README extension table + setup section. - The single rollout branch/PR prescribed here would be an empty diff — there is nothing left to merge. The stale local branch `feature/issue-149/roll-out-the-mongodb-extension-per-agents-md-track` (0 commits ahead of main, never pushed) has been deleted.

david closed this issue

2026-09-18 06:54:14 +00:00