Skip to content

feat(specs/skills): trinity/connect-accounts - #4600

Closed
gHashTag wants to merge 3 commits into
masterfrom
feat/skill-connect-accounts
Closed

gHashTag wants to merge 3 commits into
masterfrom
feat/skill-connect-accounts

Conversation

@gHashTag

@gHashTag gHashTag commented Sep 22, 2026 •

Copy link
Copy Markdown
Owner

This adds the canonical .t27 card for the trinity skill connect-accounts: signing a person into their own accounts through their remote browser, pressing SSO buttons by label, covering every sign-in case, and reporting only what the tools did.

🤖 Generated with Claude Code

Refs #3544 (skills as first-class .t27 cards under specs/skills/; this adds one more card).

…hrough their own remote browser

The canonical card for the trinity skill connect-accounts (published on
t27.ai from gHashTag/trinity). Written from two live runs on 2026-09-22:
LinkedIn through Google and X through Google, which needed pop-ups
allowed. English only; no spec is declared yet (unbound, stated).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-09-22 12:39:04 UTC

Summary

Status Count
Total Open PRs 28
PRs with Failing Checks 25
PRs with All Checks Green 3
READY 3
FAILING 25
PENDING 0
NO CHECKS YET 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=403499176a5d != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@github-actions

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

This was referenced Sep 22, 2026
@gHashTag

gHashTag commented Oct 2, 2026

Copy link
Copy Markdown
Owner Author

bee review (not merged) -- head 7051fc8b2afe5eff352e3a5a63a85b4d2c71c069, master 7079823ca7c5

Content is sound:

  • specs/skills/trinity-connect-accounts.t27 matches the shape of the 27 skill cards on master (e.g. trinity-doctor.t27); no card of that id exists on master.
  • feat(skills): connect-accounts — signing a person in through their own remote browser trinity#1122 is MERGED; the vendored SKILL.md at its merge commit hashes to b8401486a420... exactly as the card says. (The vendored copy has since moved to c7eadb87f1ed...; cosmetic, the field is a comment.)
  • Refs #3544 is the right issue (skills as first-class .t27 cards).
  • Required checks validate, check-linked-issue, parse-ratchet: green.
  • coverage, duplicate-bodies: red on the PR's merge base 5fdeca8a too. Corpus ratchet: the moved type name is Mpsse, not in this diff. Not blockers.

Blocker: Check L1 TRACEABILITY is red and the PR causes it -- the only commit, 7051fc8b2 feat(specs/skills): trinity/connect-accounts ..., carries no issue reference (the body's Refs #3544 does not satisfy this check). Master does not run it, so it is not a known master red.

Also note: every check on this head is from 2026-09-22, 381 commits behind master; the NOW entry is dated 2026-09-22 and would fail check-now-freshness (window 2026-10-01..03) on a re-run, as it now does on #4116/#4113/#4541.

To clear: a commit whose message carries Refs #3544, with the NOW entry re-dated into the current window; that re-runs everything on a current base.

gHashTag and others added 2 commits October 3, 2026 03:50
The NOW sync gate reads the entry date from the filename and accepts only
yesterday..tomorrow UTC. The entry was dated 2026-09-22; it is moved to
2026-10-03 with its heading, and a line says it was re-dated for re-review.

Refs #3544

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-02 20:56:18 UTC

Summary

Status Count
Total Open PRs 34
PRs with Failing Checks 28
PRs with All Checks Green 6
READY 1
FAILING 28
PENDING 0
NO CHECKS YET 0

These columns do not partition: 1 + 28 + 0 + 0 = 29, and there are 34 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=b45a356c2eb6 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-02 20:59:54 UTC

Summary

Status Count
Total Open PRs 34
PRs with Failing Checks 30
PRs with All Checks Green 4
READY 1
FAILING 30
PENDING 0
NO CHECKS YET 0

These columns do not partition: 1 + 30 + 0 + 0 = 31, and there are 34 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=b45a356c2eb6 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@gHashTag

gHashTag commented Oct 2, 2026

Copy link
Copy Markdown
Owner Author

Replacement opened: #5630. It has the same net diff as this PR, squashed into one commit that carries an issue reference, so L1 TRACEABILITY can pass without a force-push. I'm leaving this PR open; the reviewer closes it after #5630 merges.

gHashTag added a commit that referenced this pull request Oct 2, 2026
Supersedes #4600: same net diff as one commit carrying an issue reference.

Refs #3544

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@gHashTag

gHashTag commented Oct 2, 2026

Copy link
Copy Markdown
Owner Author

Superseded by #5630, which carries the same tree (3517ff17) as one commit with Refs #3544, merged as 32c726f. Closing without merging; the content has landed.

@gHashTag gHashTag closed this Oct 2, 2026
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.

2 participants