# LOOM 0.15.75 β€” Project Privacy, Canonical Access Identities & Live Avatars - Added System-Owner-only Public/Private project visibility. Public projects are marked with a globe; private projects are marked with a lock for authorized viewers. - Private projects are omitted server-side from project discovery for unauthorized viewers and rejected with a generic 404 before project metadata/shell output, preventing page-load glimpses. - Private project-owned assets are emitted with signed project/path URLs and return generic 404s when probed without a valid signature, closing the static-branding/media discovery gap. - Added System-Owner grant/revoke controls for giving specific permanent users or active standalone Guests access to private projects. Existing LOOM Admin / Project Admin authority remains valid for its scoped project. - Delegated-access grants follow a Guest when that identity is promoted into a permanent account, preventing access loss during account creation. - Access Manager now uses canonical visible display names everywhere and excludes attached browser lineage, claimed Guest histories, and standby future-Guest shells from grant selectors. - Portable User/Guest bundles now include private-project view grants and identity cleanup removes those grants alongside the person. - Generic project leaderboard responses resolve current avatar URLs live from LOOM profile/project identity state, with avatar-state cache versioning so avatar changes propagate to project leaderboards. - LOOM Home shows explicit `🌐 Public` / `πŸ”’ Private` project visibility state; only the System Owner receives the visibility toggle. # LOOM 0.15.74 β€” Project Module Completion State - Fixed the project-shell `Loading project modules…` fallback remaining visible after every real module had finished loading. - Action Runtime now authoritatively dismisses the shell waiting state when initial runtime startup reaches ready, so existing Instance Projects are repaired without modifying their instance-owned shell files. - New/baseline project shells use a stronger completed-state CSS rule and no longer depend on child-count MutationObserver heuristics. - The waiting element remains available when runtime startup actually fails, preserving useful startup-error feedback. # LOOM 0.15.73 β€” Core UX Consistency Polish - Backup & Restore removes its redundant in-page Admin button; the permanent global shell remains the single Admin navigation affordance. - Static shell links such as Admin now use the exact same global-control geometry, icon sizing, spacing, hover/focus treatment, and responsive height as Home, Share, Profile, and Switch User. - Admin Users receives a quieter integrated Refresh control with real busy feedback, improved directory-row hover/selection states, and smoother search/filter control rhythm. - Backup & Restore adopts the standard LOOM green primary/active-state language instead of a one-off blue accent. - Shared LOOM-owned Admin surfaces receive a restrained form/button/empty-state consistency pass without changing project-owned branding or application UI. # LOOM 0.15.72 β€” Permanent Account Identity Collapse - Permanent-account promotion no longer surfaces the pre-created future Guest generation as a second visible person. Future Guest generations are reserved as `standby` until an explicit sign-out or Guest selection activates them. - Admin Users and portable-person export hide standby Guest shells while preserving the claimed Guest History, aliases, browser lineage, avatars, project participation, project state, and activity under the permanent account. - Existing 0.15.68–0.15.71 split records are repaired idempotently when their empty post-claim generation has never accumulated project payload. - Explicit sign-out / Switch User activates the reserved Guest generation on demand, preserving the intended fresh-Guest workflow without duplicating the person at promotion time. # LOOM 0.15.71 β€” Loader, Admin UX & Navigation Reliability - Project loaders no longer render an empty secondary flying pill when the project wordmark has only one meaningful line. - LOOM Home project mutations carry the active client identity through authorization, and `project-manager.php` reads JSON identity context before access checks, eliminating false 403s for authorized System Owner/Admin project identity saves. - Active tabs use high-contrast light selected surfaces with dark text across Home, Admin, and Backup & Restore. - Native file pickers receive shared LOOM production styling instead of browser-default chrome. - Backup & Restore removes redundant Home navigation and gives its Admin control an explicit settings icon. - The permanent animated LOOM brand at the top-left of the global shell is now a keyboard-accessible Home link using the same canonical Home URL resolver as the normal Home control. # LOOM 0.15.70 β€” Clean Core Baseline - Removed the final bundled concrete-project migration payload from LOOM core. Release archives now contain engine code, generic project infrastructure, templates, and upgrade tombstones only. - Genericized leaderboard defaults and project-branding examples so core APIs/docs no longer imply a specific product project. - Removed installation-specific usernames and project names from permanent product documentation/comments. - Preserved only deployment tombstones required to remove obsolete release-owned paths during safe in-place upgrades; tombstones never target `instance/**`. - Rebuilt the deployment manifest from the sanitized tree and re-audited the release for user/project-specific identifiers and assets. # LOOM 0.15.70 β€” Canonical Release Watch + Production UI - Release Watch derives the running client release from canonical boot evidence and only announces a strictly newer semantic release. - Same-version fingerprint churn no longer creates false update banners or reload loops. - LOOM-owned Home, Admin, Backup & Restore, Activity, Referrals, Setup, Registry, project-shell, Header, Showcase, and Footer surfaces share a production-grade UI system while project-owned branding remains independent. # LOOM 0.15.68 β€” Portable Guests + System Owner migration bootstrap - Standalone Guests became first-class portable people alongside permanent accounts. - Blank-install bootstrap can restore a verified prior System Owner portable bundle while issuing fresh destination Administrator credentials. - Project + Data exports remain project-owned vertical slices; person bundles remain identity-owned horizontal slices across projects. # LOOM 0.15.67 β€” Runtime liveness and identity recursion recovery - Removed cyclic global-profile/project-identity resolution that could exhaust PHP workers. - Added recursion fuses, deployment-marker cleanup, bounded startup retries, and non-blocking deployment-status UX. # LOOM 0.15.66 β€” Home and identity runtime recovery - Restored Home bootstrap helpers and hardened visible-name resolution so internal allocation handles cannot become presentation names. - Hardened storage access in sandboxed frames and made Admin Users avatar resolution scope-relative. # LOOM 0.15.65 β€” Dynamic project identity inheritance - Project identities explicitly distinguish live global inheritance from intentional project overrides. - Project-specific presentation can no longer contaminate the global identity cache. # LOOM 0.15.64 β€” Authoritative module positioning - Project module position indexes became authoritative at runtime with deterministic collision handling and soft default composition positions. # LOOM 0.15.63 β€” Visible positioning controls + canonical Admin identity - Project Settings exposed module position indexes directly and Admin chrome was aligned with the canonical visible identity. # LOOM 0.15.62 β€” Identity/media hygiene + project discovery - Factory identity wipe gained exhaustive media cleanup and orphan-media reconciliation. - Built-in avatar presets were normalized, project search/pagination was added, deep-linked project user scopes were fixed, and human-facing timestamps became viewer-local. # LOOM 0.15.61 β€” Portable Users + scoped Backup & Restore - Backup & Restore was split into Global LOOM, Projects, and Users. - Single-user portable bundles capture the canonical identity ownership graph and restore create/merge-only without stealing unrelated identities. # Earlier core history Earlier 0.15.x and 0.12.x work established clean-instance releases, Instance Projects, project import/export, identity continuity, permissions, Admin tooling, HTML Framer, module discovery/composition, deployment gating, backup/restore, project branding, and persistence adapters. Concrete product-project development history is intentionally not retained in the clean core changelog. Deployment tombstones in `.loom-deployment.json` remain the sole source of obsolete release-path cleanup semantics required for upgrades.