Release Link v1.4.0

.github/workflows/ci.yml

@@ -81,8 +81,11 @@ jobs:
       - name: Install MCP package for verification
         run: python -m pip install ./mcp_package
 
-      - name: Run portability tests
-        run: python -m unittest tests.test_mcp_verify_core tests.test_web_http_core tests.test_release_hygiene tests.test_cli_parser_core tests.test_cli_runtime_core
+      - name: Install test runner
+        run: python -m pip install "pytest>=8,<10"
+
+      - name: Run broad Windows tests
+        run: python -m pytest tests -q --ignore=tests/test_installers.py --ignore=tests/test_serve.py --ignore=tests/test_large_wiki_smoke.py
 
       - name: Demo value-loop smoke test
         shell: pwsh
@@ -112,6 +115,13 @@ jobs:
       - name: Check shell syntax
         run: bash -n integrations/*/install.sh integrations/*/uninstall.sh integrations/_shared/*.sh
 
+      - name: Check PowerShell syntax
+        shell: pwsh
+        run: |
+          Get-ChildItem integrations -Recurse -Include *.ps1 | ForEach-Object {
+            [scriptblock]::Create((Get-Content -Raw $_.FullName)) | Out-Null
+          }
+
   release-hygiene:
     runs-on: ubuntu-latest
     steps:

CHANGELOG.md

@@ -6,6 +6,45 @@ Release sections use `MAJOR.MINOR.PATCH` versions that match `link-mcp` on PyPI
 
 ## [Unreleased]
 
+## [1.4.0] - 2026-06-14
+
+### Added
+
+- Added official CLI skills under `skills/` so agents can lazy-load Link workflows without MCP setup.
+- Added `lnk try` as a one-command demo proof loop that creates the demo, checks readiness, runs query/brief examples, and prints first agent prompts.
+- Added `lnk connect <agent>` to preview or write MCP client config for Codex, Kiro, Claude Code, Cursor, Antigravity, VS Code, and Copilot.
+- Added Windows PowerShell installers for Codex, Kiro, Claude Code, Cursor, Antigravity, VS Code, and Copilot.
+- Added optional `review_after` dates for durable memories so time-sensitive context can automatically return to the memory inbox for re-checking.
+- Added optional `expires_at` dates for durable memories so temporary context automatically leaves default recall after expiry.
+- Added `lnk import-obsidian <vault>` to copy Obsidian Markdown notes into `raw/obsidian/` with secret scanning before the normal ingest workflow.
+- Added `lnk compliance-export` for redacted readiness, validation, memory-review, operation, and log exports for team or security review.
+- Added `lnk restore-backup` to preview and confirm local backup restores with unsafe-tar checks, raw restore opt-in, and pre-restore safety backups.
+- Added `lnk team-sync` to print a safe Git sharing plan for reviewed team memory without pushing private raw sources automatically.
+- Added `lnk share <page-or-memory>` to print a local viewer permalink and agent prompt for a specific Link page.
+- Added `lnk snapshot` to export a static, read-only HTML snapshot for demos or reviews while excluding raw sources, captures, live state, and memory pages by default.
+- Added memory `visibility` metadata (`private`, `project`, or `team`) so team sharing can rely on explicit user intent instead of inferring privacy from scope alone.
+- Added `lnk set-memory-visibility` and MCP `set_memory_visibility` so existing memories can move between private, project, and team sharing intent after explicit user approval.
+- Added `lnk memory-log`, MCP `memory_log`, `/memory-log`, and `/api/memory-log` for recent memory lifecycle changes without exposing raw source or memory bodies.
+- Added privacy-safe memory-log change summaries so review, status, and visibility transitions are visible without exposing memory bodies.
+- Added `lnk wins`, MCP `memory_wins`, `/wins`, and `/api/wins` for local, non-telemetry proof signals about what Link memory is carrying.
+- Added a team security review docs page covering local deployment, data boundaries, memory approval gates, Git sharing, audit exports, and current limits.
+- Added a memory contract docs page that explains the stable MCP agent loop, tool groups, write rules, budget behavior, and sharing semantics.
+- Added an integration maintainer checklist covering installer invariants, new-agent steps, PowerShell parity, and validation commands.
+- Added a scale model docs page covering bounded defaults, benchmark/health checks, large-wiki habits, and current local limits.
+- Added `python -m link_mcp --version` so MCP package installs can be verified before a wiki exists.
+- Added an Obsidian guide for opening Link's Markdown wiki as a vault and rebuilding indexes after manual edits.
+- Added validation and doctor failures for secret-looking values already present in wiki pages so local UI and MCP context do not quietly serve manually introduced secrets.
+
+### Changed
+
+- Broadened local secret detection for common modern provider tokens and credentials before capture, ingest, Obsidian import, and doctor scans.
+- Changed the installed CLI command from `link` to `lnk` to avoid the POSIX/macOS `link` utility collision while preserving source-checkout `python3 link.py ...` usage.
+- Tightened `lnk team-sync` readiness so unreviewed memories or active `visibility: private` memories block "ready" status before Git sharing.
+- Tightened `lnk snapshot --include-memories` so private memories stay excluded unless `--include-private-memories` is explicitly passed.
+- Broadened Windows CI from a small portability subset to most non-installer/non-server tests.
+- Clarified that the Homebrew formula lives in the separate `gowtham0992/homebrew-link` tap.
+- Tightened security reporting guidance to prefer private maintainer contact before public GitHub issues.
+
 ## [1.3.0] - 2026-05-22
 
 ### Added

LINK.md

@@ -170,6 +170,7 @@ type: memory
 title: "Short Memory Title"
 memory_type: preference | decision | project | fact | note
 scope: user | project | global
+visibility: private | project | team
 project: "optional-project-slug"
 status: active | stale | archived
 date_captured: "2026-04-09T14:30:00Z"
@@ -178,6 +179,7 @@ update_count: 0
 source: "manual | conversation | mcp | raw/source.md"
 last_update_source: ""
 review_status: pending | reviewed | needs_update
+review_after: "optional YYYY-MM-DD date for scheduled re-check"
 tags: [memory, relevant-tag]
 ---
 
@@ -287,6 +289,7 @@ Rules:
 - Keep memories specific and actionable. "User likes quality" is too vague; "User prefers release/* branches over codex/* branches" is useful.
 - Use `memory_type: preference` for user preferences, `decision` for choices made, `project` for project context, `fact` for stable facts, and `note` for everything else.
 - Use `scope: user` for broad personal preferences, `project` for the current project, and `global` for agent-wide principles.
+- Use `visibility: private` for personal memory, `project` for project-team sharing, and `team` only when the human explicitly wants the memory shared across a team workspace. If omitted, Link treats user/global memories as private and project memories as project-visible.
 - For `scope: project`, include a project key when you know it. `link.py` infers this from repo-local installs; otherwise pass `--project <slug>` or MCP `project`.
 - At the start of a session or substantial task, run `python3 link.py brief "<task or question>" .` or MCP `memory_brief` when available. Treat this as the default way to prime yourself with local memory, review warnings, and saved raw capture status.
 - For long chat/session notes, prefer `python3 link.py capture-session "<file-or-text>" .` or MCP `capture_session`; it stores the raw note locally and returns proposal-only memory candidates. If you do not need to keep the raw note, run `python3 link.py propose-memories "<file-or-text>" .` or MCP `propose_memories` instead. Do not write proposals until the human confirms.