Updated: 2026-07-28
Base commit: 2b6e5128 (3way modernization replay)
Integration branch: merged
Replaces: historical PROGRESS.md completion ledger (archive only — not active truth)
The fork maintains exact mirrors of kenn-io/agentsview and
latentsignal-org/periscope, with integrative merged carrying current
AgentsView foundation plus additive Periscope product features.
This document tracks operator-facing modernization (tooling, docs, install,
sync safety). Product feature work remains in docs/periscope-v1-plan.md and
related specs.
| Item | Status | Notes |
|---|---|---|
docs/ARCHITECTURE.md |
Ported | kenn-io/latentsignal canon; SessionVitals invariant |
| Build design + plan docs | Ported | Historical May 2026 + 2026-07 epilogue |
docs/guides/periscope-upstream-sync-blueprint.md |
Updated | SessionVitals alignment |
scripts/sync-upstream.sh |
Ported | dry-run, simulate, non-interactive, no auto-push |
scripts/install.sh |
Ported | Periscope product + agentsview compat |
scripts/install_test.sh |
Updated | Periscope URLs + legacy env aliases |
| Release tag convention | Documented | v{semver}-{8-char-sha} from 5bd2e8a |
| Desktop/API/doctor product identity | Done (this replay) | User-facing name Periscope; bundle io.latentsignal.periscope |
~/.agentsview/desktop.env |
Preserved | Desktop shell still reads legacy path for compatibility |
Fork releases always embed the short commit hash of the release commit.
Adopted in commit 5bd2e8a421c326a9a40e73437930ba76f475b9cb (May 2026).
v{semver}-{8-char-commit} e.g. v0.29.2-periscope.2-657a1090
Semver pre-release identity on merged:
v0.(upstream_minor + 1).2-periscope.2
Operator tagging (after verification — never automatic from tooling):
COMMIT=$(git rev-parse --short=8 HEAD)
VERSION="v0.29.2-periscope.2"
git tag -a "${VERSION}-${COMMIT}" -m "Release ${VERSION}-${COMMIT}"Canonical: io.latentsignal.periscope (matches latentsignal-org/periscope Layer 2).
The legacy AgentsView desktop bundle id io.agentsview.desktop is not
retained: in-app updater continuity would require shipping under the same
identifier, but the product rename intentionally starts a new desktop lineage.
Users on AgentsView-branded desktop builds reinstall or migrate manually; fork
updater artifacts target diazMelgarejo/periscope.
Compatibility preserved: ~/.agentsview/desktop.env is still read for desktop
shell environment overrides (see desktop/src-tauri/src/lib.rs).
| Area | State | Tracker |
|---|---|---|
| Data-version and doctor user text | Complete | Periscope wording and tests |
| OpenAPI product identity | Complete | Periscope API and tests |
cmd/agentsview → cmd/periscope |
Complete | module, Makefile, Docker, and CI |
Desktop sidecar periscope-* artifacts |
Complete | bundle, spawn, and workflow tests |
| Full current AgentsView foundation | Complete locally | unpushed replay branch |
release.yml archive names |
Complete | Periscope archives and PyPI normalization |
- No remote mutation without authorization — mirror refresh needs backup tag
- lease SHA; scripts enforce this.
- Dual pedigree — do not rebase
mergedonto one mirror only; use blueprint disposable-worktree replay. - Desktop signing — unsigned CI builds expected until
TAURI_SIGNING_PRIVATE_KEY+PERISCOPE_UPDATER_PUBKEYare configured (72431d3b). - First Periscope-tagged release on diazMelgarejo — install script falls back
to legacy
agentsview_*archives untilperiscope_*assets ship.
# Preview upstream movement (no writes)
./scripts/sync-upstream.sh --dry-run --source kenn
./scripts/sync-upstream.sh --dry-run --source latentsignal
# Merge probe in disposable worktree
./scripts/sync-upstream.sh --simulate --source kenn
# Install script tests
./scripts/install_test.sh
# Release tag (operator, after verification)
COMMIT=$(git rev-parse --short=8 HEAD)
git tag -a "v0.29.2-periscope.2-${COMMIT}" -m "Release v0.29.2-periscope.2-${COMMIT}"| Doc | Role |
|---|---|
periscope-upstream-sync-blueprint.md |
Sync policy |
ARCHITECTURE.md |
Matryoshka + invariants |
agentsview-to-periscope-rename-catalogue.md |
Rename decision tree |