overleaf-codex 0.1.0-rc.4 → 0.1.0

package/README.md

@@ -6,7 +6,7 @@
 
 [![CI](https://github.com/umiskky/overleaf-codex/actions/workflows/ci.yml/badge.svg)](https://github.com/umiskky/overleaf-codex/actions/workflows/ci.yml)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
-[![Status](https://img.shields.io/badge/status-v1--rc--local--gates-blue.svg)](#current-status)
+[![Status](https://img.shields.io/badge/status-v1--stable--released-green.svg)](#current-status)
 
 `overleaf-codex` provides the `olcx` CLI for writing LaTeX papers locally while
 using a bound Overleaf project for remote compilation.
@@ -84,9 +84,9 @@ Overleaf passwords.
 
 ## Current Status
 
-v1 is a release candidate. Local gates are tracked in
-[docs/release-notes-v1.md](docs/release-notes-v1.md); stable release remains
-blocked until a sanitized disposable real Overleaf E2E pass is recorded.
+v1 is released as `0.1.0`. Release gates, stable approval, and the sanitized
+disposable real Overleaf E2E artifact are tracked in
+[docs/release-notes-v1.md](docs/release-notes-v1.md).
 
 The implemented command surface is:
 
@@ -150,7 +150,7 @@ command to run next.
 - [docs/troubleshooting.md](docs/troubleshooting.md) lists diagnosis commands.
 - [docs/npm-packaging.md](docs/npm-packaging.md) explains package contents.
 - [docs/release-gates.md](docs/release-gates.md) explains release checks.
-- [docs/release-notes-v1.md](docs/release-notes-v1.md) records the v1 RC status, release notes, known limitations, and stable-release approval rule.
+- [docs/release-notes-v1.md](docs/release-notes-v1.md) records the v1 release status, release notes, known limitations, and stable-release approval.
 
 See the [minimal example paper](examples/minimal-paper/README.md) for a
 sanitized project layout with `.olcx/config.json`, an auth-file shape example,

package/docs/compile.md

@@ -33,9 +33,15 @@ olcx compile --disable-fast-fallback
 olcx compile --fast-fallback-timeout 60000
 ```
 
-When fallback produces the PDF, command output includes `Status:
-fallback-success` and `Fallback: fast/draft`. Treat that PDF as a recovery
-artifact, not a full normal compile result.
+When fallback produces the PDF, command output includes:
+
+```text
+Status:
+fallback-success
+Fallback: fast/draft
+```
+
+Treat that PDF as a recovery artifact, not a full normal compile result.
 
 If both modes fail, inspect the compile output, fix the LaTeX source locally or
 on Overleaf, run `olcx sync --dry-run`, and compile again.

package/docs/release-notes-v1.md

@@ -1,8 +1,11 @@
 # v1 Release Notes
 
-Release candidate status: Local release-candidate gates passed; stable release remains blocked until sanitized disposable real Overleaf E2E is recorded.
+Release candidate status: RC cycle completed; stable v0.1.0 is approved after
+local gates and sanitized disposable real Overleaf E2E verification.
 
-Stable release decision: Not approved for stable release until a sanitized disposable real Overleaf E2E pass is recorded.
+Stable release decision: Approved for stable release
+
+Sanitized real E2E artifact: gh-release://umiskky/overleaf-codex/v0.1.0/sanitized-real-e2e.md
 
 `olcx` is not an official Overleaf project and is not an official `olcli` project. It is not affiliated with, endorsed by, or maintained by Overleaf or `olcli`.
 
@@ -21,7 +24,7 @@ Stable release decision: Not approved for stable release until a sanitized dispo
 
 ## Final Gate Checklist
 
-These gates must pass before an RC can be considered locally verified:
+These gates passed before stable v0.1.0 approval:
 
 ```bash
 npm run build
@@ -32,66 +35,50 @@ npm audit --audit-level=high
 npm pack --dry-run --json --ignore-scripts
 npm run prepublish:check
 npm run dev -- --help
+npm run e2e:real
 ```
 
-`npm pack --dry-run --json --ignore-scripts` must match the `package.json` `files` allowlist and must not include local auth, local or secret JSON, environment files, `tmp/`, tests, scripts, generated PDFs, logs, `node_modules/`, or real E2E output.
+`npm pack --dry-run --json --ignore-scripts` must match the `package.json`
+`files` allowlist and must not include local auth, local or secret JSON,
+environment files, `tmp/`, tests, scripts, generated PDFs, logs,
+`node_modules/`, or real E2E output.
 
 ## npm Publishing Status
 
-Stable npm publish is blocked. The repository contains
-`.github/workflows/npm-publish.yml` for GitHub Actions Trusted Publishing through
-the protected `npm-publish` environment, but the current v1 notes do not approve
-a stable npm release.
+Stable npm publishing is approved for v0.1.0. The repository contains
+`.github/workflows/npm-publish.yml` for GitHub Actions Trusted Publishing
+through the protected `npm-publish` environment.
 
 Release tags must match `package.json`:
 
 - `vX.Y.Z-rc.1` style prerelease versions must use GitHub prereleases and npm
   dist-tag `next`.
 - `vX.Y.Z` stable versions must use non-prerelease GitHub releases and npm
-  dist-tag `latest` only after stable approval.
-
-Sanitized real E2E artifact: not recorded for this release candidate. This line
-is a placeholder for the future sanitized artifact reference and is not evidence
-of a completed real E2E run.
-
-Future stable approval must replace the placeholder with this concrete format:
-
-```text
-Sanitized real E2E artifact: gh-release://umiskky/overleaf-codex/vX.Y.Z/sanitized-real-e2e.md
-```
-
-The forced skip smoke is allowed but is not a stable substitute. It only proves
-the CI command is safely disabled for agent-safe release-candidate checks.
+  dist-tag `latest` after stable approval.
 
-## Real Overleaf E2E Policy
+## Real Overleaf E2E Record
 
-The default release-candidate verification runs only the forced skip smoke:
-
-```bash
-OLCX_E2E_IGNORE_LOCAL_ENV=1 OLCX_E2E_ENABLE_REAL=0 npm run test:e2e:real
-```
-
-This command must not read `.env.e2e.local` and must not contact Overleaf.
-
-A stable release requires a separate disposable real Overleaf E2E pass. The recorded artifact must be sanitized and must state:
+The stable release artifact states:
 
 - the command completed successfully against a disposable project;
-- no raw cookie, session value, account label, private project id, or private paper content is recorded;
-- the artifact path is a sanitized handoff or release-management artifact, not a packaged npm file.
+- No raw cookie, session value, account label, private project id, or private paper content is recorded.
+- the artifact path is a sanitized release-management artifact, not a packaged npm file.
 
 No raw real-E2E credentials, project IDs, cookies, or private paper contents may be committed.
 
+The forced skip smoke is allowed but is not a stable substitute. It only proves
+the CI command is safely disabled for agent-safe checks.
+
 ## Known limitations
 
 - Overleaf access depends on Overleaf private interfaces and may break when Overleaf changes its web or compile behavior.
 - Authentication uses a session cookie or environment-provided token-like value; v1 must not store Overleaf passwords.
 - JSON output mode is reserved for a future release.
 - v1 is a CLI release. A VS Code extension is intentionally out of scope.
-- Real E2E is gated because it needs disposable Overleaf credentials and a disposable Overleaf project.
+- Real E2E requires disposable Overleaf credentials and a disposable Overleaf project.
 
 ## Post-v1 roadmap
 
-- Add a stable release process after sanitized disposable real E2E is recorded.
 - Improve structured output for automation.
 - Expand compatibility coverage as Overleaf behavior changes.
 - Consider a VS Code extension only after the CLI workflow is stable.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "overleaf-codex",
-  "version": "0.1.0-rc.4",
+  "version": "0.1.0",
   "description": "Local Git, VS Code, and Codex workflow bridge for Overleaf-backed LaTeX compilation.",
   "type": "module",
   "repository": {