Skip to content

Releases: haiqigeng/1-web-analyst-mcp-setup

v1.6.0 - Utility-first connection flow

Choose a tag to compare

@haiqigeng haiqigeng released this 22 Jul 21:38

Full Changelog: v1.5.0...v1.6.0

v1.5.0 - Credential isolation and configuration integrity

Choose a tag to compare

@haiqigeng haiqigeng released this 20 Jul 17:06

Highlights

  • Isolates each local MCP process to the environment keys declared for its selected tool/provider instead of exposing the complete local credential map.
  • Fingerprints Codex managed TOML blocks so Apply and reset preserve analyst modifications; exact v1.4-generated blocks migrate safely.
  • Installs only selected-provider runtimes, does not upgrade a healthy Node.js runtime, and no longer installs unrelated Git.
  • Emits documented remote MCP configuration for Claude Code and Gemini CLI, including environment-backed bearer headers where required.
  • Replaces broad analytics-account inventories with target-first, minimally disclosing read-only smoke tests.
  • Expands regression coverage from 26 to 36 tests and updates CI to the current official Node 24-based checkout action.

Upgrade Notes

  1. Update the skill, then run Apply -Client Selected -Preview before the real Apply.
  2. An unchanged v1.4 Codex managed block is recognized and migrated. A block changed by the analyst is preserved and Apply stops for explicit review.
  3. Run CheckMcpUpdates before Apply when local MCP packages are selected, then reload the configured client.
  4. Existing ignored credentials, tokens, package locks, evidence, and machine-specific state remain local and are not part of this release.

Verification

  • GitHub Actions: passed on commit 397ae5d with PowerShell 7 and Windows PowerShell 5.1.
  • Pester: 36/36 tests passed.
  • JSON schemas, PowerShell parsing, fixture tests, catalog review, and skill metadata: passed.
  • Release audit: passed; no local credential/runtime files in the 35-file tracked archive.
  • Audited archive SHA256: 7AC243B9027B85FBDB212D56CDFE2D090DA31D6F2E0C63F9F4529785DD312F96.

See README.md for first use and CHANGELOG.md for the complete change list.

v1.4.1

Choose a tag to compare

@haiqigeng haiqigeng released this 19 Jul 23:49

Full Changelog: v1.3.0...v1.4.1

v1.4.0 - Safe ownership, evidence, and reproducible setup

Choose a tag to compare

@haiqigeng haiqigeng released this 10 Jul 18:31

Highlights

  • Adds a real installable SKILL.md with Codex UI metadata while keeping AGENTS.md as a lightweight cross-agent entry point.
  • Makes Apply ownership-safe: selected clients only, preview mode, timestamped backups, collision refusal, and managed ownership records.
  • Adds ResetMcpConfig to remove only unchanged kit-owned entries. ResetKit now cleans local credentials and runtime state without silently deleting client configuration.
  • Records factual Configured, Authenticated, Visible, and Verified evidence, including target and human-verifiable read-only proof in onboarding reports.
  • Resolves npm and PyPI packages to exact local versions after update checks, preventing floating @latest launches.
  • Makes the MCP catalog the provider source of truth and adds lifecycle-based freshness windows plus scheduled provider checks.
  • Expands validation from 6 to 26 behavior and safety tests, with PowerShell 7, Windows PowerShell 5.1, JSON schema enforcement, and release-archive secret scanning.

Upgrade Notes

  1. Run CheckMcpUpdates before Apply; local MCP launchers now require an exact generated version lock.
  2. Run Apply -Client Selected -Preview before the real Apply to inspect client paths and server names.
  3. To disconnect, run ResetMcpConfig -Client Selected -ConfirmedMcpEndpointDeletion before ResetKit.
  4. Existing unowned MCP entries with the same server name are preserved and cause Apply to stop with a clear collision message.

