Skip to content

Codex/linkedin sther existing thread - #237

Open
iblmediaconsultancy wants to merge 31 commits into
trycompai:mainfrom
iblmediaconsultancy:codex/linkedin-sther-existing-thread
Open

iblmediaconsultancy wants to merge 31 commits into
trycompai:mainfrom
iblmediaconsultancy:codex/linkedin-sther-existing-thread

Conversation

@iblmediaconsultancy

Copy link
Copy Markdown

No description provided.

iblmediaconsultancy and others added 14 commits September 28, 2026 00:47
Preserve conversation-history guards, fail-closed execution checks, quota rollover inheritance, atomic reservations, failure release, and confirmed-send accounting.
Require stable exact recipient resolution before first-message history checks and preserve historical no-note first-touch lineage.
Persist verified opaque member IDs and prove LinkedIn slug equivalence across queue and execution.
Release LinkedIn profile/member identity equivalence fix.
Scope first-touch history checks to resolved LinkedIn composer surfaces
chore(main): release 1.5.5
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Harden profile identity and defer conversation matching until target composer resolution.
Preserve fail-closed identity matching while excluding the exact non-person LinkedIn heading.
Release metadata for LinkedIn profile identity heading fix.
@vercel

vercel Bot commented Oct 1, 2026

Copy link
Copy Markdown

@iblmediaconsultancy is attempting to deploy a commit to the Comp AI - PoC Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions
github-actions Bot changed the base branch from release to main October 1, 2026 16:18
@github-actions

github-actions Bot commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

Retargeted this onto main.

release is the default branch so that a plain clone runs the last tagged release, but nothing merges into it — it is fast-forwarded onto the tag by the Release workflow and that is all. Changes go to main, and reach release when a release is cut.

Nothing is wrong with your branch. If the diff now shows commits that are already on main, rebase and force-push:

git fetch origin main
git rebase origin/main
git push --force-with-lease

@iblmediaconsultancy
iblmediaconsultancy force-pushed the codex/linkedin-sther-existing-thread branch from d088839 to 5ba9c66 Compare October 3, 2026 18:32
@iblmediaconsultancy
iblmediaconsultancy force-pushed the codex/linkedin-sther-existing-thread branch from 5ba9c66 to 9660361 Compare October 3, 2026 18:33

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant