fix: clarify external checkpoint discovery warning

[peyton-alt]

When checkpoints are pushed to a separate checkpoint remote, the push can succeed even though entire.io may not be able to discover that remote from the repository. The old hint only told the user to commit .entire/settings.json, but it didn’t explain the consequence.

This change makes the post-push warning consequence-first:

[entire] Note: Commit and push .entire/settings.json or entire.io may not find checkpoints on this remote.

Scope:

• only after successful pushes to an external checkpoint remote URL
• only when .entire/settings.json is not tracked by git
• only once per push process

Refs: #859

---

Note

Medium Risk
Adds a new post-push hint gated by an external checkpoint URL and a git ls-files check, plus introduces a new Copilot JSONL compaction path; both affect user-facing CLI output and transcript parsing behavior.

Overview
After successful pushes to an external checkpoint URL remote, the CLI now emits a consequence-first hint when /.entire/settings.json is not tracked by git, and ensures this message prints only once per process via sync.Once (applied to both v1 doPushBranch and v2 doPushRef).

The transcript compactor gains Copilot JSONL support: format detection is added post-truncation, a new compactCopilot converter inlines tool.execution_complete results into preceding tool_use blocks, and fixture-based tests + sample data validate the transformation.

^{Reviewed by Cursor Bugbot for commit fe2de3e. Configure here.}

[Copilot]

Pull request overview

This PR improves user feedback after pushing checkpoints to an external checkpoint remote by warning (once per process) when .entire/settings.json isn’t tracked, clarifying that entire.io may not be able to discover the checkpoint remote. It also adds support for compacting GitHub Copilot CLI transcripts into the normalized transcript.jsonl format.

Changes:

• Emit a consequence-first post-push note for external checkpoint remote pushes when .entire/settings.json is untracked (deduped via sync.Once).
• Add Copilot transcript compaction (assistant.message / tool.execution_complete → inlined tool results) plus fixtures and a unit test.
• Rename the Codex "message" constant to a shared transcriptTypeMessage for reuse in format detection.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
cmd/entire/cli/strategy/push_common.go	Adds printSettingsCommitHint + isSettingsTrackedByGit to print the clarified warning after successful URL pushes.
cmd/entire/cli/strategy/push_v2.go	Invokes the new post-push settings hint after successful v2 ref pushes.
cmd/entire/cli/strategy/push_common_test.go	Adds tests covering settings tracking detection and hint printing/deduping.
cmd/entire/cli/transcript/compact/compact.go	Routes Copilot-format transcripts through the new compactor.
cmd/entire/cli/transcript/compact/copilot.go	Implements Copilot JSONL detection and compaction with inlined tool results.
cmd/entire/cli/transcript/compact/copilot_test.go	Adds fixture-based test for Copilot compaction.
cmd/entire/cli/transcript/compact/testdata/copilot_full.jsonl	Adds a Copilot raw transcript fixture.
cmd/entire/cli/transcript/compact/testdata/copilot_expected.jsonl	Adds expected normalized output for the Copilot fixture.
cmd/entire/cli/transcript/compact/codex.go	Renames the "message" type constant used by Codex parsing.

[Copilot]

These tests temporarily replace the process-wide os.Stderr but don’t restore it via t.Cleanup/defer, so a t.Fatalf/require failure before restoration can leak the redirected stderr into later tests. Consider using t.Cleanup to always restore os.Stderr (see strategy/checkpoint_token_test.go for an example), and also close both pipe ends via defer to avoid FD leaks on early returns.