Verification

  • GitHub Actions: passed on the release commit.
  • Pester: 26/26 tests passed.
  • JSON schemas and skill metadata: valid.
  • Release audit: passed; 35 tracked reusable files.
  • Audited archive SHA256: 35A44F643FCB48C359F9404AEE5CC866A89666D3C1098D6AD3080FFFF3687D0B.

See README.md for first use and CHANGELOG.md for the complete change list.

v1.3.0 - Setup guidance, safety, and maintainability

Choose a tag to compare

@haiqigeng haiqigeng released this 24 Jun 22:17

Highlights

  • Added CredentialGuide for direct selected-tool setup URLs and credential requirements.
  • Expanded CheckMcpUpdates with npm/PyPI freshness, remote endpoint reachability, and catalog verification age.
  • Added BigQuerySafetyPlan for dry-run, max-bytes, project/dataset, and approval guardrails.
  • Added provider lifecycle metadata for default/fallback/optional/candidate/private-beta/API-fallback decisions.
  • Added Pester maintainability tests and wired them into CI and release audit.

Release Checks

  • Confidentiality scan: no personal credentials, local PC paths, or test-client strings found in tracked reusable files.
  • Validate: passed.
  • TestFixtures: passed.
  • PesterTests: 6 passed.
  • CatalogReview: passed with the existing Gmail third-party risk warning.
  • ReleaseAudit: passed.

v1.2.0 - Cleaner first-day setup flow

Choose a tag to compare

@haiqigeng haiqigeng released this 24 Jun 21:41

Highlights

  • Default onboarding now uses direct tool selection; profiles remain dormant/manual.
  • Removed the generated access-request helper flow; access requests are drafted in conversation only when requested.
  • Improved first-day handover with clearer MCP configuration status, setup priority, and read-only smoke-test reminders.
  • Added safer local auth helpers for Drive/Gmail token refresh and BigQuery short-lived bearer-token fallback.
  • Clarified reset behavior so real onboarding keeps working credentials, while tests and handoffs can reset cleanly.

Release Checks

  • Confidentiality scan: no personal credentials, local PC paths, or test-client strings found in tracked reusable files.
  • Validate: passed.
  • TestFixtures: passed.
  • ReleaseAudit: passed.

v1.1.1 - First-day checklist patch

Choose a tag to compare

@haiqigeng haiqigeng released this 24 Jun 18:21

Adds the generated FirstDayChecklist output, makes OnboardingReport produce the checklist automatically, and tightens ReleaseAudit so releases fail when reusable files have uncommitted changes. Local release suite passed: Validate, TestFixtures, CatalogReview, and ReleaseAudit.

v1.1.0 - Release readiness and scalable onboarding

Choose a tag to compare

@haiqigeng haiqigeng released this 18 Jun 19:44

Adds client capability metadata, ReleaseAudit/CatalogReview/TestFixtures/ItRequest actions, structured onboarding state output, optional KEY_FILE secret loading, profile fixture checks, and expanded CI validation. Local release suite passed: Validate, TestFixtures, CatalogReview, and ReleaseAudit.

v1.0.0 - Web Analyst MCP Setup

Choose a tag to compare

@haiqigeng haiqigeng released this 18 Jun 19:21

Stable release of Web Analyst MCP Setup.

This release was rebuilt after the repository rename and checked for local credentials, personal test identifiers, generated files, and machine-specific state before upload.

Highlights:

  • Doctor diagnostics for machine readiness and selected tool state
  • OnboardingReport generation for local handover summaries
  • Reusable setup profiles: minimal, google-workspace, analytics-core, browser-testing, full-web-analyst
  • Catalog decision metadata for officialness, auth friction, runtime, data exposure, write capability, risk, and last verification date
  • JSON schemas and GitHub Actions validation
  • Data and credential safety guidance
  • IT request templates for Google, GA4, BigQuery, GTM, and vendor API approvals

Recommended start:

Read AGENTS.md and guide me through the web analyst setup.

For a quick health check:

powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\WebAnalystSetup.ps1 -Action Doctor