docs: integrate installed resource loading
This commit is contained in:
1 parent
d22d4b0f6e
commit
bd377c9732
9 files changed
+143
-301
No files matched your search
@@ -0,0 +1,100 @@
|
||||
# Task: Integrate installed resource loading fix to main
|
||||
|
||||
## Identity
|
||||
|
||||
- Task ID: 20260903-integrate-installed-resources-4b7e2c91
|
||||
- Mode: Integration
|
||||
- Branch: codex/20260903-integrate-installed-resources-4b7e2c91-integrate-installed-resources
|
||||
- Worktree: D:\Datas\OthersProjects\makelore-integrate-installed-resources-4b7e2c91
|
||||
- Base commit: 28e1690038d61b9333a2f6ca77f0187ea4273676
|
||||
- Owner: codex
|
||||
- Status: Ready for Main Promotion
|
||||
|
||||
## Scope
|
||||
|
||||
- Integrate the completed packaged Device Package prepare fix and the successor
|
||||
installed-resource activation fix onto the current local `main` history.
|
||||
- Promote the accepted behavior and evidence into current-state, architecture,
|
||||
README, evidence, and release-acceptance memory.
|
||||
- Verify the exact integrated source tree without installing a replacement
|
||||
client, publishing artifacts, pushing, or modifying unrelated user work.
|
||||
|
||||
## Intent And Constraints
|
||||
|
||||
- Every resource explicitly installed and currently enabled by the user must be
|
||||
included in the Main-selected parent resource generation. Manual disablement
|
||||
remains authoritative.
|
||||
- The generated Makelore extension remains the required first extension. All
|
||||
further selected Device Package extensions load through Pi's explicit
|
||||
additional-extension input while ambient project/user discovery stays off;
|
||||
selected Skill paths remain unchanged and child workers stay empty.
|
||||
- Treat the two source task records as read-only integration evidence. Do not
|
||||
rewrite their history or broaden this merge into Marketplace, Provider,
|
||||
Renderer, deployment, publication, or installed-application changes.
|
||||
- The root `main` worktree is owned by an earlier diagnostic task and contains
|
||||
three pre-existing untracked task records. Preserve them exactly; do not
|
||||
stash, reset, clean, adopt, overwrite, or force-release that ownership
|
||||
without explicit human confirmation.
|
||||
|
||||
## Integration Plan
|
||||
|
||||
1. Fast-forward the completed source history from current `main` into this
|
||||
isolated integration branch and confirm both product commits are present.
|
||||
2. Reconcile the accepted promotion with canonical product/architecture
|
||||
memory and the release acceptance commitment.
|
||||
3. Run focused tests, full unit/pressure verification, typecheck, scoped lint,
|
||||
production build, diff checks, and the task documentation gates.
|
||||
4. Advance local `main` only through a clean, ownership-safe operation.
|
||||
|
||||
## Outcome
|
||||
|
||||
- Fast-forwarded the completed source history through
|
||||
`d22d4b0`, retaining product commits
|
||||
`5a2f0eb6785b59d8b455ed5cb1d9773351ff895a` and
|
||||
`17664c5fffcfe695653b4146503e645f54767c4b` on the integration history.
|
||||
- Packaged Device Package inspection now resolves `DefaultPackageManager` and
|
||||
in-memory settings from the distributed physical Pi runtime. The generated
|
||||
Makelore bridge remains required, and the Agent Server loads every further
|
||||
Main-selected installed/enabled extension through Pi's explicit additional
|
||||
paths without ambient discovery; all selected Skill paths remain unchanged.
|
||||
- Promoted the accepted behavior and verification boundary into `README.md`,
|
||||
canonical current state, system overview, module map, evidence index, and the
|
||||
Windows release commitment. The README's stale Hosted Web Search description
|
||||
was reconciled with the already-integrated selected-model tool architecture.
|
||||
- Excluded the two source task-owned records from the final integration tree as
|
||||
required by the task-aware document boundary. Their files and commits remain
|
||||
intact on the source branches; this integration record carries the promoted
|
||||
default-branch result.
|
||||
- No installed application, local Device Package store, user project, package,
|
||||
deployment, publication, remote branch, or unrelated root-worktree file was
|
||||
changed.
|
||||
|
||||
## Verification
|
||||
|
||||
- `corepack pnpm install --frozen-lockfile` — passed with pinned pnpm 10.33.4;
|
||||
lockfile unchanged.
|
||||
- Focused integrated regressions — 5 files / 31 tests passed, including packaged
|
||||
package authority, generated extension bundle, real Agent Server multi-extension
|
||||
registration, worker opener, and Device Package manager behavior.
|
||||
- Full unit suite — 222 files / 1,815 passed / 2 conditional skips; serialized
|
||||
coding-chat pressure test 1/1 passed.
|
||||
- `corepack pnpm run typecheck` — passed.
|
||||
- Scoped ESLint over all ten changed source/test files — passed.
|
||||
- `corepack pnpm run build:vite` — Renderer, Main, Preload, and release utility
|
||||
passed; only pre-existing mixed-import and chunk-size warnings were emitted.
|
||||
- `git diff --check` — passed.
|
||||
- The task-aware drift check initially identified the two imported source task
|
||||
records as foreign ownership files. They were removed from the integration
|
||||
result; the final drift result is recorded after this task record is committed.
|
||||
|
||||
## Follow-ups
|
||||
|
||||
- Build and install a client from the exact promoted `main`, then execute live
|
||||
Conversation prepare→confirm→activation with npm/Git/loose Skill coverage and
|
||||
a generation containing at least two enabled extensions. The currently
|
||||
installed 1.2.6 client remains the old, known-failing artifact.
|
||||
- No push was requested; remote publication remains separate.
|
||||
|
||||
## Promotion Candidates
|
||||
|
||||
- None. Accepted source-task promotions were applied during this integration.
|
||||
Reference in new issue
Block a user