chore: update gptme-contrib submodule (77ea27e → ea26c28)

[TimeToBuildBob]

Summary

Updates gptme-contrib submodule from 77ea27e to ea26c28 (6 new commits).

What's included:

• fix(lessons): improve browser-verification keyword precision — removes overly broad "browser tool" keyword, reduces false-positive lesson matching
• feat(user-memories): add user memory extraction plugin — new plugin for extracting user memories
• fix(types): fix test imports and type annotations across packages
• fix(github): use REST API in is_item_open to save GraphQL quota
• feat(gptme-sessions): add per-tool-call timing and warning phrase detection
• docs(lessons): add progress-despite-blockers and stage-files-before-commit

Why

New agents created from this template will get the improved lessons and bug fixes. The browser-verification keyword precision fix is especially valuable — it was showing up as a marginally harmful lesson (LOO Δ=-0.096) due to overly broad matching on "browser tool".

Co-authored-by: Bob bob@superuserlabs.org

[greptile-apps]

Greptile Summary

This PR advances the gptme-contrib submodule pointer by 6 commits, delivering upstream improvements directly to new agents created from this template. The changes are entirely contained within the submodule — the template repo itself has no logic changes.

Key changes bundled in this update:

• fix(lessons): Removes the overly broad "browser tool" keyword from the browser-verification lesson, reducing false-positive lesson injection (previously measured at LOO Δ=-0.096).
• feat(user-memories): Adds a new plugin for extracting and persisting user memories across sessions.
• fix(types): Corrects test imports and type annotations across packages for cleaner type checking.
• fix(github): Switches is_item_open to the GitHub REST API to conserve GraphQL quota.
• feat(gptme-sessions): Adds per-tool-call timing instrumentation and warning phrase detection.
• docs(lessons): Adds two new lesson entries: progress-despite-blockers and stage-files-before-commit.

No issues were identified. The submodule URL in .gitmodules correctly points to https://github.com/gptme/gptme-contrib.git and the commit SHA is consistent with the PR description.

Confidence Score: 5/5

• This PR is safe to merge — it is a well-described, non-breaking submodule bump with no logic changes in the template repo.
• The change is a single submodule pointer update. All 6 upstream commits are bug fixes, additive features, or documentation — none are breaking changes. The PR description is thorough and cross-references the measured impact of the keyword precision fix. No issues were found.
• No files require special attention.

Important Files Changed

Filename	Overview
gptme-contrib	Submodule pointer advanced from 77ea27e to ea26c28, pulling in 6 upstream commits: keyword precision fix, new user-memory plugin, type annotation fixes, GitHub REST API migration, per-tool-call timing, and two new lessons. No issues found.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[gptme-agent-template] -->|references submodule| B[gptme-contrib @ 77ea27e\n(before)]
    A -->|updated pointer| C[gptme-contrib @ ea26c28\n(after)]

    C --> D[fix: browser-verification\nkeyword precision]
    C --> E[feat: user-memory\nextraction plugin]
    C --> F[fix: type annotations\nacross packages]
    C --> G[fix: GitHub REST API\nin is_item_open]
    C --> H[feat: per-tool-call\ntiming + warning detection]
    C --> I[docs: 2 new lessons\nprogress-despite-blockers\nstage-files-before-commit]

Loading

_{Last reviewed commit: "chore: update gptme-..."}